-
Notifications
You must be signed in to change notification settings - Fork 106
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
Prebuilt releases header files location #410
Comments
I think that makes sense. That makes it generally easier to extract the contents into a larger project. Probably a good idea to also rename the What exact folder structure are you suggesting, |
@Sahnvour, I'd be happy to write the change to apply your suggestion, but I am not sure what the best folder structure would be. |
In my case, I think the ideal structure would be
Having a root folder helps (I use meson, which has a feature to workaround if it's missing), and a separate include/lib folders make sure we can't include or link something by error while offering the expected standard include paths. |
@Korijn what's your thought about this? |
I'm fine with this! Looks reasonable to me. I wonder if there are more examples like imgui. |
For consuming the prebuilt releases from a build system (meson in my case), it would help if the headers were placed in a
[include]/webgpu
subfolder.When building with other libraries than can use WebGPU (such as imgui) it seems expected to have WebGPU available in the form of
#include <webgpu/webgpu.h>
(note the leading directory).However it is currently needed to manually move the headers in a
webgpu
subfolder after extracting the archive to achieve that and specify correct include paths in the build system.The text was updated successfully, but these errors were encountered: