Author Topic: Compiler detection  (Read 2868 times)

vagy

  • Guest
Compiler detection
« on: October 05, 2007, 09:49:49 pm »
Hi guys,
first post in the list so let me congratulate you for your nice project! Thanx for sharing it.
It happened to run the latest nightly build (1st October one) in two different Windows machines.
The first has its system drive as C: and the second as G:. Both machines have the cygwin
dev environment installed. The detection of cygwin gcc in the machine with the C: system
drive was successful while on the one with the G: system drive it wasnt. Makes me think
your code may assume the system drive is C: (?). If thats the case i would suggest to have
your code ask windows whats the system drive and then run the detection method on it.

Friendly,

Vagelis

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9614
Re: Compiler detection
« Reply #1 on: October 06, 2007, 11:26:51 am »
Makes me think your code may assume the system drive is C: (?).
Nope. Cygwin detection is based on querying the registry. If Cygwin is properly installed this will succeed. Hence if Cygwin is (e.g.) copied only than there is no registry entry to query. In that case C::B assumes the default installation directory which is C:\Cygwin. There is no *good* other way for the detection than this.
With regards, Morten.
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