« previous next »
Pages: 1 [2]  All   Go Down

Author Topic: Per compiler custom variables not expanded?  (Read 11430 times)

takeshimiya

  • Guest
Re: Per compiler custom variables not expanded?
« Reply #15 on: May 08, 2006, 08:31:31 pm »
Quote from: yop on May 08, 2006, 08:25:41 pm
Me too. If you change the QTDIR env var you can switch between Qt versions on the fly. It's obvious that I 'm intrested ;)
Same case here, but for wxWidgets. :)

If it gets done per-target, I could have different targets for different versions, different configurations and even different compilers, all without touching furthermore the project or anything else, just the WXCFG variables :)
« Last Edit: May 08, 2006, 08:35:43 pm by Takeshi Miya »
Logged

Offline yop

  • Regular
  • ***
  • Posts: 387
Re: Per compiler custom variables not expanded?
« Reply #16 on: May 08, 2006, 08:45:20 pm »
The more I think about it the more I like it. Setting the LD_LIBRARY_PATH in Linux if developing a shared object and more and more... How come we never thought about it?
Logged
Life would be so much easier if we could just look at the source code.

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Per compiler custom variables not expanded?
« Reply #17 on: May 08, 2006, 09:41:06 pm »
I've done it. A first version is available at:
http://forums.codeblocks.org/index.php?topic=3061.0
I don't have a linux system so this plugin needs testing - especially on linux.
...have fun with it, I hope I didn't implement too much errors... ;-)
With best regards, Morten.
Logged
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ
Pages: 1 [2]  All   Go Up
« previous next »