Sadly I was just too quick to gloss over the steps you wrote, thinking that I knew what I was doing more or less.

After re-reading the above CAREFULLY, I realized that I had just added the UnitTest++ code directly to the target instead of making a separate .a file and linking to it.

XCode was trying to compile it all together directly.

My first test is compiling and failing now, as it should.

Thanks again for the article!

The problem here is that you need the files to be compiled using both Objective-C and C++. By default a .m is compiled as just Obj-C, and .cpp as C++. .mm files allow both Obj-C and C++ code.

In this case, the iPhone Sdk files make use of Objective-C, so any C++ files that include them will need to be renamed .mm

I haven’t looked at this code recently, but if you include UIKit.h in your pre-compiled header, you’ll need to make your .cpp files into .mm (or find a way to not use the pre-compiled headers with those files). As an alternative, does UIKit.h need to be included in every single file? Could you instead just include it in those .m files that make use of it?

Thanks for this article, but I am running into a problem. I was getting 997 compile errors, and then I renamed the main .cpp to .mm. Those errors went away and I was left with about 10 link errors. I realized I had not marked the files in UnitTest++ as belonging to the new UnitTests target I added.

After adding that in, I am back to the 997 errors. It appears to be related again to the fact that the UnitTest++ files are .cpp files.

Does anyone know what is wrong with this? I tried commenting out the contents of the prefix file (precompiled header), and removing the file from the project, but the results were the same.

It has something to do with including the UIKit framework in a precompiled header, but I cannot figure out where the issue is.

I haven’t yet had a chance to try this code under 3.2.1 – I’ve only just recently upgraded. I don’t think a difference in XCode versions is the problem here.

I’ll try to help you with the trouble you’re having, could you help me by supplying a little more detail? For example:

- Does the sample project (link near the top of the article) work for you?
- There are a few stages through the article where it says you can try things to check they are working. At what stage does it stop working?
- I’m not sure off hand what a 2788 error is, can you supply the text that goes with that error?
- Also, a ‘Code sign error’ sounds like a badly setup provisioning file. Are you building to a device or the simulator?

Any help in getting a empty UnitTest++ project working with Xcode 3.2.1 is greatly appreciated,

Thanks,
Harry

And like Noel, I would love to have a solution to this. Perhaps Applescripting XCode is the answer here?

Things that I want to do but I’m not currently doing include:
- Running unit tests on the iPhone as well (right now they’re #ifdef’d out)
- Use UnitTest++ for Objective C code as well

If someone is doing that, I’d love to hear about it