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
The name of the library becomes libiio.lib after Cmake + Nmake finishes.
But using the generated libiio.pc with this command pkg-config libiio --libs --msvc-syntax
gives: /libpath:f:/ProgramFiler-x86/libiio/lib iio.lib
There's no iio.lib. Hence pkg-config is unusable for MSVC.
Only works for MinGW: pkg-config libiio --libs correctly gives -Lf:/ProgramFiler-x86/libiio/lib -liio.
The text was updated successfully, but these errors were encountered:
Honestly, we don't use pkg-config on Windows because it's a pain.
However if you think this should be fixed, it's just a matter of setting the correct library name in libiio.pc.cmakein from one of the CMake variables.
--msvc-syntax
This option is available only on Windows. It causes pkg-config to output -l and -L flags in the form recognized
by the Microsoft Visual C++ command-line compiler, cl. Specifically, instead of
-Lx:/some/path it prints /libpath:x/some/path, and instead of -lfoo it prints foo.lib. Note that the --libs output
consists of flags for the linker, and should be placed on the cl command line after a /link switch.
so I think it's doing exactly what it is supposed to - if you change the libiio.pc.cmakein - for MSVC - it will break for mingw.
The name of the library becomes
libiio.lib
after Cmake + Nmake finishes.But using the generated
libiio.pc
with this commandpkg-config libiio --libs --msvc-syntax
gives:
/libpath:f:/ProgramFiler-x86/libiio/lib iio.lib
There's no
iio.lib
. Hence pkg-config is unusable for MSVC.Only works for MinGW:
pkg-config libiio --libs
correctly gives-Lf:/ProgramFiler-x86/libiio/lib -liio
.The text was updated successfully, but these errors were encountered: