search

KhronosGroup / glslang

Khronos-reference front end for GLSL/ESSL, partial front end for HLSL, and a SPIR-V generator.
Other
3.01k stars 829 forks source link

[Question] linking problem #3471

Closed jcyuan closed 9 months ago

jcyuan commented 9 months ago

Hi there, just a simple question, i have tried to search the similar question and there was no result. i have tried to use GLSLANG_IS_SHARED_LIBRARY + GLSLANG_EXPORTING to expose those flagged methods, but these marco are for generating dynamic libs (.dll) which is not what i wanted. i need static libs (.lib) for linking in my own project. if without GLSLANG_IS_SHARED_LIBRARY + GLSLANG_EXPORTING to compile, there won't be any methods get exposed inside of the final lib files which makes the linking of my own project failed finally. what is the right way to expose methods for static libs too? manually modify on the macros? thanks.

jcyuan commented 9 months ago

well, not sure why but use the output from VCPkg auto compiling, it works fine now....