• 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: Undefined constants from pch
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Undefined constants from pch


  • Subject: Re: Undefined constants from pch
  • From: Steve Mills <email@hidden>
  • Date: Tue, 18 Apr 2006 14:57:22 -0500

On Apr 18, 2006, at 14:51, Óscar Morales Vivó wrote:

If the problem is that it's mangling the constants' names, it sounds like enclosing them in an extern "C" block should do the trick.

Failing that, you could always forget about all that and always force C++ compilation. If your C code isn't particularly weird, it should work fine (although paying a price in compile speed).

Not sure if this 3rd project can be compiled this way. Besides, that won't help explain why one project works and the other doesn't. We need to get to the root of this problem, not find hacks around it. Thanks anyway.


Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/


_______________________________________________ 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: 
 >Undefined constants from pch (From: Steve Mills <email@hidden>)

  • Prev by Date: Undefined constants from pch
  • Next by Date: Re: Codesense not working
  • Previous by thread: Undefined constants from pch
  • Next by thread: XCode 2.2.1 / gcc 4.0 Peephole Bug
  • Index(es):
    • Date
    • Thread