-
May 30th, 2006, 04:42 PM
#1
Per-configuration dependencies
I have a workspace with two projects, MyProj and MyLib.
MyProj uses code from MyLib, so I have established a dependency. It works. When I compile the Win32 Debug build of MyProj, the Win32 Debug build of My Lib is compiled if needed. Likewise for the Win32 Release builds.
I now want a slightly different look and behavior for MyProj. I have created Win32 MyProjMod Release and Win32 MyProjMod Debug configurations with some different settings.
The dependencies do not work. When I compile either of the MyProjMod builds, it is always the Win32 Debug build of MyLib that is compiled.
How do I fix this?
I see there is an Allow per-configuration dependencies checkbox in Project Settings / General, but it doesn't seem to help.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|