This is what my pkgconfig file looks like. The issue is that not using
pkgconfig will assume it is a MSVC build. I think using a pkgconfig
file is preferable in this instance. Let the person doing the build
tailor one to their environment.
prefix=/c/VulkanSDK/1.3.280.0
includedir=${prefix}/Include
On 2025-01-15 7:38 p.m., Koushik Dutta wrote:
For my use case I ended up creating a custom pkgconfig file. My
platform and compiler is windows and msvc.
I was unable to get the existing configure to work correctly with this
environment and opted for pkgconfig as the hook for my environment. Is
t
On 16.01.2025 02:53, Lynne wrote:
On 16/01/2025 09:38, Koushik Dutta wrote:
For my use case I ended up creating a custom pkgconfig file. My
platform and compiler is windows and msvc.
I was unable to get the existing configure to work correctly with this
environment and opted for pkgconfig as th
On 16/01/2025 09:38, Koushik Dutta wrote:
For my use case I ended up creating a custom pkgconfig file. My
platform and compiler is windows and msvc.
I was unable to get the existing configure to work correctly with this
environment and opted for pkgconfig as the hook for my environment. Is
there
For my use case I ended up creating a custom pkgconfig file. My
platform and compiler is windows and msvc.
I was unable to get the existing configure to work correctly with this
environment and opted for pkgconfig as the hook for my environment. Is
there a better way?
Koush
On Tue, Jan 7, 2025 a
On 07/01/2025 14:46, Koushik Dutta wrote:
Searches pkg-config for glslang libraries.
Use libavutil thread.h wrapper rather than directly including pthread.h.
Signed-off-by: Koushik Dutta
---
configure | 1 +
libavutil/vulkan_glslang.c | 2 +-
2 files changed, 2 insertions
