User forums > General (but related to Code::Blocks)
Moving to GCC question
klight:
Forgive my ignorance, but perhaps there is a different approach...
Why couldn't the MS project/workspace import do the work and add the required paths to the job file? While I realize this may be more work and may raise other issues, it would seem to be a less offensive approach to the core C::B design.
rickg22:
Hmmm interesting idea. It may work. Ok, let me jump into the bandwagon and suggest the addition of this flag in the project's build options.
--- Quote ---[ ] Add Extra search paths like MS-VisualStudio (WARNING: NOT recommended for cross-platform projects since it's not ISO-C++ compliant)
--- End quote ---
This flag could be set for importing MSVC projects :)
thomas:
--- Quote from: klight on January 19, 2006, 06:11:36 pm ---Forgive my ignorance, but perhaps there is a different approach...
Why couldn't the MS project/workspace import do the work and add the required paths to the job file? While I realize this may be more work and may raise other issues, it would seem to be a less offensive approach to the core C::B design.
--- End quote ---
That's not ignorance at all. That's the correct way :)
mandrav:
--- Quote from: thomas on January 19, 2006, 05:52:59 pm ---Because it is not right to add a path secretly. Although it will probably (hopefully) never cause a problem in this particular case, it still is not right. You don't know where it is inserted (first, last...?) either. Well, you would know if you looked at the sources, but the point is you don't even know that it is happening.
--- End quote ---
Well, I would normally agree with you but this is a case where it doesn't hurt. The reason is that what I added is "." (current dir) from the compiling-file's point of view. The current dir, unless overriden, is implicitely included in the search list. The only difference here is that because C::B uses the project's dir as the current dir, we "help" the compiler by adding the file's current dir in the list :).
I hope it makes sense the way I wrote it :P
tiwag:
@thomas : you are right, IT IS A BUG !!!
after updating CB to rev 1813 i tried to rebuild any of my plugin's and earned a lot of undefined symbols errors
after reverting /trunk/src/plugins/compilergcc/cmdlinegenerator.cpp to rev 1810 it behaves ok again !
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version