Thanks for all the input guys. Grabbing the Nuke find package from OpenColorIO was a good start. And the out-of-source build mindset cemented things.
Initially I found this tutorial to be helpful, if anyone else is just starting out with CMake: http://www.cs.swarthmore.edu/~adanner/tips/cmake.php -Paul On Mon, Oct 31, 2011 at 6:45 AM, Colin Doncaster <[email protected]>wrote: > +1 > > Don't try and control CMakes structures too much or else you'll end up > with a nightmare CMakeList to manage. make VERBOSE=1 is your friend. > > * > -- > Colin Doncaster > Peregrine Labs > http://peregrinelabs.com > * > > On 2011-10-30, at 11:52 AM, Moritz Moeller wrote: > > On 10/28/2011 08:15 PM, Paul Hudson wrote: > > Hi all, > > > We are just starting to use CMake. Does anyone have recommendations for > > folder structure, CMakeLists.txt examples? > > > I just suggest you use an out-of-source build folder. > > Furthermore, we do a local install with relative folder names. > I.e. 'make install' will create the folder structure inside the build > folder. That way we make no assumptions, when creating e.g. tbz2 archive > for our customers on Linux, where the default deployment location is of > the plugin is, on the client's side. > > > .mm > _______________________________________________ > Nuke-dev mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev > > > > _______________________________________________ > Nuke-dev mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev > >
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
