You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi I am trying to build OpenHevc on Windows 11 visual studio 15 2017 on a intel x86_64 bit machine and facing a build issue like this:
Severity Code Description Project File Line Suppression State
Error LNK2019 unresolved external symbol ff_dct32_float_sse referenced in function ff_dct_init_x86 LibOpenHevcWrapper C:\Users\Downloads\sencore\openHEVC\build\dct_init.obj 1
Severity Code Description Project File Line Suppression State
Error LNK2019 unresolved external symbol ff_dct32_float_avx referenced in function ff_dct_init_x86 LibOpenHevcWrapper C:\Users\Downloads\sencore\openHEVC\build\dct_init.obj 1
I have tried adding them to the c folders but everytime a new unresolved external symbol shows up.
I have made all the changes according to the pull request and have installed yasm along with SDL,SDL2 but the executable is not built.
Can anyone checkout and resolve this issue.
The text was updated successfully, but these errors were encountered:
Hi I am trying to build OpenHevc on Windows 11 visual studio 15 2017 on a intel x86_64 bit machine and facing a build issue like this:
Severity Code Description Project File Line Suppression State
Error LNK2019 unresolved external symbol ff_dct32_float_sse referenced in function ff_dct_init_x86 LibOpenHevcWrapper C:\Users\Downloads\sencore\openHEVC\build\dct_init.obj 1
Severity Code Description Project File Line Suppression State
Error LNK2019 unresolved external symbol ff_dct32_float_avx referenced in function ff_dct_init_x86 LibOpenHevcWrapper C:\Users\Downloads\sencore\openHEVC\build\dct_init.obj 1
I have tried adding them to the c folders but everytime a new unresolved external symbol shows up.
I have made all the changes according to the pull request and have installed yasm along with SDL,SDL2 but the executable is not built.
Can anyone checkout and resolve this issue.
The text was updated successfully, but these errors were encountered: