-
I've found only this as something related to my question and one more link I cannot find anymore, but that conversation got offtopic too quick, at least for me. I have simple vulkan dependency in my build file defined like this But I'd like to link to the I know how to work around this, I could create just simple wrap file to get vulkan header, or hardcode the path to option, but I've already had this question, so I was interested if there is a way how to do this for my future encounters, in case there won't be another way. Is there maybe some option to "clear" already created object? ### Now during writing this last sentence I've tried to look at it from different angle and reread the I guess I'll see once I'll try it but still wanted to ask this either way. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I've tried with EDIT: Going through source code I've found the inheritance model But I'll be looking forward to implementation of this TODO nontheless |
Beta Was this translation helpful? Give feedback.
I've tried with
(links: false, includes: true)
but unfortunately it seems they are not being propagated, so not sure if the final .exe would directly link since I don't have access to headers in a first place for a successful compilation.EDIT: Going through source code I've found the inheritance model
VulkanDependencySystem->SystemDependency->ExternalDependency
don't haveinclude_dirs
variable in a first place, so there is nothing to copy. Good thing is though that at least for now, include path is defined incompile_args
and nothing else, so lucky me I don't need to bring more unnecessary arguments into my project and for internal dependencies my previous approach should work just fine.B…