On Thu, 2013-04-04 at 18:37 +0200, Armin K. wrote: > I believe the more correct term is "autotools variables" since CMake > also produces Makefiles :)
The Autotools don't actually have anything to do with them, other than the fact that I think they can be used to override them at configure time. http://www.gnu.org/software/make/manual/html_node/Implicit-Variables.html#Implicit-Variables has a list of all the variables that Make can use in its implicit rules. I'm pretty certain that other, non-GNU, Make implementations honour a similar list of variables. The SUSV4 spec states: "The default rules for make shall achieve results that are the same as if the following were used. Implementations that do not support the C-Language Development Utilities option may omit CC, CFLAGS, YACC, YFLAGS, LEX, LFLAGS, LDFLAGS, and the .c, .y, and .l inference rules. Implementations that do not support FORTRAN may omit FC, FFLAGS, and the .f inference rules. Implementations may provide additional macros and rules." That suggests to me, that conforming Make implementations that *do* support the C-Language Development Utilities *must* support that particular list of variables. >From a quick browse of the cmake docs, it looks like it's a project similar to the autotools, in that it will produce 'native' Makefiles that can be run using GNU Make, and therefore CFLAGS & CXXFLAGS can be used with cmake too. Where the OPs C_FLAGS & CXX_FLAGS came from, I'm not sure :-) Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
