>>> We are willing to proceed on this but first it'd be nice to get some >>> feedback. I tried to keep the changes as small, easy-to-review commits. >> >> That's lovely. I'm not personally a suitable reviewer for cmake stuff >> but I hope one or two who are fluent in cmake will step up and at >> least offer a comment on your series... > > As nobody responded, I've pushed your patch series as I trust that's at least > better than before. It still shows a > lack of interest in cmake though from > libcurl hackers in general.
Thanks. I continue to work on this. My guess is that most of the current developers already have their environment setup. I can't say I blame anyone for not being eager to change what's working for them. Most of non-libcurl-developers probably use binaries, so there are not many people left ;) I wonder what would most new developers choose. When I see a CMake script in the project, this is the first thing I try... Anyway, I have a CI build setup now for 5 platforms (Linux, Windows 32/64 and solaris x86_64). I still have 6 tests failing (probably due to out-of-source build) and many skipped (this must be due to current state of CMake scripts). This is example summary from my linux-64 machine: TESTDONE: 750 tests out of 756 reported OK: 99% TESTFAIL: These test cases failed: 1013 1014 1022 1023 1026 1119 TESTDONE: 945 tests were considered during 280 seconds. ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
