Closed raphaelmenges closed 4 months ago
I can reproduce the problem on GitHub actions: https://github.com/raphaelmenges/static-openpnp-capture/actions/runs/9820442542/job/27115023180
Sorry, I don't know. I don't develop for Windows anymore. You can check which functions are exported by the static library using Microsoft's dumpbin I think.
I managed to build a static library under Windows by removing #define DLLPUBLIC
: https://github.com/openpnp/openpnp-capture/commit/7459dd8f4319d19194dc4ce593395c18a5a2cf41
I guess one would need a proper refactoring to build both dynamic and static libraries of openpnp-capture
and sadly, I have no time for that. However, my fork suits my needs. Thus, I see the scope of this issue to be fulfilled.
Hello 👋,
thank you for this library! According to my research, this is the only library that can reliable list connected cameras on Windows and macOS and provides an uniform frame format to be processed across platforms. Great!
I want to use
openpnp-capture
within another library. For this, I prefer to linkopenpnp-capture
statically. I have forked the project and I have changed theCMakeLists.txt
accordingly. It works fine for me under macOS. However, using compiling the library and accompanying test using Visual Studio 2022, I am confronted with the following linker errors:I had suspected
target_link_libraries(openpnp-capture strmiids)
(https://github.com/openpnp/openpnp-capture/blob/8badbbae826a578c2d66deecbffb6a2a079f1817/CMakeLists.txt#L89C5-L90C1) as cause of the issue and moved the linking ofstrmiids
into theCMakeLists.txt
of the test underwin/tests
. But the linker error persist. Any idea what I am doing wrongly?