Question

Scenario: 1) I have Xcode project with C++ code and I have added third party dylib (xxxx.dylib) into it. Program runs fine without any issues. 2) Now I add one more dylib into the project named yyyy.dylib. I have just added it and did not use any functionality of it, meaning I just compiled my project once I have added it. 3) Now, one of the third party function call in first dylib (xxxx.dylib) fails because I added yyyy.dylib into the project. Failing here means, the function have some internal exception and I don't have source code to know whats going on. 4) Now if I remove second dylib (yyyy.dylib) and compile the project again, the function call of xxxx.dylib worked without any errors, thats how I find out that adding second dylib (yyyy.dylib) causing an issue.

Anybody have faced this kind of situation like this? I did not add code here because its all third party lib calls which fails. My guess here is there are some symbol clash between xxxx.dylib and yyyy.dylib internally causing this. Any clue?? Any suggestions?

Était-ce utile?

La solution

It seemed that, I had no other clue other than filing the bug with third party and upgrading to their new lib solved the issue.

Licencié sous: CC-BY-SA avec attribution
Non affilié à StackOverflow
scroll top