http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19541
--- Comment #19 from Chris Litchfield <chris.litchfield at gmail dot com> 2010-12-08 16:10:47 UTC --- For now, we keep the -iquote in and hope the other parts are not removed. In our shop we have many different functions to try and mitigate the problem. Include files have #defines at the top to prevent the includes from being double included, use the proper syntax of #include <> and #include "" when appropriate. Hard coding the include path is just horrible for coding and deemed unacceptable for us. One of the workarounds is drastic but involves configuration management to the extreme. All source files and include files in the same directory and to verify that NO include files are ever duplicated. This can be done and use virtual designs for your "projects" in IDEs. Redesign of the Include files so they do not pull in other include files or have a layer of include files that include other files but when you change the sub-include files, it automatically pulls in the above layer include file. Yes, all these are ugly for something that should be part of ANY include system. There is a reason an Include Path exists, and to use "shortcuts" as standard practice inside the compiler hurts everyone here complaining about it. Quite a few developers just continue to use older compiler versions as no need to upgrade into some of the pain. Wish we could assign this to someone. I bet we could keep the needed option as a separate option (-I-). Dont know what this was last reconfirmed 2006 though... Chris (In reply to comment #18) > So there is no hope for this option then ? Anybody have a work around... We > are considering drastic measures to work around this. > > Thanks, > Chris > > > > From: "chris.litchfield at gmail dot com" <gcc-bugzi...@gcc.gnu.org> > > > To: Christopher Ferguson/Burlington/i...@ibmus > > > Date: 12/06/2010 03:14 PM > > > Subject: [Bug c/19541] need another option to support what -I- did just > besides -iquote > > > > > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19541 > > --- Comment #17 from Chris Litchfield <chris.litchfield at gmail dot com> > 2010-12-06 20:13:30 UTC --- > All versions since 4.0.0 seem to still have this issue. We are still > awaiting > it, and its not assigned to anyone either. > > -- > Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug.
