Re: Unit Testing frameworks problem - 2.4
Re: Unit Testing frameworks problem - 2.4
- Subject: Re: Unit Testing frameworks problem - 2.4
- From: Byron Wright <email@hidden>
- Date: Tue, 15 Aug 2006 17:11:48 -0700
Hi Aaron,
thanks for the reply but unfortunately that didn't help. My symbols
are being exported, nm output:
MacDaddy:~/Projects/hessianobjc/trunk byronwright$ nm -gj build/
HessianObjC/HessianObjC.framework/HessianObjC
build/HessianObjC/HessianObjC.framework/HessianObjC(single module):
.objc_category_name_BBSHessianCall_PrivateMethods
.objc_category_name_BBSHessianDecoder_PrivateMethods
.objc_category_name_BBSHessianEncoder_PrivateMethods
.objc_class_name_BBSHessianCall
.objc_class_name_BBSHessianDecoder
.objc_class_name_BBSHessianEncoder
.objc_class_name_BBSHessianInvocation
.objc_class_name_BBSHessianMapDecoder
.objc_class_name_BBSHessianProxy
.objc_class_name_BBSHessianResult
.....
...
..
.
Any other suggestions?
Thanks,
Byron
On Aug 15, 2006, at 4:25 PM, Aaron Montgomery wrote:
On Aug 15, 2006, at 3:30 PM, Byron Wright wrote:
I have a framework project with unit tests that I know worked fine
in 2.2 (The last time I updated the framework and it's tests).
Today I attempted to build the framework and its tests and am
getting unresolved symbols when trying to link the framework with
my test bundle. I followed these instructions http://
developer.apple.com/documentation/DeveloperTools/Conceptual/
UnitTesting/index.html but still cannot successfully build my test
bundle.
Just a guess, but missing symbols make me think that your framework
isn't making the symbols public. Try the nm tool on the framework
to see what it is making public. It may be that you need to uncheck
the "Symbols Private by Default" setting in your frameworks "Code
Generation" settings. There are also problems (application will
crash when test classes are destroyed, so this isn't your current
problem, but it may arise later) with the at exit handling and the
CPlusTest framework that arose in 2.3. I don't know if they still
exist in 2.4. You can prevent this by setting -fno-cxa-atexit flag
in the C flags of the Unit Test target.
Hope that helps,
Aaron
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden