-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Makefile does not detect new toolchain #6219
Comments
Does the new toolchain on your search path? |
Right, the example of this is zcc and zcxx worked even though they generated a flags error. Only zig build did not return any information in the output. The strange thing is that when did an external test manually everything works. What do you mean? zig code doesn't need libc (only ffi) and the other toolchains can't find to call it. e.g.: $> zig build-obj src.zig
...
$> xtoolchain-gcc src.o -o myfile
# error, need to call libc
....
$> zig build-obj src.zig -lc #link to libc
...
$> xtoolchain-gcc src.o -o myfile
# done |
Wow! Thx @lupyuen |
Thanks! I'm totally new to Zig, but it looks super exciting :-) |
Ref: #5732
When trying last to commit the proposal above there was an issue during the make build running the toolchain that its initialization was not listed in the makefile log. I expected at least some compilation error but it doesn't even return. Except when replacing the
CC
andCXX
withZCC
andZCXX
there are some compilation errors onConfig.mk
file.Would any further changes be required to add a new toolchain or did I forget some reference point?
output:
The text was updated successfully, but these errors were encountered: