From: Alex Blekhman on 5 Nov 2009 11:20 "andrey the giant" wrote: > Looking at the output of cl /?, /o maps to /Fe, /Fo, /Fp > depending on presence or absence of /c, /E Also, you can use linker's /OUT switch to specify output file name. > I'm guessing the deprecation warning says "/o is undocumented, > use at your own risk". Being a UNIX guy, I'm used to using -o to > specify output. I think they keep this switch for compatibility with gcc. I personally have never heard of it. It is completely undocumented. Alex
From: Tim Roberts on 6 Nov 2009 01:30 andrey the giant <andrey.vul(a)gmail.com> wrote: > >Other compilers, such as gcc and icc, directly create the executable >from the source unless you run it in two stages: >$(CC) -c foo.c -o foo.o >$(CC) foo.o -o bar Actually, they don't. They run the two steps separately, then delete the object file afterward. >When I run VC9, $(CC) foo.c -o bar.exe creates foo.o, when I didn't >ask for it. Well, it creates foo.obj. Just embed an erase command in the makefile. -- Tim Roberts, timr(a)probo.com Providenza & Boekelheide, Inc.
First
|
Prev
|
Pages: 1 2 Prev: What is the share mode for fopen()? Next: using the string class with LoadString( ) |