• 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
AU exporting different symbols for different architectures
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AU exporting different symbols for different architectures


  • Subject: AU exporting different symbols for different architectures
  • From: Kieran Tyrrell <email@hidden>
  • Date: Wed, 17 Nov 2010 13:42:46 +0100

Hi,

When using an exports file with an Audio Unit with a Cocoa and a Carbon view, we're getting the problem that when the linker tries to link the x86_64 part of the binary it can't find (obviously) the Carbon View entry point (because it's not there).

Is there a way to use two exports files in Xcode, one for i386 linking and another for x86_64?

Alternatively, can we create a dummy carbon view entry point that does nothing on x86_64 to satisfy the linker and exports file, or is there a chance that some hosts might try to use this if it's there?

I realise I can just forget about the exports file and export everything (as a lot of other AUs seem to do), but can't help feeling that's a bit messy :P

Cheers, Kieran.

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: AU exporting different symbols for different architectures
      • From: Kieran Tyrrell <email@hidden>
  • Prev by Date: Re: HostCallback_GetBeatAndTempo malfunction in Logic?
  • Next by Date: Re: Issue with Logic 64bits bridge and cocoa UI
  • Previous by thread: Re: AU Callback on a separate thread ? How ?
  • Next by thread: Re: AU exporting different symbols for different architectures
  • Index(es):
    • Date
    • Thread