-
Notifications
You must be signed in to change notification settings - Fork 28
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
Why the need to separately compile aarch64 and x86_64? #61
Comments
However, some larger projects (for example The build steps for such packages error out if |
The process used in this repo precedes |
In case one has a project were the difference is not relevant, which recipe should take as an starting point? Is there any superconfigure subproject currently delegating all this to |
No, every project in this repo builds x86_64 and aarch64 separately, and combines via
I'd recommend building for each arch separately, like the recipes here, because it is easier to test. For a build using just |
We are working on a project and while we were trying to create a config-wrapper we had a doubt about why it is necessary to compile both architectures separately if in the end we will have a single binary.
Considering that the cosmopolitan README instructions say that cosmocc generates an APE for you, why does superconfigure compile separately and then put them together?
The text was updated successfully, but these errors were encountered: