Sharadh Rajaraman
Sharadh Rajaraman
@stripe2933 thanks for testing! To answer your questions: 1. I moved `#include ` to `vulkan_hpp_macros.hpp` because the latter has the following few lines: ```c++ // 32-bit vulkan is not typesafe...
The entire reasoning is as follows: in `vulkan.hpp` we have standard header files that need to be conditionally included (or the `std` module imported instead), based on the macro. That...
Reworked again.
> It seems #include have to be added before the line #if defined(__cpp_lib_modules) in vulkan/vulkan.cppm. Good point. I might just `#include` the whole of `vulkan_hpp_macros.hpp` before that clause; it goes...
Reworked again! @asuessenbach, let me know if you'd rather I squashed the commits (unless you can do that when you merge).
The CI setup is really nice; maybe we can use it almost-wholesale. More importantly, we should find a way to parametrise even the hardcoded stuff; having typos like this making...
Thanks for the insight. I've been meaning to update the readmes for a while, including the guidance on different compilers, build systems, etc (the module requires latest _everything_).
@asuessenbach this is ready. @M2-TE I have made the minimum necessary edits to the readme (module name only). All other changes I intend to work in as part of #2358.
Hi @theHamsta! Long time, no see. > Would it be possible to enable at least one configuration in CI that compiles at least one test with C++ modules enabled. Yes,...
I can, but at least one of the PRs will run into a conflict and will have to be correctly rebased, one on top of another.