-
Notifications
You must be signed in to change notification settings - Fork 63
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
Porting po4a to windows #370
Comments
po4a works well under cygwin . |
Thanks for this precious feedback, @benoitrolland. Is there anything specific to know or to do when using po4a under cygwin? How did you install it? |
Of course an actual port would be great... But in the meantime, a dev
container would certainly fit most of the bill.
|
I used the github version (po4a version 0.69.) and as far as i remember, I had to install a tool after a strange error message was in fact meaning that a file was not found ...
|
git clone ... I could rebuild po4a v0.69 from a fresh cygwin 3.4.6-1 installation using the following cygwin libraries: perl 5.32.1-2 The following commented-out libs were not explicitly required _At that point because of the following error I had to fuzzy search for the following libs that might not all be required. perl-PerlIO-utf8_strict 0.010-1 Then following the official build instructions should work. |
po4a can be gotten from https://packages.msys2.org/base/po4a for any windows users and it is good. |
Hello,
as a main maintainer of po4a, I'm a linux user. I would need help from the community to get po4a working on Windows. I just setup a build action on github to test the current status.
My understanding is that the most problematic part of po4a wrt portability is its test suite. It relies quite a bit on executing shell commands, which is obviously not a good idea if you target windows. I tried to reduce their amount, and I think that the main runner itself (TestHelper.pm) is more or less OK. I seem to understand that specific tests (the
t/*.t
files) are now the main source ofsystem()
calls that rely on the shell.As I said, I'm by no mean a windows user myself (the last version of that OS that I used was Windows 98 🧓), so I need help here. Please feel free to fork the project, play around, and comment back in this issue how we could further improve the portability. Of course, any working PR would be more than welcome :)
Poke @jowr who attempted such a fork a while ago.
Thanks all for your support. Remember that po4a is maintained by the community nowadays. I don't have the time and energy to do much more than reviewing and applying your patches ;)
Mt
The text was updated successfully, but these errors were encountered: