Jens,

Thanks. A great thing about this list is that the answers often leave me more 
confused than when I asked the question, which is, in fact, great, because it 
often leads to learning new things. I’ve looked into otool and 
install_name_tool now, and I’m beginning to understand the issue. I’ve never 
been able to concentrate hard enough to really understand the issues of dynamic 
linking, though.

So I can get going with my test fast, however, I went back to my usual test 
harness, which is just a simple app with buttons for each major test. I added a 
button to do the NLP testing, and it’s working fine. I’ll be sticking with that 
for awhile.

With any luck, I can put off learning more about dynamic linking for awhile. 
Toungue in cheek. I really appreciate how much willingness to help there is on 
this list. Thanks again.

Tom Wetmore.

 
> On Oct 3, 2015, at 3:32 PM, Jens Alfke <[email protected]> wrote:
> 
> 
>> On Oct 3, 2015, at 12:03 PM, Thomas Wetmore <[email protected]> wrote:
>> 
>> dyld: Library not loaded: @rpath/libswiftAppKit.dylib
>>  Referenced from: 
>> /Users/ttw4/Library/Developer/Xcode/DerivedData/LifeLines-aybxjpaancakhdbudfijgqpqpbhi/Build/Products/Debug/DeadEndsKit.framework/Versions/A/DeadEndsKit
>>  Reason: image not found
>> 
>> A little research indicates that it may not be possible (yet?) to run Swift 
>> command line programs if they require Swift frameworks in order to run.
> 
> You could run install_name_tool on your binary to change the path of 
> libswiftAppKit.dylib to the real location; or alternatively set the Runtime 
> Search Paths [sp?] build setting to the directory it’s in. Although if its 
> real location is inside the Xcode bundle, that won’t be very portable.
> 
> —Jens


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to