Community
Participate
Working Groups
The platform has the notion of one project referencing another. CDT has a more detailed set of relationships that takes into account the CDT build-configuration concept. CDT's launch delegates only consider the platform relationships. It should use the CDT ones. Steps to reproduce problems 1. Create a project p1. By default it has build configurations Debug and Release 2. Create a project p2. By default it has build configurations Debug and Release. 3. Give p1/Debug a reference to p2/Debug in project Properties > C/C++ General > Paths and Symbols > References 4. Do NOT give p1/Release a reference to p2/Release 5. Create a launch configuration for p1, and specify project "p1", build configuration "Debug" in the Main tab 6. Make a change to the source file in p2 but do not save the file 7. Invoke the launch configuration. You'll get a dialog asking if you want to save the file in p2. That's expected. 8. Cancel 9. Change the launch configuration to refer to build configuration "Release" of project p1. 10. Invoke the launch configuration You'll get a dialog asking if you want to save the file in p2. That's shouldn't happen. p1/Release does not have a reference to p2 so the launcher shouldn't check to see if there are any unsaved files in p2.
