It turns out that the problem was that the INSTALL project is not set to build in the Project Configuration manager. This is usually the desired behavior but it's what I was trying to work around - checking the build box for the INSTALL project in the configuration manager does exactly what I want.
I can still have the default project set to the app that I want to debug, but a build command will always trigger an install, whether it's the exe or a shared lib that was rebuilt. Sam -----Original Message----- From: Bill Hoffman [mailto:[EMAIL PROTECTED] Sent: Friday, October 31, 2008 1:13 PM To: Sam Baker Cc: Eric NOULARD; [email protected] 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 default. That does work and I can still debug as long as I tell it where the exe is. > > That doesn't work so well for my more complex Tools project that has multiple executables in the solution since I then need to switch default projects to debug different apps but I can put up with that for now and look at the add_custom_command options later. > > Is it possible to build the solution's INSTALL project as a post > build step for a target? I realize that may not make much sense outside of visual studio projects. The install is specific to the game whereas the libraries shouldn't be building with knowledge of the game so the coupling isn't ideal. > > Thanks again! > I don't think most folks would want this. You can right click on a target in vs and build it, you don't have to make it the default project. For most developers, you do lots of building and testing before you install, and they would not want to install every time. -Bill Big Fish Games, Inc. A New Game Every Day! _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
