Re: AU Universal Binary no worky on Intel
Re: AU Universal Binary no worky on Intel
- Subject: Re: AU Universal Binary no worky on Intel
- From: William Stewart <email@hidden>
- Date: Tue, 6 Feb 2007 11:19:42 -0800
If you use the template from XCode, then it should just be a matter
of filling in the information in the .r file in the project and the
resources should build for you. It decides which resource flavours to
publish (ppc, i386) based on the architectures that you chose when
building.
Bill
On 05/02/2007, at 9:47 PM, Chris Johnson wrote:
OK, so I seriously need help.
I've made a bunch of AU plugs- at the moment, _exclusively_ AU
plugs, if that amuses Cupertino any- eighteen AU plugs, some of
which are awfully competitive sound-wise with anything else out
there. I have spent years working on DSP code, but only recently
got into C++ and plugin authoring. That's why I suddenly have 18
plugs and more in the channel- I had all the DSP code already and
it's just a matter of porting.
I've got them working great- on PPC, which I'm building them on.
I've got a free plug (Channel) of which the latest build is at
http://www.airwindows.com/f/Channel.dmg and I'm using it to gauge
whether the plugs- based on the AU templates, neither Carbon or
Cocoa views, and with CAVectorUnit.cpp and CAVectorUnit.h included
under 'Source' to get them to compile... will run on Intel, which I
don't have.
The guys trying to run it are having no joy at all. It just
doesn't work.
I've tried OTHER_REZ_FLAGS -d ppc_$ppc -d i386_$i386
I've tried OTHER_REZ_FLAGS -rd -d ppc_$(ppc) -d i386_$(i386) for
good measure, though I can't find what this all means, quite.
I've got Architectures as ppc i386
I've got SDK Path as /Developer/SDKs/MacOSX10.4u.sdk
One user provided an auval failure log:
Last login: Mon Feb 5 23:04:44 on ttyp1
Welcome to Darwin!
MacBook-Pro:~ msc$ auval -v aufx chnl Dthr
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
AU Validation Tool
Version: 1.1.2c11
Copyright 2003-4, Apple Computer, Inc.
Specify -h (-help) for command options
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
--------------------------------------------------
VALIDATING AUDIO UNIT: 'aufx' - 'chnl' - 'Dthr'
--------------------------------------------------
ERROR: Cannot get Component's Name strings
ERROR: Cannot get Component's Info strings
ERROR: Error from retrieving Component Version for resource: -3000
* * FAIL
--------------------------------------------------
TESTING OPEN TIMES:
FATAL ERROR: didn't find the component
MacBook-Pro:~ msc$
I've also run lipo on the component and ascertained that it does
have Intel code in it, it's just not helping.
All these plugs (including this tester) run fine on PPC- in fact
they're pretty resilient because I'm careful to check for improper
startup conditions, which seem to pop up in odd places (certain
array references I have to manually boundscheck because they can't
be trusted to be sane). What is going on that this universal binary
build cannot be made to work for my users?
Oh- and hello- hopefully when I've sorted out my own headache
maybe I can occasionally be of help to others in turn :)
Chris Johnson
airwindows
_______________________________________________
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
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
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