Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: jmccay on July 22, 2006, 08:53:06 pm

Title: Strange behavior....or default behaivor?
Post by: jmccay on July 22, 2006, 08:53:06 pm

CB: Version 1.0 revision 2610 () gcc 3.4.5 Windows/unicode

I don't know if this is known, fixed, on purpose, or what, but I wanted to post it.  I just noticed something.  Under:

Compiler & Debugger setings -> programs

If you set the directory to a directory where the mingw compiler is not located (such as c:\test_MinGW), C::B still compiles fine as long as there is a compiler in the default mingw location (C:\MinGW).  Is this on purpose?  If so, you might want to note that this behaivor is the default somewhere on the dialog.  It would help people when there may be using mulitpl version of a compiler.

   Does it always use C:\MinGW?  Or does it just search there when it can't find the compiler in the directory specified?

   Anyways, Great work, and like the games.
jmccay

Title: Re: Strange behavior....or default behaivor?
Post by: sethjackson on July 22, 2006, 11:04:32 pm

Quote from: jmccay on July 22, 2006, 08:53:06 pm

CB: Version 1.0 revision 2610 () gcc 3.4.5 Windows/unicode

I don't know if this is known, fixed, on purpose, or what, but I wanted to post it.  I just noticed something.  Under:

Compiler & Debugger setings -> programs

If you set the directory to a directory where the mingw compiler is not located (such as c:\test_MinGW), C::B still compiles fine as long as there is a compiler in the default mingw location (C:\MinGW).  Is this on purpose?  If so, you might want to note that this behaivor is the default somewhere on the dialog.  It would help people when there may be using mulitpl version of a compiler.

   Does it always use C:\MinGW?  Or does it just search there when it can't find the compiler in the directory specified?

   Anyways, Great work, and like the games.
jmccay

Hmm well I think it is a bug. I don't like programs hiding things from the user......

Title: Re: Strange behavior....or default behaivor?
Post by: tiwag on July 23, 2006, 07:48:56 am

Quote from: jmccay on July 22, 2006, 08:53:06 pm

...   Does it always use C:\MinGW?  Or does it just search there when it can't find the compiler in the directory specified?  ...

are you sure, you do NOT have the path to MinGW ( "C:\MinGW" ) somewhere in your PATH variable defined ?

Title: Re: Strange behavior....or default behaivor?
Post by: jmccay on July 25, 2006, 02:50:49 am

Quote from: tiwag on July 23, 2006, 07:48:56 am

are you sure, you do NOT have the path to MinGW ( "C:\MinGW" ) somewhere in your PATH variable defined ?

You are correct.  I forgot to check the user PATH variable--I looked at the system PATH variable.  Actually, I didn't know you could have a user specific PATH variable.  I only thought it was a system specific.  Sorry.  This is not an issue.  I didn't think it was possible to put something that obvious in without someone else noticing.
jmccay