Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Duplicate Symbol Error: SBJsonParser.o?

I currently have ShareKit in my project that is compiled as a static library. It is properly implemented. I also have implemented Amazon's AWS SDK by just adding their framework into my project.

It seems that the duplicate symbol is coming from Amazon's AWS SDK file, "AWSIOSSDK". This is what it looks like:

enter image description here

And that file is colliding with ShareKit's file, libShareKit.a. This is what that file looks like:

enter image description here

Anyway both of these files are ones that I haven't seen before. And it seems that some JSON files are colliding within them.

I have looked at other SO questions and they say to do some things with the compiled sources but none of these files are in the compiled sources from either library.

Here is the exact error Xcode gives:

ld: duplicate symbol _OBJC_CLASS_$_SBJsonParser

Anyway, does anyone have any ideas what I should do? My app does not compile unless I fix this issue.

Thanks!

like image 920
SimplyKiwi Avatar asked Jul 22 '12 20:07

SimplyKiwi


2 Answers

You could go ahead and split a library archive into its object files and merge them again by leaving out the duplicates.

See the following walkthrough for getting an idea to manage that task: Avoiding duplicate symbol errors during linking by removing classes from static libraries

like image 83
Till Avatar answered Oct 04 '22 09:10

Till


Both of these have built SBJsonParser into their static libraries. This is not the correct way to build a static library. Each should build without SBJson and then you should link all of them together with SBJson. There are a couple of solutions:

  • Rebuild these libraries (or have their maintainers do so) to not include third-party libraries directly into a static library. This is the ideal solution.
  • Remove the incorrect SBJson files from the .a files using ar. You should be able to do this using ar -t to list the objects in the .a and then ar -d to delete the ones that shouldn't be in there. You could of course also ar -x to extract all the .o files and link them directly.
like image 40
Rob Napier Avatar answered Oct 01 '22 09:10

Rob Napier