Alternative port that supports more platforms

[sno2]

I created a new port from scratch that supports more platforms and uses an external nasm source. I believe my port solves #3 , #5, and #6.

https://github.com/sno2/nasm

Let me know if you would like to adopt my repository in place of this one.

Edit: cc @andrewrk

Edit x2: Updated my port to NASM 3.01.

[andrewrk]

@sno2 it looks good but how did you handle the generated files?

also the vendored zlib should be ignored and an actual dependency on aycb/zlib added instead.

[sno2]

@andrewrk Thanks, I updated it to use allyourcodebase's zlib.

Regarding the generated files, I did not realize they were not checked into the GitHub source. I was depending on the "releasebuilds" on the nasm website: https://www.nasm.us/pub/nasm/releasebuilds/3.01/. This tarball includes the generated files from the Perl scripts, such as asm/warnings_c.h, which are not included in the GitHub source for the tag.

[andrewrk]

Nice that's a good solution for the generated files. Your package looks great, I think there's no point in the aycb one when yours exists. Two things to consider:

1. Let's try to avoid breaking any URLs for example by renaming or force pushing this repo.
2. Some projects (e.g. ffmpeg) might require an older 2.x nasm in which case having a 2.x branch would be useful. Although personally if ffmpeg builds with 3.x then I don't care.

[sno2]

Yeah, that makes sense. I created an issue for tracking anyone who needs 2.x support. It seems like many of the breaking changes are added errors for using dubious syntax (e.g. 64-bit REX prefix in 16/32-bit mode).

[andrewrk]

Assuming you want to take over this repository, I think here is a path forward:

• Give you maintainer status on this repo
• Branch off main into "legacy" or something like that, and push it. Never delete that branch.
• Replace main branch with a force push of your main branch

How does this plan sound?

[sno2]

Yeah, that sounds good.

[andrewrk]

@kristoff-it can you help us execute this plan? I don't think I have perms to do it

[kristoff-it]

@sno2 I've invited you both to ayc and to this repository specifically, please accept both invites, once you're in you should be able to perform the necessary changes. If not, just ping me.

[sno2]

Thank you. I copied master into legacy and forced-pushed my main to master.

One thing: Can someone please change the repository description to "nasm ported to the zig build system" or something similar to indicate the current maintained version is not a fork?