Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

several issues with "open #include file ..."

<< < (5/7) > >>

MortenMacFly:

--- Quote from: killerbot on November 27, 2005, 10:51:31 am ---allrighty, here we go with the analysis of problem 2 : [...]

--- End quote ---
I am sorry, but can I ask to go a step back? I have somehow lost the point of this discussion. :( I have understood why you want to add the mingw version special directories (for the includes), but what are you trying to solve with the latest post? What is "problem 2"? Could you please explain this to me in a short proposal? That would help me... sorry.

Morten.

killerbot:
Morton,

As mentioned in the start of this thread :
The second problem is :
In the attached project switch to the digital mars compiler (includes path for that compiler are for example : C:\dm and c:\dm\stlport\stlport).
Save the project, close it, open it
The include paths of the digital mars are not added to the parser::AddIncludeDir(), once again it are the include paths of the gnu compiler which are added.

More details in my previous post on what goes wrong.
Shortly stated : project top level says gnu, target says digital mars -> so when I open include a c++ header , I should get the one from digital mars and not the gnu one.

Hope this makes it clear,
Lieven

MortenMacFly:

--- Quote from: killerbot on November 27, 2005, 11:55:01 am ---Hope this makes it clear,

--- End quote ---
It did, thanks. But: I cannot reproduce the issue you have explained. I've opened your project, compiled it with the default compiler (mingw). Then I changed the compiler for this project to Digital Mars. C::B complained I should recompile, so I did. I re-build the project which was now done with DM and worked. Then I closed C::B (and saved the changes  done to the project). I re-opened the project and re-build it again (without changin any settings). It was compiled with the DM compiler again and was still working also the include path's were set correctly to the ones of DM...

Am I still missing something?

Morten.

mandrav:
Hi Lieven

I think you 're over-complicating things. Not that what you said isn't true, but you have tied your thinking to the selected target which has nothing to do with the functionality of "open #include".
The way it is structured now, allows it to work even for single files, not belonging to a project.
Even if you 're only working with project files, you should be able to locate #includes in files not belonging to the project or the currently selected target.
With your suggestion, before using "open #include" in a file, I should manually select the file's target to work (and this wouldn't work always).

I have an easier solution for you.
Leave it as it is now, but instead of breaking out of the search when the first match is found, continue searching. If at the end of the search more than one files were located, display a nice selection dialog for the user to choose :)

killerbot:
Morton,

Yes you are missing a little thingy  :)

in one of the files do "open include file" on one of the c++ headers (or just type an #include <iostream> in one of the files and do it on that one). You won't be able to open it (that was problem 1 which I fixed, just grab the code attached somewhere above), and then with your recompiled version, try again, you'll end up in the wrong iostream header, the one from gnu not digital mars.
So COMPILING is OK, but the "open include file" funtionality is not.

Cheers,
Lieven

Navigation

[0] Message Index

[#] Next page

[*] Previous page