Bug #15440 2009-03-26 14:06
andwan0
Visual C++ 6.0 Import Incomplete
1. When importing a Visual C++ 6.0 workspace, it doesn't import the dependency information from the *.dsw file.
2. Sometimes it ignores the /def:"....def" link options so this doesn't get copied across.
3. It is importing the ADD BASE LINK32 lines too. It is not suppose to (according to Visual C++ 6.0 behaviour).
- Category
- Application::WrongBehaviour
- Group
- Status
- Closed
- Close date
- 2010-01-22 16:16
- Assigned to
- mortenmacfly
History
Cannot reproduce. What version? Did you try a nightly?
mortenmacfly wrote, "Cannot reproduce. What version? Did you try a nightly?"
I used Code::Blocks 8.02. No nightly. Please try to reproduce using release 8.02.
Ensure you have multiple projects within a Visual C++ 6.0 workspace (eg. 4 DLL projects & 1 EXE project). Then setup dependencies.
For the DLL projects, double-check you have /def:"....def" link options in the Visual C++ 6.0 project settings. This should be setup by default for standard DLL projects.
As you change link libraries over time... Visual C++ 6.0 adds changes on new ADD LINK32 lines... leaving the original base ADD BASE LINK32 intact. It seems Visual C++ 6.0 doesn't use the ADD BASE line... and the ADD LINK32 lines take precendence.
Code::Blocks 8.02 doesn't import DLL project dependencies, ignores /def:"....def" link options, and it imports all ADD LINK32 lines (including the ADD BASE LINK32 which it should ignore).
I won't try with 08/02. This makes no sense. We did modifications recently to the VC(6) importer. So most likely this bug is already fixed in a nightly version (which are also stable btw...) So again: Could you please try a nightly?
Report is closed.
Note: This is a preformatted standard message.
Possible reasons for closing this report are:
* the developer in charge of the issue
- could not reproduce it despite trying several times
- did not get sufficient information
- got no reply to an inquiry for specific information
* the report is quite a bit dated of now, and
- no user comments have been added for several weeks
- significant changes have been made to the code
- no other developer could reproduce it either
It is assumed that the problem does not persist and the report
can be closed.
If the problem reappears in future releases, please feel free to
re-open this report and provide precise information on how to
reproduce it.