You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you're wondering "why would you ever want to do that?", the answer is that I have a tool that parses a preprocessed header. So it uses zig c++ -DSTUFF=FOO -E header.h and then goes through the output and parses it.
This works fine with clang (as long as -nostdinc is not specified).
The text was updated successfully, but these errors were encountered:
When compiling with
zig c++
, if the input file is.h
instead of.cpp
the system include directories are not set up properly. With a.cpp
file:With a
.h
file:If you're wondering "why would you ever want to do that?", the answer is that I have a tool that parses a preprocessed header. So it uses
zig c++ -DSTUFF=FOO -E header.h
and then goes through the output and parses it.This works fine with
clang
(as long as-nostdinc
is not specified).The text was updated successfully, but these errors were encountered: