[Geany-devel] Windows Build commands

2012-08-27 Thread Lex Trotman
Hi Enrico or some other Windows dev,

Had a report on IRC from a new Windows Geany user that when they
installed Geany the C compile command was gcc -m32 “%f” -o “%e.exe”
which didn't work, but when they pressed the reset in the build
commands dialog the command changed to the normal gcc -Wall -o %e
%f which worked.

Is the build command being deliberately changed on windows builds or
is it something picked up from the build environment accidently?  And
if it is deliberate, it doesn't seem to work?

Cheers
Lex
___
Geany-devel mailing list
Geany-devel@uvena.de
https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel


Re: [Geany-devel] Windows Build commands

2012-08-27 Thread Matthew Brush

On 12-08-27 02:38 PM, Lex Trotman wrote:

Hi Enrico or some other Windows dev,

Had a report on IRC from a new Windows Geany user that when they
installed Geany the C compile command was gcc -m32 “%f” -o “%e.exe”
which didn't work, but when they pressed the reset in the build
commands dialog the command changed to the normal gcc -Wall -o %e
%f which worked.

Is the build command being deliberately changed on windows builds or
is it something picked up from the build environment accidently?  And
if it is deliberate, it doesn't seem to work?



On Windows 7 it's the normal command from filetypes.c or whatever, but 
I'm using built from Git, maybe release installer is different.


Cheers,
Matthew Brush

___
Geany-devel mailing list
Geany-devel@uvena.de
https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel


Re: [Geany-devel] Windows Build commands

2012-08-27 Thread Frank Lanitz
On Tue, 28 Aug 2012 07:38:52 +1000
Lex Trotman ele...@gmail.com wrote:

 Hi Enrico or some other Windows dev,
 
 Had a report on IRC from a new Windows Geany user that when they
 installed Geany the C compile command was gcc -m32 “%f” -o “%e.exe”
 which didn't work, but when they pressed the reset in the build
 commands dialog the command changed to the normal gcc -Wall -o %e
 %f which worked.
 
 Is the build command being deliberately changed on windows builds or
 is it something picked up from the build environment accidently?  And
 if it is deliberate, it doesn't seem to work?

Are you referring to filetypes.c and the preconfigured command for
compiling? If yes: This hasn't changed for 6 years according to blame
and I don't know of any Windows-special-setup here. 

Cheers, 
Frank


-- 
http://frank.uvena.de/en/


pgpKit4Gk4Xap.pgp
Description: PGP signature
___
Geany-devel mailing list
Geany-devel@uvena.de
https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel