Re: [Shapefusion-devel] 0.3 release

[tiennou <tie...@gm...>]

Le 30 mars 07 =C3=A0 19:44, Tito Dal Canton a =C3=A9crit :

> I tried to build 0.3 on MacOS X, but failed. I can't really say =20
> Xcode is
> my friend...
>
> The first problem I experienced was a strange duplication in source
> compiling: each .cpp was being compiled twice. This resulted in an
> infinity of multiply-defined symbols at linking. This happened because
> the Xcode project is configured to build for "ppc" and =20
> "NATIVE_ARCH". Of
> course I'm building on ppc; apparently Xcode isn't smart enough to
> understand that it should build once, and panics. I guess you =20
> should put
> "ppc" and "intel" instead. Can you do this and commit?

Yes, you're right, I didn't thought of this when putting ppc $=20
(NATIVE_ARCH) in the settings.
It should be $(NATIVE_ARCH) for Debug and ppc i386 for Release. I'll =20
change this...

> After this correction building still failed because my wx is =20
> configured
> as static linking only (as far as I remember). So I tried to replace
> libwx_mac with libwx_mac_static in the ShapeFusion project. Xcode was
> happier but still failed to build, complaining about a couple =20
> undefined
> symbols. I couldn't solve this.

I've set things such that you just need to put wx 2.6.3 sources next =20
to shapefusion...
It's right I link with the shared wx, but you can change this by =20
checking the libwx_mac_static.a instead of the libwx_mac.dylib. Only =20
that static linking in Development makes a 140meg Shapefusion, which =20
hogs my computer at link time, so I prefered the dynamic way...
I added a small script to copy the dylib to the Frameworks folder =20
automatically, this was the step I forgot.

> I think I'll release regardless, but I'd feel better if you could fix
> the first problem.

I'm testing a full build (Development & Deployment) before I commit. =20
No problem, I just got prebinding disabled because wx overlaps with =20
Shapefusion...
tiennou