Hi, On Wed, 2009-07-01 at 09:37 +0200, Johannes Brunen wrote: > Hello Gerrit, > > "Gerrit Vo" <[email protected]> schrieb im > Newsbeitrag news:[email protected]... > >
> > Another small warning I stumbled across, > > the std cmake boost find mechanism only react to these settings > > (static + mt) the very first time, once Boost has been found changing > > these flags/options does not change which boost libraries are used. > > So you have to delete/clean the cache to get changes in. > > > I did not understand that completely. it means that if you run cmake and it finds boost, say the dynamic libs (e.g. boost_system.dll). Now if you just enable static libs and just rerun cmake it will still point to boost_system.dll instead of the static libboost_system.lib. > > PDB file are generated for all targets but I made the install optional > > (OSG_INSTALL_PDB_FILES). I also added an option > > (OSG_USE_SEPARATE_LIBDIRS) so you can choose where the libs are placed > > during the install, the general lib dir or a target specific subdir. I > > still keep both .lib and .dll files in the lib dir, windows seems more > > to tend to install the .dll file in the bin dir. Would you prefer the > > bin dir or is the lib dir ok ? > > > Personally, I would prefer the bin dir for the dll files. This is how I > treat all other libs. ok, I can change that. > > If you have anything else let me know. One open issue is custom > > compiler flags. > > > I did follow your suggestion and implemented the settings of the flags in my > controller script. This work pretty fine. ok. > > I'm also not sure all the 3rd party libs are handled correctly for > > all variants. I'll try to check this but it will take a second as > > windows builds are so slow ;( And I have to build the 3rd party > > lib variants ;( > > > I do have builds of all the 3rd party libs of the current versions for the > 32Bit and 64Bit windows platform. If there is any interest I could provide > these. > > Below is a list of the libraries I did manage to build with the > standard CMake settings (debug[suffix 'D']+release) plus the following > compiler settings which I use consistently on all my builds. I'm still thinking of how to do that most efficiently on windows. Unfortunately it is such an empty system, and I don't like to make cygwin a prerequisite. One way is to go the VTK way and include all the sources needed, which is ok for the small stuff like image libs but with collada, gdal, or vtk itself it might get out of hand. The other is provide binary downloads and a build script which is based on cygwin so that if people want to / need to rebuild things they can easily do so. > -D_CRT_SECURE_NO_DEPRECATE > -D_CRT_SECURE_NO_WARNINGS > -D_CRT_NONSTDC_NO_DEPRECATE > -D_SECURE_SCL=0 > -D_SCL_SECURE_NO_WARNINGS > -D_SCL_SECURE_NO_DEPRECATE > > List: > === . . . . > The cmake scripts are only work on windows. I do not have experience with > platform independent builds. usually that should be fine. Most packages come either prebuild on unix or are easily build. And you don't have to fight with runtime and other settings like on windows. kind regards, gerrit ------------------------------------------------------------------------------ _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
