sys

[ddkwork]

hi，can you make a "new carbon project as windows kernel driver" template use these commands:
carbon -cc msvc -kernel -o driver.sys driver.v
-DUNICODE -D_UNICODE
-DWINVER=0x0600 -D_WIN32_WINNT=0x0600 -DNTDDI_VERSION=0x06000000
-I"C:\WinDDK\7600.16385.1\inc\ddk"
-Wl,/entry:DriverEntry -Wl,/subsystem:native -Wl,/nodefaultlib
-lntoskrnl.lib -lhal.lib

[jonmeow]

Carbon's toolchain is being built on top of Clang and LLVM (for more information, see "How will Carbon work?" in the FAQ). The compiler infrastructure is being integrated very deeply, so in theory Carbon should be able to build anything that Clang/LLVM could. However, this does require deep integration, so other C++ compilers cannot be trivially swapped in.

If I understand correctly, what you're asking about requires using MSVC, not Clang/LLVM. As a consequence of the above, what you'd need to do would look more like cross-toolchain interoperability (for an outline of this, see the interoperability goal, "Support mixing Carbon and C++ toolchains"). Rather than dropping MSVC into Carbon, you'd need to use Carbon to build something that MSVC could consume.

For example, you could use Clang's MSVC compatibility. That might look like:

1. Use Carbon (+Clang+LLVM) to generate a C++ header and object file from a Carbon library, with an ABI that's suitable for use with non-Carbon toolchains.
2. Use MSVC, linking the output from the Carbon toolchain.

Note a similar story exists for other C++ compilers, such as GCC.