GCC output directory

[Gernot Frisch]

Might b e a bit OT, but I know there's lots of you who can help
quickly.

Is there any way to let gcc/g++ output the .o files in a folder I can
specify?

Thank you for not flaming,

-Gernot
int main(int argc, char** argv) {printf
("%silto%c%cf%cgl%ssic%ccom%c", "ma", 58, 'g', 64, "ba", 46, 10);}

[benben]

Gernot Frisch wrote:

Might b e a bit OT, but I know there's lots of you who can help
quickly.

Is there any way to let gcc/g++ output the .o files in a folder I can
specify?
What's wrong with g++ followed by a cp?

Thank you for not flaming,

-Gernot
int main(int argc, char** argv) {printf
("%silto%c%cf%cgl%ssic%ccom%c", "ma", 58, 'g', 64, "ba", 46, 10);}

[Ian Collins]

Gernot Frisch wrote:

Might b e a bit OT, but I know there's lots of you who can help
quickly.

Is there any way to let gcc/g++ output the .o files in a folder I can
specify?

-o is a common compiler switch to specify the output file name.

--
Ian Collins.

[Gernot Frisch]

Is there any way to let gcc/g++ output the .o files in a folder I
can
specify?

What's wrong with g++ followed by a cp?

in my case "mv". The files are generated in the directory of the
g++.exe. But the compiler directory might be read only to a normal
user, so it would be nice if I could tell it to use another one in the
first place...

[Owen Jacobson]

On Wed, 19 Apr 2006 11:45:55 +0200, Gernot Frisch wrote:

Is there any way to let gcc/g++ output the .o files in a folder I
can
specify?

What's wrong with g++ followed by a cp?

in my case "mv". The files are generated in the directory of the
g++.exe. But the compiler directory might be read only to a normal
user, so it would be nice if I could tell it to use another one in the
first place...

I think you'll find they're placed in the current directory, not the
directory containing gcc.