XCode conversion problems with VST plugin
XCode conversion problems with VST plugin
- Subject: XCode conversion problems with VST plugin
- From: Jeff DuMonthier <email@hidden>
- Date: Sun, 16 May 2004 20:32:23 -0400
I am having major problems converting a VST plugin (bundle) from
Project Builder to XCode 1.2 under 10.3.3. I'm past the file not found
and path interpretation changes to the point of actually getting it to
build, but when I try to start a host which loads it I just get an
immediate crash. The old versions build with PB under 10.2 still work
under 10.3.3 with the hosts I am using to test.
On the VST mailing list I saw posts about this being due to linking
against the 10.3 SDK by default and exporting too many symbols. After
more work than it should have taken I think I have converted to the
10.2.8 SDK. I changed the cross development SDK in the Project
inspector. I changed the deployment target in the targets to 10.2. I
changed the paths of the frameworks and libstdc++ to their 10.2.8 SDK
locations, then unchecked and rechecked them to get the right search
paths in the target. I added the -nostdinc and -nostdinc++ flags to
the other c/c++ flags so that my include paths according to the -v
output are only:
#include "..." search starts here:
#include <...> search starts here:
/Developer/SDKs/MacOSX10.2.8.sdk/usr/include/gcc/darwin/3.3/c++
/Developer/SDKs/MacOSX10.2.8.sdk/usr/include/gcc/darwin/3.3/c++/ppc-
darwin
/Developer/SDKs/MacOSX10.2.8.sdk/usr/include/gcc/darwin/3.3/c++/
backward
/Developer/SDKs/MacOSX10.2.8.sdk/usr/include/gcc/darwin/3.3
/Developer/SDKs/MacOSX10.2.8.sdk/usr/include
I had some problems getting the library search path for libstdc++ to
"$(SYSTEM_DEVELOPER_DIR)/SDKs/MacOSX10.2.8.sdk/usr/lib/gcc/darwin/3.3"
because it kept coming up ".../3.1", but after some manual intervention
I no longer see the 3.1 path on the linker command. When I tried to
add the -Z linker option to make sure no 10.3 system libraries were
being linked against I get this one error I don't understand or know
how to work around:
ld: can't locate file for: -lbundle1.o
I can't find a file like that anywhere either, so I can't specify a
path explicitly and can't build with that option.
I'm not sure whether I should be setting the library style to bundle,
static or dynamic. Bundle would seem the logical choice since that is
what I am building, but all three build and none of them work. I have
tried eliminating all code optimization and targeting only a generic
PPC with no instruction scheduling. I have tried turning off fix and
continue and prebinding. Since the native targets I am using were
created from legacy targets which worked under PB/10.2 I have to assume
any other relevant options copied over. BTW, the legacy targets also
build but crash.
Any suggestions for something to try that I have not already mentioned?
Is there a way to use the debugger with a plug-in bundle?
-Jeff DuMonthier
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.