Skip to content

Commit

Permalink
build: use clang instead of llvm-gcc (#300)
Browse files Browse the repository at this point in the history
Modern clang works just fine, also llvm-gcc is nowhere to be found.
  • Loading branch information
ryan-filmware committed Apr 3, 2024
1 parent b42f035 commit b3a6e99
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 1 deletion.
1 change: 1 addition & 0 deletions Make.inc
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,7 @@ endif

ifeq ($(ARCH),wasm32)
USECLANG = 1
USEGCC = 0
TOOLPREFIX = llvm-
endif

Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ loongarch64.
Linux and Windows.
3. Use `make USECLANG=1` to build with clang. This is the default on OS X, FreeBSD,
and OpenBSD.
4. Use `make ARCH=wasm32` to build the wasm32 library with clang. Requires clang-8.
4. Use `make ARCH=wasm32` to build the wasm32 library with clang.
5. Architectures are auto-detected. Use `make ARCH=i386` to force a
build for i386. Other supported architectures are i486, i586, and
i686. GCC 4.8 is the minimum requirement for correct codegen on
Expand Down

0 comments on commit b3a6e99

Please sign in to comment.