[sldev] easybuild branch
Brad King
brad.king at kitware.com
Tue Apr 21 06:58:24 PDT 2009
Robin Cornelius wrote:
> please have a look at
> http://jira.secondlife.com/browse/VWR-10579 i've added some extra
> comments (and patch) as the patch applied is still broken and not
> enabling NDOF in standalone mode.
Thanks. I've updated the issue further.
> I'm all for cmake improvements if they simply the build process
[snip]
> i assume you mean a general cmake change.
Yes, of course. The idea is that improvements that go to CMake help
everyone while develop.py is only for Second Life.
>> One idea to auto-create a build tree is to have some kind of file in the
>> source tree that tells CMake where to put the build tree if a user tries
>> an in-source build.
>
> This sounds interesting, I think it would be very useful to allow the
> build location to be set via CMakeList.txt or the command line. So the
> current way still works but a new system of allowing some function like
[snip]
> set_build_directory("viewer-${ARCH}")
By the time CMake processes a CMakeLists.txt file it needs to already
know where the build tree goes. My proposal is to have an extra file
called something like "InSource.cmake" which can be put at the top of
the source tree. If someone tries to do an in-source build, this file
will be loaded first and it can choose a different build tree. All
this will happen before CMakeLists.txt code runs though, and I'm not
sure what information we'll be able to make available to the startup
script.
> So what i would like to see is as follows
>
> 1) Standard build automaticly grabs everything
> 2) Full standalone, no artwork in source tree
> 3) standalone with automatic artwork fetch
I'm sure something like this is possible.
> I can see how the existing functionality of vstool could be integrated
> into cmake. But please remember this does not and cannot work for
> express editions of visual studio as they do not support the API's
> necessary for automated editing of the solution, needed for setting the
> project user options file that contains the default working directory,
> the start up project and the build type, to name a few options.
IIRC the information is not actually in the .sln file but in a user
file (.suo or something) next to it. We might be able to directly
generate that file if it does not exist, but it need investigation.
> Something that has not been discussed is the install target.
[snip]
> What is there now does work so please keep that intact.
Sure.
-Brad
More information about the SLDev
mailing list