Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use for patchelf (linux etc.) or install_name_tool (macOS) #2

Open
plicease opened this issue Nov 17, 2017 · 11 comments
Open

Use for patchelf (linux etc.) or install_name_tool (macOS) #2

plicease opened this issue Nov 17, 2017 · 11 comments
Assignees

Comments

@plicease
Copy link
Member

interesting?

https://github.com/NixOS/patchelf

@plicease plicease self-assigned this Nov 17, 2017
@kiwiroy
Copy link

kiwiroy commented May 1, 2018

My experience suggests it works well.

install_name_tool does the same for dyld

@plicease
Copy link
Member Author

@plicease plicease changed the title Use for patchelf? Use for patchelf or install_name_tool Mar 31, 2022
@plicease plicease changed the title Use for patchelf or install_name_tool Use for patchelf (linux etc.) or install_name_tool (macOS) Mar 31, 2022
@shawnlaffan
Copy link

My immediate plan is to use it for autotool aliens for which passing LDFLAGS like -Wl,rpath=\$ORIGIN/../lib leads to shell escape headaches.

Let me know if it would be sensible for it to live under the PerlAlien org.

@shawnlaffan
Copy link

Oh, and passing relative and absolute rpath args in the build process seems to work well with Alien::geos::af and Alien::proj. Both use Cmake, which handles the shell escapes sanely.

Example: https://github.com/shawnlaffan/perl-alien-proj/blob/71970eb98c73e69d08f5fef0fc8561034ad269bc/alienfile#L293-L303

@plicease
Copy link
Member Author

Relative paths for linking is I think what I had in mind, makes relocatable @INC workable. Haven't made any progress beyond just thinking about it mind you.

I'd be happy to host these sort of Aliens under the PerlAlien org!

@shawnlaffan
Copy link

I'd be happy to host these sort of Aliens under the PerlAlien org!

Let me know what I need to do.

@shawnlaffan
Copy link

shawnlaffan commented Mar 31, 2022

Relative paths for linking is I think what I had in mind, makes relocatable @INC workable

Absolute paths can be useful, at the least on cpan-testers where some testers keep everything in their respective blib dirs and not the final install location. The approach I use at the moment is to have the relative paths first. If they don't exist then they are skipped anyway.

@plicease
Copy link
Member Author

Let me know what I need to do.

I think all you need to do is go to https://github.com/shawnlaffan/perl-alien-patchelf/settings and under "Danger Zone" (scary lol) there is a button that says Trasfer. (If you do, please change the name to Alien-patchelf to match the convention of the other repos). I think as a member of the org you should be able to do this without my intervention (and create new repos as well), but if not let me know and I will bump your access.

@plicease
Copy link
Member Author

Absolute paths can be useful, at the least on cpan-testers where some testers keep everything in their respective blib dirs and not the final install location. The approach I use at the moment is to have the relative paths first. If they don't exist then they are skipped anyway.

Ah nice. So you can specify multiple paths?

@shawnlaffan
Copy link

Ah nice. So you can specify multiple paths?

Yes, it uses the same colon separated format as normal unix paths.

@shawnlaffan
Copy link

Repo transferred but I can no longer change its name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants