Difference between revisions of "User:Michelle2 Zenovka/cmake-flags"
Jump to navigation
Jump to search
(→Flags) |
|||
| Line 23: | Line 23: | ||
|STANDALONE||BOOL||Sets the build to standalone mode, if enabled the build will try to use system provided libraries instead of the ones from the libs tarball. | |STANDALONE||BOOL||Sets the build to standalone mode, if enabled the build will try to use system provided libraries instead of the ones from the libs tarball. | ||
|- | |- | ||
|UNATTENDED|BOOL| | |UNATTENDED||BOOL||Normally set to false, Internal option for Linden Labs building??? | ||
|- | |||
|} | |} | ||
Revision as of 00:33, 29 July 2008
Intro
Normaly develo.py will bootstrap the actual cmake process for you, but you may wish to override certain operations. The Debian build for example does not use develo.py but calls cmake directly.
The typical invocation of cmake will look like the following :-
cmake -G "Visual Studio 7 .NET 2003" -DUNATTENDED:BOOl=FALSE -DSTANDALONE:BOOL=FALSE "" "c:\\secondlife\\Release\\release\\indra
cmake variables are passed on the command line with the -D option, followed by the variable name, a seperation colon, the type of variable then =value for example :-
-DSTANDALONE:BOOL=FALSE
Variable name STANDALONE
Type BOOL
value FALSE
Flags
| STANDALONE | BOOL | Sets the build to standalone mode, if enabled the build will try to use system provided libraries instead of the ones from the libs tarball. |
| UNATTENDED | BOOL | Normally set to false, Internal option for Linden Labs building??? |