search

Neumann-A / my-vcpkg-triplets

my collection of vcpkg triplets
MIT License
72 stars 12 forks source link

msvs 2022 vcpkg settings for this one? #17

Closed TomieAi closed 3 months ago

TomieAi commented 3 months ago

image how to do it ? xD it still redirecting at x64-windows-static-md instead of x64-win-llvm-static-md-release

my installed dir looks like this image

I also paste your stuff at vcpkg D:\vcpkg\triplets\community haha i mean it works tho i just want it to redirect now the x64-windows-static-md to x64-win-llvm-static-md-release.. or i did wrong? i dont understand your readme.. i feel if i do that i will still have the folder called x64-win-llvm-static-md-release/

I installed it stuff like this. build fine installed at x64-win-llvm-static-md-release but again vcpkg at ms still doing x64-windows-static-md vcpkg install LightningScanner:x64-win-llvm-static-md-release

project is also set image

Edit: Progress 1

If you installed it like this vcpkg install <pkg_name_here>:x64-win-llvm-static-md

you have to set it like this image

setting dynamic and static will append static-md at triplet x64-win-llvm so it will redirect to ``vcpkg\installed\x64-win-llvm-static-md```

but if u installed it like this vcpkg install <pkg_name_here>:x64-win-llvm-static-md-release

you have to set it like this image

disabling dynamic and static because you skip the static-md appending part

Edit: Progress 2

theres also undefined symbol : __movsb hmm i think because it skip if msvc defines at source code.. i dont know.

Edit: Progress 3

yeah it compile and skip this 

#if defined(_MSC_VER) && !defined(MINHOOK_DISABLE_INTRINSICS)
    #define ALLOW_INTRINSICS
    #include <intrin.h>
#endif

because i can reproduce the same error if u comment #include after adding the minhook source maunally.. i guess its a minhook problem.. maybe? xD

TomieAi commented 3 months ago

im gonna close this one.. the lib issue its because llvm doesnt support msvc auto linking so you must include the lib manually via pragma comment .. and for avx make sure u enable the avx support in order to use it.. declaring header is not enough for clang.

Neumann-A commented 3 months ago

and for avx make sure u enable the avx support in order to use it.. declaring header is not enough for clang.

With LLVM 19 that will change.

TomieAi commented 3 months ago

and for avx make sure u enable the avx support in order to use it.. declaring header is not enough for clang.

With LLVM 19 that will change.

god i hope so xD