Bug #11621 2007-07-24 01:49

sarkar112

GCC is started in wrong directory

A variety of command line options act irregularly, such as -S or --save-temps, due to the fact that a call to gcc is placed from the CodeBlocks installation directory to compile the application, when regularly, a call to GCC should be placed from the directory that the source code is in.

Category
Compiler
Group
 
Status
Closed
Close date
2007-07-27 17:37
Assigned to
biplab

History

biplab 2007-07-25 16:53

It works in my PC. If possible, please provide more details to reproduce this

sarkar112 2007-07-25 20:57

Specify --save-temps as a compiler argument and check the codeblocks installation directory (the directory codeblocks.exe is in).

sarkar112 2007-07-25 21:01

Sorry: Specify --save-temps as a compiler argument, compile a file that compiles regularly which is not in a project, and check the codeblocks installation directory (the directory codeblocks.exe is in). On my PC, the compilation results are as follows: The object file and the executable file in the directory the compiled source code is in, and *.ii/*.s end up in CodeBlocks installation directory.

biplab 2007-07-26 10:16

If a file is not part of any project, gcc is run with minimum commands. So the -save-temps may not be passed correctly to GCC.

Create a project and add the compiler option in the *Project > Build options*. This should solve your problem.

biplab 2007-07-27 17:37

I'm closing this thread. You may post a Feature Request on this explaining in details.

Thanks for ur feedback.