Re: [CMake] CPack and building installers for sub-projects

On Friday, April 01, 2011 02:42:53 pm Clinton Stimpson wrote: > On Friday, April 01, 2011 01:48:41 pm Crni Gorac wrote: > > On Fri, Apr 1, 2011 at 8:38 PM, Eric Noulard wrote: > > > 2011/4/1 Crni Gorac : > > >> Am working with seemingly not too complicated CMake setup: Have two > > >> projects, s

Re: [CMake] CPack and building installers for sub-projects

On Friday, April 01, 2011 01:48:41 pm Crni Gorac wrote: > On Fri, Apr 1, 2011 at 8:38 PM, Eric Noulard wrote: > > 2011/4/1 Crni Gorac : > >> Am working with seemingly not too complicated CMake setup: Have two > >> projects, say Foo and Bar, both dependent from the library libBaz; > >> actually at

Re: [CMake] CPack and building installers for sub-projects

2011/4/1 Crni Gorac : > > Thanks for replies.  I'm using CMake 2.8.4, and for this particular > project - it's mostly about PackageMaker and NSIS installers (for Mac > and Windows, respectively).  Also, CPack components stuff is really > not usable here, these are two projects with completely separ

Re: [CMake] CPack and building installers for sub-projects

On Fri, Apr 1, 2011 at 8:38 PM, Eric Noulard wrote: > 2011/4/1 Crni Gorac : >> Am working with seemingly not too complicated CMake setup: Have two >> projects, say Foo and Bar, both dependent from the library libBaz; >> actually at the beginning there was only Foo project, and now there is >> Bar

Re: [CMake] CPack and building installers for sub-projects

2011/4/1 Clinton Stimpson : > On Friday, April 01, 2011 12:38:25 pm Eric Noulard wrote: >> 2011/4/1 Crni Gorac : >> > Am working with seemingly not too complicated CMake setup: Have two >> > projects, say Foo and Bar, both dependent from the library libBaz; >> > actually at the beginning there was

Re: [CMake] CPack and building installers for sub-projects

On Friday, April 01, 2011 12:38:25 pm Eric Noulard wrote: > 2011/4/1 Crni Gorac : > > Am working with seemingly not too complicated CMake setup: Have two > > projects, say Foo and Bar, both dependent from the library libBaz; > > actually at the beginning there was only Foo project, and now there is

Re: [CMake] CPack and building installers for sub-projects

2011/4/1 Crni Gorac : > Am working with seemingly not too complicated CMake setup: Have two > projects, say Foo and Bar, both dependent from the library libBaz; > actually at the beginning there was only Foo project, and now there is > Bar project, and common code is refactored into libBaz library.

Re: [CMake] Static code analysis with CDash

I've used cppcheck as a test that fails in case of errors, and also that adds a target to run cppcheck. My script is here: https://github.com/rpavlik/cmake-modules/blob/master/CppcheckTargets.cmake It uses these additional

[CMake] CPack and building installers for sub-projects

Am working with seemingly not too complicated CMake setup: Have two projects, say Foo and Bar, both dependent from the library libBaz; actually at the beginning there was only Foo project, and now there is Bar project, and common code is refactored into libBaz library. All three of these are into

[CMake] Exclude source files from build for a specific configuration with Visual Studio

Hello, I am migrating a project from Visual Studio 8 to CMake and I look for a way to exclude files from build for a defined configuration. I think the "HEADER_FILE_ONLY" source file property can suit my needs and it would be great to have a "HEADER_FILE_ONLY_ version. But maybe there is a "work

Re: [CMake] problems with FindBoost

Dear Mike, Many thanks for your hint to enable debugging in FindBoost. Doing so I immediately located the culprit, and it seems it is not FindBoost that is to blame. The package using FindBoost was silently setting Boost_USE_STATIC_LIBS to ON behind my back, thus the DLL version was - properly - n

Re: [CMake] Extra options for strip?

On 03/28/2011 03:08 PM, Hariharan wrote: > I'm trying to build a stripped target using install/strip with the function > and line information retained. I need to pass the "--strip-debug" and > "--keep-file-symbols" to the system strip binary because the default is to > strip all symbols. Is there a