On Dec 05, 2006, at 1:11 PM, Jonathan Johnson wrote:
On Dec 5, 2006, at 1:46 PM, Björn Eiríksson wrote:
On Dec 5, 2006, at 7:41 PM, Jonathan Johnson wrote:
The issue is that 2006r3 did not support Universal Binaries, and
it's choking on the different Mach-O header. To create a plugin
that is compatible with r3 and prior, you need to put just a
PowerPC part in the "Mac Carbon Mach-O" folder, and the universal
part can live in a "Mac Carbon Mach-O Universal" folder. r4 will
prefer the part that lives in the Universal folder, but will fall
back on the part that lives in the Mach-O folder if that folder
isn't present. r3 however, has no knowledge of the Universal
folder, and thus things still work properly.
HTH,
Jon
Yes I know, I had this part correct. (And have had that right from
start from when the new folder was introduced, always publishing
both new and old part)
After I found that this was the only plugin behaving like this
then I at first compared it to other project, saw no difference,
then re-created the X-Code project file by copying the other
project and put the correct cpp files into it and finally got it
to not post that error. I am assuming here that the project file
was simply just corrupt in some way.
Oh, sorry about that, I didn't understand the situation fully.
Unfortunately in later versions of Xcode the setting is not
prominent. In 2.2 and prior, it was easily seen. In later versions,
I'm not sure where you can find the setting.
It might be worthwhile to ask on the Apple Xcode-users list if you
haven't already.
Which setting ?
The switch between two level name space and flat name spaces ?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
