Re: 64-bit AU
Re: 64-bit AU
- Subject: Re: 64-bit AU
- From: Jean-Daniel Dupas <email@hidden>
- Date: Fri, 22 Jan 2010 13:28:58 +0100
You have to export you Entry point. Make sure your entry symbol AUViewEntry is properly exported. Add _AUViewEntry in you .exp file and find what prevent the linker to works.
Le 22 janv. 2010 à 13:22, john smith a écrit : Ok, so auval -64 -a does not list my plug-in. What could cause this? Is it because I removed AUViewEntry from the .exp? Besides removing some carbon specific code (AUCarbonView etc.), that's basically all I did. Thanks, Michael Olsen
Subject: Re: 64-bit AU From: email@hiddenDate: Fri, 22 Jan 2010 13:17:51 +0100 CC: email@hiddenTo: email@hiddenLe 22 janv. 2010 à 13:03, john smith a écrit :
Hi,
so, I'm finally moving my code to 64-bit AU.
First step: Compile, link, and have the plug-in show up in AULab (running in 64-bit mode). Unfortunately that seems to be harder than expected.
Compiling and linking wasn't a big problem; removing the code that didn't compile (mainly file stuff).
I had a strange link error about _AUViewEntry, and I had to remove that from the .exp (is this the proper thing to do?).
That's all the changes I made. Unfortunately the plug-in doesn't show up in AULab.
Is there anything I should look out for? Any special requirements?
Also, I appear unable to figure out how to run auval in 64-bit mode. That way I might be able to get some runtime info from my plug-in.
man auval ?
OPTIONS -64 | -ppc must be specified first. can specify either: -ppc to run using Rosetta on Intel machine, or -64 to run as 64 bit. If neither specified runs as 32 bit native architecture
Windows Live: Make it easier for your friends to see what you’re up to on Facebook.
|
_______________________________________________
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