Author Topic: C++ parser options. Is portable solution?  (Read 1854 times)

Offline blockn102

  • Single posting newcomer
  • *
  • Posts: 7
C++ parser options. Is portable solution?
« on: October 25, 2008, 04:39:15 am »
I think CB save the path of "C++ parser options" in cbp file is not good.

My solutions:
  • Add Global C++ parser options
  • Detect path by name of project (or regex match)

Example, I have a project wxWidgetsProject1. Global C++ parser:
Code: [Select]
wxWidgets* => C:\src\wxWidgets, C:\src\boost
My friend settings:
Code: [Select]
wxWidgetsProject1 => E:\wxWidgets, E:\boost
Code: [Select]
codeblocks => E:\wxWidgets, E:\codeblocks\devel
This solution is easy to share project, group work.

Thanks for read this.

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: C++ parser options. Is portable solution?
« Reply #1 on: October 25, 2008, 01:38:37 pm »
I think CB save the path of "C++ parser options" in cbp file is not good.
...that's exactly why global compiler variables (GCV) were introduced. Read about this concept in the Wiki. It will resolve your issues and even more... ;-)
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ