I got it working, just built a new tool from scratch (I don't know
why the previous project was passing the framework as the last
argument...), but a few caveats.
Great to hear, thanks a ton for the update!
1) It would still not load the SenTestingKit correctly. Even if I
set - rpath manually, it still referenced it from @rpath/
SenTestingKit.framework/Versions/A/SenTestingKit
Putting the framework into one of the framework directories fixed
this...... (as a side note, Xcode is installed into my user folder)
You can the appropriate search paths to your test rig by adding "$
(DEVELOPER_LIBRARY_DIR)/Frameworks" to the "Runpath Search Paths"
build setting in your test rig's target. You can also specify the
environment variable DYLD_FALLBACK_FRAMEWORK_PATH as "$
(DEVELOPER_LIBRARY_DIR)/Frameworks" in your test rig's executable
within Xcode so when dyld can't resolve that @rpath-relative build
setting, it looks in the running Developer Tools folder's Library/
Frameworks. Either should work.
Arghhghh, forgot /Frameworks......
2) With the code below, it would not find any tests unless I pre-
loaded the bundle of my test, like so: [[NSBundle bundleWithPath:
[[[NSProcessInfo processInfo] arguments] lastObject]] load];
Oh, good catch!
3) Since the tool is built with gc turned off, it had to be built
with fobjc-gc or higher.
Right, sorry I forgot to mention this too.
Thanks for giving this a try, I'm glad it works for you now and I'm
sure you've helped out a lot of other people too!
Thanks for helping me get this working!!
Andre
-- Chris
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
