• 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: dialect specific warnings/WARNING_CFLAGS ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: dialect specific warnings/WARNING_CFLAGS ?


  • Subject: Re: dialect specific warnings/WARNING_CFLAGS ?
  • From: Chris Espinosa <email@hidden>
  • Date: Tue, 17 Mar 2009 15:00:00 -0700


On Mar 17, 2009, at 2:38 PM, Greg Guerin wrote:

It should also be doable by moving the source files into sub-targets that only compile, then a linking stage in another target, with target dependencies to the compile-only targets.

Still a mess, but a different category of messitude.

Xcode doesn't really do that. Compile into a static library, then link with that, sure. But you can't really make one target go and grab another target's .o files.


Chris
_______________________________________________
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: dialect specific warnings/WARNING_CFLAGS ? (From: Greg Guerin <email@hidden>)

  • Prev by Date: Debugger failure within layered subclasses
  • Next by Date: Per architecture file subsets in a Compile files build phase
  • Previous by thread: Re: dialect specific warnings/WARNING_CFLAGS ?
  • Next by thread: Problem sending data with CFHTTPMessage
  • Index(es):
    • Date
    • Thread