Skip to content
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

Deleting unwanted prebuilds for Yocto #60

Open
jakew009 opened this issue Feb 1, 2022 · 1 comment
Open

Deleting unwanted prebuilds for Yocto #60

jakew009 opened this issue Feb 1, 2022 · 1 comment

Comments

@jakew009
Copy link

jakew009 commented Feb 1, 2022

This is kind of a follow on to this: #54

We use a package (msgpackr-extract) that relies on prebuildify to do it's prebuilding.

The problem we have is that prebuildify leaves the various prebuilt binaries on the OS, even the ones that cannot possibly run (like 64 bit ones on a 32 bit system).

This is obviously normally not a problem, except for when you try and use it with a system like Yocto to build an OS.

Yocto has various QA systems and uses objcopy to move the binaries across. It blows up when you try and copy a 64 bit binary to a 32 bit OS because it knows it could never possibly run.

My current solution is rm -rf node_modules/msgpackr-extract/prebuilds after npm install has finished, to wipe out all the prebuilt binaries (the one we need isn't shipped anyway).
Obviously, this is a bit of an ugly hack.

Is there any way that this situation could be handled differently to make it more compatible with build systems?

@mafintosh
Copy link
Collaborator

Nothing in prebuildify for that no, but you could make a prune tool / option that removes all non-relevant builds

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants