Skip to content
This repository was archived by the owner on Apr 14, 2026. It is now read-only.
This repository was archived by the owner on Apr 14, 2026. It is now read-only.

Transition the build tool to wasixcc #3

@zebreus

Description

@zebreus

Before leaving wasmer I tried to finish the transition of build-scripts from using wasix-clang to wasixcc.

The state of build-scripts is sadly not as wasixcc-compatible as I would like. I pushed my changes to main, but you need to use wasixcc from the branch at wasix-org/wasixcc#54 for it to work. I got the packages up to cpython and its dependencies working this way, but did not have the time to do any further testing.

The approach to finishing this is to run make all and see how far you get. The most common error is that wasm-ld is passed a random thing as input that is not actually an input. This is because wasixcc treats all clang flags it does not know as having no arguments, which means the argument will be interpreted as linker input. There is a list in the wasixcc source, where you can add such flags, so the next thing is treated as an argument. As the build works with wasix-clang, most changes to fix the build should happen in wasixcc, not in build-scripts.

I added some docs on how to use wasixcc from that branch to the Readme. If you already have wasixcc installed, best delete and reinstall to get the latest sysroot release.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions