I ported pigz from Unix to Windows • Hacker News Board

Re: I ported pigz from Unix to Windows

#21

Post by frainfreeze » Tue, Jun 24, 2025, 12:35 AM UTC

haunter wrote: post #15

Very old post, needs 2013 in the title https://web.archive.org/web/20130407195442/https://blog.kowa...

Seems to be updated, no?

Re: I ported pigz from Unix to Windows

#22

Post by nialv7 » Tue, Jun 24, 2025, 1:28 AM UTC

The best kind of porting - other people have already done most of the work for you!

Re: I ported pigz from Unix to Windows

#23

Post by throwaway2046 » Tue, Jun 24, 2025, 5:02 AM UTC

nly wrote: post #20

PeakKS wrote: post #14

Earlier quoted context omitted.

It's 2025, just use meson

Completely useless in an airgapped environment

Could you elaborate on that?

Re: I ported pigz from Unix to Windows

#24

Post by carlmr » Tue, Jun 24, 2025, 5:20 AM UTC

throwaway2046 wrote: post #23

nly wrote: post #20

Earlier quoted context omitted.

Completely useless in an airgapped environment

Could you elaborate on that?

I'm guessing it needs internet for everything and can't work with local repositories.

Re: I ported pigz from Unix to Windows

#25

Post by anilakar » Tue, Jun 24, 2025, 6:54 AM UTC

Pigz? Good old Pigzip? :)

https://pc-freak.net/files/hackles.org/cgi-bin/archives.pl%3...

Re: I ported pigz from Unix to Windows

#26

Post by ObscureScience » Tue, Jun 24, 2025, 7:01 AM UTC

anilakar wrote: post #25

Pigz? Good old Pigzip? :) https://pc-freak.net/files/hackles.org/cgi-bin/archives.pl%3...

I don't see any relation. Pigz is a multithreaded reimplenentation of gzip (drop in replacement)

Re: I ported pigz from Unix to Windows

#27

Post by mid-kid » Tue, Jun 24, 2025, 7:56 AM UTC

I'm not sure how willing I'd be to trust a pthread library fork from a single no-name github person. The mingw-w64 project provides libwinpthread, which you can download as source from their sourceforge, or as a binary+headers from a well-known repository like msys2.

Re: I ported pigz from Unix to Windows

#28

Post by account42 » Tue, Jun 24, 2025, 8:24 AM UTC

> Porting pthreads code to Windows would be a nightmare.

Porting one application using pthreads to use the Win32 API directly is however a lot more reasonable and provides you more opportunity to deal with impedance mismatches than a full API shim has. Same goes for dirent and other things as well as for the reverse direction. Some slightly higher level abstraction for the thnings your program actually needs is usually a better solution for cross-platform applications than using one OS API and emulating it on other systems.

Re: I ported pigz from Unix to Windows

#29

Post by account42 » Tue, Jun 24, 2025, 8:26 AM UTC

igrunert wrote: post #19

malkia wrote: post #17

Earlier quoted context omitted.

These VirtualAlloc's may intermittently fail if the pagefile is growing...

Ah yeah, I see Firefox ran into that and added retries: https://hacks.mozilla.org/2022/11/improving-firefox-stabilit... Seems like a worthwhile change, though I'm not sure when I'll get around to it.

This is something you also need to do for other Win32 APIs, e.g. file write access may be temporarily blocked by anti-virus programs or whatever and not handling that makes unhappy users.

Re: I ported pigz from Unix to Windows

#30

Post by account42 » Tue, Jun 24, 2025, 8:30 AM UTC

themadsens wrote: post #6

I wish premake could gain more traction. It is the comprehensible alternative to Cmake etc.

I'd rather everyone use CMake than have to deal with yet another build system. Wouldn't be so bad if build systems could at least agree on the user interface and package registry format.