[sldev] [VWR] cmake flags

Robin Cornelius robin.cornelius at gmail.com
Tue Jul 29 04:31:22 PDT 2008


The previous post relating to the location of the FMOD api has got be
thinking and documenting too. There are many flags than can be passed
to the cmake process to control the operation and build. When invoking
cmake via develop.py these are all hidden and not possible to get to.
I have started listing them at
http://wiki.secondlife.com/wiki/User:Michelle2_Zenovka/cmake-flags

Some of these are particularly useful for distributors on linux as it
gives access to the unix makefile options. But others just may help
configure things and could be of use to someone (and probably could do
with listing).

Now have i missed something fundamental with cmake? is it possible to
invoke cmake to set one of these variables (I think they are all
cached type anyway) so that i could run for example :-

 cmake set -DFMOD_SDK_DIR:STRING=/path/to/fmod/

and then the complete run of develop.py would then bootstrap cmake and
pick up my set variables from the cache? or should develop.py have a
method for passing through custom parameters to cmake? or is it
assumed anyone wanting to pass custom parameters can pass all the
parameters required and just will not be using develop.py anyway and
the particular fmod case is unique?

Also drifting off original topic slightly..... i have also been trying
to update the cmake build instructions and based on the current state
of the release branch i have updated
https://wiki.secondlife.com/wiki/User:Michelle2_Zenovka/cmake and i
think the builds are pretty complete for windows, and close for linux,
any differences for mac (mainly Prerequisites, i have not got a clue,
so if some one can flesh out or merge with the windows section if
approprate etc, that would be great).

Robin


More information about the SLDev mailing list