-
Notifications
You must be signed in to change notification settings - Fork 49
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
Create an alien module for Image::Magick #142
Comments
I used the installation of Image::Magick in #139 (comment) Then, I created a test script:
and ran pp_autolink on that file:
Does this mean that we only need to pack the following 5 libraries?
|
It should only need those not ending in "__.dll" as those are part of Strawberry Perl (32 bit appends one underscore, 64 bit does two). Although So that means it should only need Edit - I think that is also consistent with what @sisyphus reported in #140 (comment) |
Refer to #139 (comment) :
@shawnlaffan Interesting. Is it also correct that a third option (and maybe the best?) would be to have |
In principle yes, but there are always complexities. The builds need manual intervention at the moment, per the method @sisyphus worked out in https://www.perlmonks.org/?node_id=11153992 but this is a step forward. In one scenario such an Alien would compile from source rather than munging MSYS2 files. The number of extra dependencies is high, though, which leads to more Aliens. There's also the possibility of compiling the various dependencies using the approach we use for the Strawberry Perl deps (see https://github.com/StrawberryPerl/build-extlibs). |
Continuing the discussion from here: #139 (comment), #139 (comment) and #139 (comment)
@shawnlaffan Looks like a good idea, I am creating an issue here so we can track it. I will investigate
App::PP::AutoLink
and come back here when I know more.The text was updated successfully, but these errors were encountered: