|
Re: Is there a Native Perl for Windows 10 Arm64
by pryrt (Abbot) on Jul 01, 2021 at 15:58 UTC
|
Good point. I am seeing other open-source applications I use generating arm64 binaries.
Strawberry Perl is my go-to for Windows Perl, but I don't see that they have published any arm64 builds for distribution.
I peeked at Strawberry's support page for where to file bug reports or feature requests, and looked through both their rt.cpan.org-based issue tracker and github-based issue tracker, and there don't seem to be any requests yet for a Windows Arm64 build of Strawberry Perl. Maybe you would be interested in making a request there. | [reply] |
|
|
Thanks you. Filed a tracker for Strawberry Perl. The response was they are ready to port but largest blocker is that MSYS2 does not support arm64 windows yet.
Also Filed a case at ActiveState Perl, but still under consideration.
For my current solution: I got the source from perl.org and did a cross compile on a Windows x86_64 + VS2019 and a-lot of Makefile tweak.
Thank again for your help.
| [reply] |
|
|
I got the source from perl.org and did a cross compile on a Windows x86_64 + VS2019 and a-lot of Makefile tweak
Wow !!
Do you feel like writing up precisely what you did, and posting it here ?
It's the sort of thing that some other(s) would find useful.
Out of idle curiosity, I'm wondering whether the win32/Makefile was the *only* file in the perl source that needed tweaking ?
(I'm also a bit interested in knowing the details of the cross compilation ... though it's unlikely I'll ever be building perl for arm64.)
Cheers,
Rob
| [reply] |
Re: Is there a Native Perl for Windows 10 Arm64
by holli (Abbot) on Jul 01, 2021 at 19:01 UTC
|
| [reply]
[d/l] |
|
|
| [reply] |
|
|
| [reply]
[d/l] |
|
|
Re: Is there a Native Perl for Windows 10 Arm64
by syphilis (Archbishop) on Jul 02, 2021 at 01:29 UTC
|
Is there a Native Perl for Windows 10 Arm64 ?
Not that I've heard of.
Have you any interest in building one ?
I envisage that, using the Microsoft compiler you indicated, you'd start by working through the (self-documenting) win32/Makefile in the perl source.
If, instead, you wanted to try building perl with a mingw-w64 port of gcc then, according to Wikipedia "a packaging of LLVM's clang to mingw-w64 is also provided by MSYS2. It supports ARM for Windows (aarch64-w64-mingw32 and armv7-w64-mingw32)".
However, it seems there's not yet an MSYS2 for arm64, though the idea has been floated, and some progress has been made. (Google for "msys2 arm64".)
I also note that there are mingw-w64 ports of gcc that include clang and LLVM available at http://winlibs.com/.
With them, you'd start by working your way through the win32/GNUmakefile.
I have absolutely no idea what sort of mileage you would get with any of those approaches ... I expect there would be some non-trivial problems to solve.
Cheers,
Rob
PS: Cygwin also provides a build of perl, so you could see if anything useful turns up when you google for "Cygwin arm64".
However, I don't think that Cygwin (or MSYS2, for that matter) really count as "native" windows. | [reply] |
Re: Is there a Native Perl for Windows 10 Arm64
by Aldebaran (Curate) on Jul 01, 2021 at 18:33 UTC
|
Is there a Native Perl for Windows
I would say that perl is native to unix, "liquid unix" as bliako says. Strawberry Perl has made Windows bearable for me in the past, but using cygwin has been where I usually end up. | [reply] |
|
|
| [reply] |
|
|
| [reply] |
|
|
And especially what planetscape wrote
The issues that you and she outlined can be avoided by paying due diligence to the content of your PATH.
On my Windows machines, there are no perls in my default path.
If I want a perl in my path, I have to add the one I want - by opening a Cygwin bash shell, or by executing a batch file (portable Strawberry's portableshell.bat, or one of my own customized .bat files).
That way, I'm generally set up to avoid those types of problems, without even having to think about them.
Cheers,
Rob
| [reply] |
Re: Is there a Native Perl for Windows 10 Arm64
by raandom (Acolyte) on Nov 26, 2023 at 09:23 UTC
|
| [reply] |
