Possible to target x64 architecture

[mdodge-ecgrow]

I quickly learned when I built an EXE on my new ARM computer that that will not work as is. After some digging I learned it created an ARM compatible EXE and will not run on every other computer in our company. So I'm wondering if there is a way in native NodeJS to target x64 architecture when building the EXE? From my research I can see that pkg can do that. But it also looks like that library has been archived and no longer being developed.

[BYK]

@mdodge-ecgrow the generated blobs are platform independent (as long as you're not using code cache etc). Once you have the blob, you can download the official Node.js binary for your target platform and inject the blob into that regardless of what platform you're running from.

I've created a tool that does this for you and you can either use that or look at the source code for reference: https://github.com/BYK/fossilize

[mdodge-ecgrow]

Wow, thanks! Anything to make this task easier! I've spent all day fighting with the native SEA option and the nexe library. For some reason, my EXE created with nexe never works once I move it out of the default folder.

My boss has tasked me with creating an exe that will read data from our database and create PDF's from the data. If fossilize will make this easier, I will definitely give it a try.

[mdodge-ecgrow]

So I got it work with a basic node app that does nothing. But once I try and include my pdfGenerator file that uses pdflib, I get this error:
`Error: ENOENT: no such file or directory, open 'C:\Users[username]\Desktop\test\data\Helvetica.afm'

So I'm thinking I need to figure out this line in your main page: "It also supports embedding assets either file by file, from a directory, or through a Vite manifest." Do you have more details on how to do that?
Thanks!

[BYK]

Look at the command line options which will show you how to embed an asset. Then on program start, you read that asset using the built-in sea module with one of these methods: https://nodejs.org/api/single-executable-applications.html#seagetassetkey-encoding

You can then either extract them to the file system or just use them directly.

[mdodge-ecgrow]

Thank you. The only thing I can't figure out is how to set asset keys in Fossilize. It looks like the sea api is looking for a key that points to an asset location. And from the command line options I found in Fossilize the assets option only accepts a string which I assume would be the asset location.

[BYK]

@mdodge-ecgrow apologies as I seem to have forgotten to implement the --asset flag feature 🤦🏻‍♂️ (I was using the --asset-manifest option instead for my own stuff)

Just added that and released v0.5.0. You can find the sample code that I use to test this here: https://github.com/BYK/fossilize/blob/main/test/sample.cjs

Essentially, whatever you pass to the -a option also becomes the key. This is for simplicity.

[RaisinTen]

Download the x64 Node.js binary on your ARM device and then inject the generated SEA blob into that x64 binary. That's how pkg handles it under the hood. Use https://github.com/yao-pkg/pkg instead of pkg. That is the most active and updated fork of pkg.