Larry Evans wrote:
> On 10/12/07 15:33, Larry Evans wrote:
> [snip]
> There is a workaround. Running the attached bash shell
file with no
> CMakeCache.txt file present, results in a new
CMakeCache.txt with:
>
> //CXX compiler.
>
CMAKE_CXX_COMPILER:FILEPATH=/home/evansl/download/gcc/4.3-20
071005/install/bin/g++
>
>
> //First argument to CXX compiler
> CMAKE_CXX_COMPILER_ARG1:STRING= -std=gnu++0x
>
-I/home/evansl/prog_dev/boost-cvs/ro/boost/sandbox/variadic-
templates
I did not see this before I answered... At least I answered
correctly.
You should also be able to do this:
cmake -DCMAKE_CXX_COMPILER=/home/evansl/download/gcc/
4.3-20071005/install/bin/g++ -DCMAKE_CXX_COMPILER_ARG1=
-std=gnu++0x
-I/home/evansl/prog_dev/boost-cvs/ro/boost/sandbox/variadic-
templates
That should have the same effect without having to use a
shell variable.
I guess you could do this as well:
Create a CMakeCache.txt that this contents:
CMAKE_CXX_COMPILER:FILEPATH=/home/evansl/download/gcc/4.3-20
071005/install/bin/g++
CMAKE_CXX_COMPILER_ARG1:STRING= -std=gnu++0x
-I/home/evansl/prog_dev/boost-cvs/ro/boost/sandbox/variadic-
templates
Put that into an empty directory and run cmake with a path
to the source.
An initial cache file could be the same as the
user-config.jam file. I have not used jam, but I assume
you have one
of these per compiler. You could have an initial
CMakeCache.txt for
each of the compilers you use for cmake.
-Bill
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
a>
|