Symbol stripping on OS X
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 25/09/2012 at 11:14, xxxxxxxx wrote:
Originally posted by xxxxxxxx
Hi. I've been trying to get Xcode working with Cinema, I;ve got 3.2.6 running on my Mac right now and the R13 SDK examples refuse to build but the R13 Demo SDK examples build without a problem on the first try. I've been reading through a lot of posts about getting Xcode to work, but I didn't see anything about the demo version working when the actual release one won't. Could it still be my Xcode having the incorrect settings or would my R13 SDK examples be wrong? Dan
Please don't hi-jack other threads; stay at the thread you've opened with your question and make that one as descriptive as possible.
Best regards,
Wilfried
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 12/10/2012 at 20:36, xxxxxxxx wrote:
I made the changes to my projects but kept getting the strip failure error that Robert was getting. I don't use any functionality of R13/R14, so the latest builds of my plugins are R12... so a lot of the info in these instructions don't apply to my current plugins. It didn't matter if I used xcode 3.1.4 or 3.2.6, the error popped up and symbol stripping didn't occur (though, ironically, I sent one of these builds to someone who was having trouble with one of my plugins and their response was "hey, working perfectly, thanks!" and I haven't heard anything to the contrary from them and they're actively using it on a project).
I started messing with some other symbol related project settings out of frustration and got a "strange" error about not being able to use both unexport and export lists. So this is what I did to get a successfully stripped R12 build (out of both 3.1.4 and 3.2.6) :
Uncheck "Separately Edit Symbols"
Delete the path for "Unexported Symbols File"I tested this using clean cinema4dsdk projects from both R12 and R13 (so those settings were changed from default).
-kvb
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 13/11/2012 at 01:34, xxxxxxxx wrote:
Hi,
does anyone know where I could find the SDK 13.061 recommended by Maxon to build plugins for C4D R14 without these symbol stripping problems ??
We can't update our plugins on MacOS for now because it crashes C4D at startup...
Any help would very appreciated.
I didn't find the SDK on http://beta.villa.maxon.net/, there is a post about an update for the SDK 13.061 but it does not contain any download link.
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 13/11/2012 at 03:32, xxxxxxxx wrote:
Originally posted by xxxxxxxx
Hi,
does anyone know where I could find the SDK 13.061 recommended by Maxon to build plugins for C4D R14 without these symbol stripping problems ??We can't update our plugins on MacOS for now because it crashes C4D at startup...
Any help would very appreciated.
The SDK 13.061 is the SDK that comes with R13.061. Update your installed CINEMA R13 to this version.
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 13/11/2012 at 03:32, xxxxxxxx wrote:
Originally posted by xxxxxxxx
Originally posted by xxxxxxxx
Hi,
does anyone know where I could find the SDK 13.061 recommended by Maxon to build plugins for C4D R14 without these symbol stripping problems ??We can't update our plugins on MacOS for now because it crashes C4D at startup...
Any help would very appreciated.
The SDK 13.061 is the SDK that comes with R13.061. Update your installed CINEMA R13 to this version.
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 13/11/2012 at 08:45, xxxxxxxx wrote:
Thanks, but I have another question: what is the address of the update server? By default I have bugslife.maxon.de:80. Is it correct ?
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 13/11/2012 at 09:54, xxxxxxxx wrote:
Originally posted by xxxxxxxx
Thanks, but I have another question: what is the address of the update server? By default I have bugslife.maxon.de:80. Is it correct ?
Please post your questions about Beta in the appropriate forum. All the information is here.
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 12/12/2012 at 15:41, xxxxxxxx wrote:
Hi Wilfried,
Originally posted by xxxxxxxx
- Use XCode 3.1.x only if you want to create plugins for R12 and with the R12 SDK. Check the compiler/linker log for messages indicating that stripping doesn't work anymore and use "nm" to verify that new/delete isn't exported. Don't use XCode 3.2.x or newer to create plugins with the R12 SDK.
I got a system set up now that I downgraded to use XCode 3.1.4 so I can do as you indicated above. It's for compiling a plugin which doesn't need any SDK functionality above R12 and that way we have one binary distributable for R12-R14. Doing as you advised still doesn't seem to work, though. I used the R12.48 SDK and there are still new and delete operators getting exported.
Did this work for anyone else?
Best
Timm -
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 13/12/2012 at 00:09, xxxxxxxx wrote:
Originally posted by xxxxxxxx
Hi Wilfried,
Originally posted by xxxxxxxx
- Use XCode 3.1.x only if you want to create plugins for R12 and with the R12 SDK. Check the compiler/linker log for messages indicating that stripping doesn't work anymore and use "nm" to verify that new/delete isn't exported. Don't use XCode 3.2.x or newer to create plugins with the R12 SDK.
I got a system set up now that I downgraded to use XCode 3.1.4 so I can do as you indicated above. It's for compiling a plugin which doesn't need any SDK functionality above R12 and that way we have one binary distributable for R12-R14. Doing as you advised still doesn't seem to work, though. I used the R12.48 SDK and there are still new and delete operators getting exported.
Did this work for anyone else?
Best
TimmThen it might have already been broken in XCode 3.1.4; can't say for sure, as I have neither the required OS nor this XCode version to check - you should check the build log for this message:
"[…] nmedit: removing global symbols from a final linked no longer supported. […]"If it is there, the XCode version you're using was already broken.
What I can say for sure is: We used XCode 3.1 (3.1; not 3.1.2 or 3.1.3 or 3.1.4) to build R12 and checking the plugins/modules distributed with R12 shows, that symbol stripping was working there. If you can't get rid of the new/delete symbols, then DON'T use this plugin with R13 or R14 (instead build an extra version based on the 13.061 SDK that can be used with R13 & R14).
Best regards,
Wilfried
-
On 13/03/2013 at 07:38, xxxxxxxx wrote:
OK, I'm lost. I tried several combinations of Xcode and project files (even the projects that come with the c4dsdk project) and I consistently failed to compile a single dylib that did *not* export new and delete. Is there any Xcode Wizz here that is close to either Düsseldorf, Berlin or Munich and could have a (paid) day to spare to figure this out with me?