• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Compile file
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Compile file


  • Subject: Re: Compile file
  • From: "Jonathan Johnson" <email@hidden>
  • Date: Tue, 21 Feb 2006 20:46:51 -0600

On 2/21/06, Fritz Anderson <email@hidden> wrote:

> Then I am confused. What do you expect to get out of the double compilation?

I recently ran into this as well. When debugging a problem that is
inside of #if code for the other target (ie, an x86 assembly block),
using Cmd-K is misleading because it successfully "compiles" the file,
but then will fail on a full build. It seems like the two behaviors
should be synonymous in behavior -- if I'm currently working on
building a universal app, errors potentially can be in different code
paths in that file due to #if's.

So yes, it's the same parser, but it's different source because of the
preprocessor.

-Jon


--
Jonathan Johnson
REAL Software, Inc.

REAL World 2006, The REALbasic User's Conference
<http://www.realsoftware.com/realworld>
 _______________________________________________
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

References: 
 >RE: Compile file (From: "David Litwin" <email@hidden>)
 >Re: Compile file (From: Fritz Anderson <email@hidden>)

  • Prev by Date: Re: Compile file
  • Next by Date: Re: build failed, no diagnostic messages
  • Previous by thread: Re: Compile file
  • Next by thread: RE: Compile file
  • Index(es):
    • Date
    • Thread