RE: Compile file
RE: Compile file
- Subject: RE: Compile file
- From: "David Litwin" <email@hidden>
- Date: Tue, 21 Feb 2006 19:02:15 -0800
- Thread-topic: Compile file
I'm not sure why someone would think it was just running the parser on the
file, it does a compilation of the file, and as a result it generates a .o
(parser, optimizer, code gen). Basically exactly what I'd expect if I'm given
an option to "compile" the file.
But unless we have an option to select the architecture (like we can
select the configuration), it would be quite useful to be able to have it build
both. When half of my project won’t compile, I want to work file by file,
especially when it only fails on one architecture. Having it take effect in
the executable is hours or days of work away.
As to cross compilation doing no good under Debug I don’t agree. I currently
have it set to only the native architecture, but once I get into QA I’ll want
the debug version running on all machines, and that means a universal binary.
Dave
From: Fritz Anderson [mailto:email@hidden]
Then I am confused. What do you expect to get out of
the double compilation?
Under the Debug configuration, cross-compilation does
you no good, as you'll only be able to ZeroLink and debug in your native
architecture.
Under the Release configuration, cross-compilation
does you no good in a check compilation -- it's the same parser, so why run it
twice? If you want the results of the compilation to take effect in the
executable, then you have to do a full build anyway to link the application, so
you pick up the other architecture's compilation automatically.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden