Xcode 5 compile errors linking to libraries

Question

Level 1

0 points

Xcode 5 compile errors linking to libraries

I am trying to compile an s/c application created by a intern that has left the company. On one mac the software compiles and links ok, but on my mac it does not, see below. Basically I am using MailCore.xcodeproj, Base64, SFHFkeychainUtils, and URLencode. All the libraries are giving me a O Linker (id) error saying the directory doesn't exist or Unknown X. ssl for example is saying things like "Unknown type name 'XSym', RSA, etc for every class. Why on this Mac does the code not compile while on the other mac it does? Neither of use has used Xcode before and we can't get enough information from the error messages to have any idea what is going on. The SA says both mac have the save software. I am sure this is some install / compile problem with the imported libraries required on this MAC.

xcode 5

Mac OS X 10.9.1

The software is from a CD where the app software directory was copied too.

This is the link/compile errors I am getting on my MAC. Doesn't happen on the other Mac. I have been google over a week with out success. If you need more info let me know.

<E-mail Edited by Host>

iPhone 4, iOS 6.1

Posted on Feb 11, 2014 6:40 AM

Reply

Answer 1

Feb 11, 2014 6:53 AM in response to john kerich

First guess is that the other machine has the libraries and your machine does not, if it really is a library problem.

What machine was the intern working on? If the breakup was not acrimonious the easiest thing is to contact the intern an ask what was done.

From the looks of it it appears you do not have the header file included. Do you get any errors about a missing header file?

Did you copy over everything from the other machine, the entire project?

Reply

Answer 2

john kerich Author

Level 1

0 points

Feb 11, 2014 7:40 AM in response to Frank Caggiano

What machine was the intern working on? If the breakup was not acrimonious the easiest thing is to contact the intern an ask what was done.

The intern help get the application working on the over person PC before he left. There is no contact information of course. David, the other mac people, did not write down any notes or remember anything that might have been modified. It was in the spring of 2013 when this happened.

From the looks of it it appears you do not have the header file included. Do you get any errors about a missing header file?

If there is headers missing its not saying. Since so many variables are unknown I assume something is missing but I don't have a clue what. I assume the 4 libraries are all there under the source code and are trying to link to something. If you max out the picture you should see the type of error message I am getting per lib. See picture 2. The required libs are all under CFNetwork.framework so they should be there.

Did you copy over everything from the other machine, the entire project?

I copied the applications source code folder there should have include all files required to compile. I am just starting to look the the "Linked Framworks and Libraries" section to see if the path is somehow not pointing to the correct locations, but sinces these libs libcrypto.a, libssl2.a, libssl.a are all under Framework->CFNetwork.framwork they should be there, right?

Reply

Answer 3

Feb 11, 2014 6:00 PM in response to john kerich

OK this is strange.

The unknown types it is complaining about here are defined in the header files included. for example EVP_MD_CTX is defined in evp.h.

But what's more strange is that the first time EVP_MD_CTX is encountered the compiler does not complain. That is in the first function static int init(EVP_MD_CTX *ctx) there is no error for EVP_MD_CTX.

It would seem that the intern setup the other system somehow that is not standard and not duplicated on your system. What that is I can't say.

Reply

Answer 4

john kerich Author

Level 1

0 points

Feb 12, 2014 1:29 PM in response to john kerich

Ok, I was talking to the other person who's Mac the software compiles on and asked if he remember anything that the intern changed to get it to compile and it turns out that software copy he gave me was the pre-fixed CM version. I then installed the new software and compare it against the CM version and found that:

I didn’t have a provisioning profile (forgot to press the fix it button)
The Build Phases Target Dependencies was missing the MailCore (MailCore) reference (which is why it said not found for the classes).
The Build Phases Compiled Sources was missing one extended NSString class (it was there, but xcode didn’t know about it).

So the problem is solved. Needless to say, I was not happy with my co-worker.

Reply

Answer 5

Feb 12, 2014 2:53 PM in response to john kerich

Needless to say, I was not happy with my co-worker.

That makes two of us.

Reply