PathKit build fails through Carthage about pathkit

[kylef]

Does PathKit.framework get built into Carthage/Build/Mac/?

[Danappelxx]

Yup - it's in the second code block (I edited my post right after I pressed submit).

[kylef]

Just curious, can you try the following before running ./main:

$ install_name_tool -add_rpath "@executable_path/Carthage/Build/Mac/"  "main"

[Danappelxx]

Huh... that worked. I've never heard of that command before. What does it do?

Output:

$ ./main
/Users/dan/Desktop/test

[kylef]

I've written about it at https://github.com/kylef/Commander#installation

When you said it works perfectly for other frameworks, we're you doing this the exact same way? With swiftc?

[Danappelxx]

Yup - take a look at the build script for MastCLI if you need an example.

[kylef]

@Danappelxx I think MastCLI is only working because you haven't used any APIs from Commander only imported it.

Once you try using Commander, without the Commander framework available in the rpath it will not run too.

[Danappelxx]

Src/main.swift uses Commander.

[kylef]

Ah missed that file, was looking in src/Command.swift.

[Danappelxx]

Hm... adding install_name_tool -add_rpath "@executable_path/Carthage/Build/Mac/" "bin/mast" to my setup script in MastCLI doesn't fix the PathKit issue I'm having. Would you happen to know why?

[kylef]

@Danappelxx The rpath you've shown is relative to executable path, and Carthage isn't inside the bin directory.

Should become:

$ install_name_tool -add_rpath "@executable_path/../Carthage/Build/Mac/" "bin/mast"

[Danappelxx]

Man, you really know your stuff - thanks!

[kylef]

Going to close this since it looks like we've resolved the problem.