Re: [Cppcms-users] cppcms build problems
Brought to you by:
artyom-beilis
From: Artyom <art...@ya...> - 2009-11-10 21:32:07
|
Hello... > > Searching for libs is very easy - if there is already > support for it. It is > also often done without pkg-config. Something like > find_package(Boost 1.34 REQUIRED COMPONENTS thread > date_time program_options > regex filesystem) > may be enough. Good you mentioned it ;-) Just to make my points better. This exactly what stucks me now. I have two versions of boost, system installed 1.35 and local 1.39 I give CMake Paths to library headers and libs... It seearches... finds 1.39 but... Instead of linking with /some/path/to/libboost_foo_bar.so it links to /usr/lib/libboost_foo_bar.so Headers and libraries of different version!!! WTF?? All I need to do with auto is ./configure CXXFLAGS=-I/path/inc LIBS=-L/path/lib But CMake is smarter... Ok lets try to search a library by myself and check if I can find all I need... Find 5 libraries... but second if(X and Y and Z and T) does not work in CMake syntax... So lets write long-long tests... Ok lets check where we have socket? in libc, nls, or socket (AC_SEARCH_LIBS) there is no such thing (note it is quite different from find library)... Write long macros again. Now, lets check for simple C++0x feature "auto"... Wait a second for TRY_COMPILE I need to create a project instead of writing 3 lines. WTF??? ----------------------------- In other words... CMake is almost as useable as... handly written configure script. It is just too verbose, It is more verbose by an order of magnitude then auto* even for simple tasks you take for granted. > > Btw. have you already read > http://www.rrsd.com/software_development/boost/oopsla05.pdf > Thanks for the link... No I still didn't Artyom |