Re: [CMake] Building out of source

2008-12-05 Thread Sam Baker
I have a folder for project files only (everything that CMake creates). To build to that folder I just run cmake from that folder. I have: cpp/project_files/tools cpp/project_builds/tools cpp/source/tools The CMakeLists.txt is in cpp/source/tools. I run CMake from cpp/project_file

Re: [CMake] Visual Studio debbuging working directory

2008-11-07 Thread Sam Baker
There was a post on this a while ago that you can find with the right google search - apparently it's not possible because the working directory is stored in your solution's *.suo user options file which is saved by Visual Studio for each solution. CMake doesn't generate those and isn't able to eas

Re: [CMake] Visual Studio dependency/auto-install help

2008-10-31 Thread Sam Baker
2008 1:13 PM To: Sam Baker Cc: Eric NOULARD; cmake@cmake.org Subject: Re: [CMake] Visual Studio dependency/auto-install help Sam Baker wrote: > Thanks Eric - I'm so used to having the executable project be the default project for debugging, I didn't think of making the INSTALL project

Re: [CMake] Visual Studio dependency/auto-install help

2008-10-31 Thread Sam Baker
EMAIL PROTECTED] Sent: Friday, October 31, 2008 12:48 PM To: Sam Baker Cc: cmake@cmake.org Subject: Re: [CMake] Visual Studio dependency/auto-install help Le Fri, 31 Oct 2008 11:58:53 -0700, "Sam Baker" <[EMAIL PROTECTED]> a écrit : > When generating MSVS solutions, is there a

[CMake] Visual Studio dependency/auto-install help

2008-10-31 Thread Sam Baker
When generating MSVS solutions, is there a way to make all library projects automatically build the solution's INSTALL project when done? I have a game executable and a bunch of DLLs in my solution. When my game builds, I have a post-build step that copies the exe file and the library DLLs t

Re: [CMake] Semicolons in command options

2008-10-21 Thread Sam Baker
Change your set command to set (FOO "one;two;three") The ; notation without quotes is used for declaring lists of strings. With quotes, FOO will be a single string instead. Sam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric (Brad) Lemings Sent: Tu

Re: [CMake] CPack NSIS installer requires CPACK_PACKAGE_EXECUTABLES entry?

2008-10-19 Thread Sam Baker
Sam From: David Cole [mailto:[EMAIL PROTECTED] Sent: Friday, October 17, 2008 4:10 PM To: Sam Baker Cc: cmake@cmake.org Subject: Re: [CMake] CPack NSIS installer requires CPACK_PACKAGE_EXECUTABLES entry? On Thu, Oct 16, 2008 at 4:25 PM, Sam Baker <[EMAIL PROTECTED

[CMake] CMAKE_INSTALL_PREFIX not working in Visual Studio

2008-10-18 Thread Sam Baker
In my project file I have near the top of the file, the line: set(CMAKE_INSTALL_PREFIX ${APP_INSTALL_DIR}/MyApp) Which I thought would force all install destinations to be relative to that directory. Later in the same CMakeLists.txt file, I have some install commands: INSTALL(TARGETS My

[CMake] CPack NSIS installer requires CPACK_PACKAGE_EXECUTABLES entry?

2008-10-16 Thread Sam Baker
I'm using CPack (CMake 2.6.2) for the first time and I have a flat install directory with my executable and some dlls. I want my start menu shortcuts (Win XP) to run the executable from the install folder and not from a bin subfolder. It appears that: - CPACK_PACKAGE_EXECUTABLES onl