[mitk-users] Testing modules problem

Hello, I created a brand new module with one sample test included. I followed the documentation, and so i have the module itself and an included test folder, with minimal CMakeLists.txt, file.cmake and a test.cpp. So test/CMakeLists.txt contains : MITK_CREATE_MODULE_TESTS

Re: [mitk-users] Testing modules problem

Hi, why do you have the DLL but not the LIB of your own module? As far as I know, DLLs are created out of LIBs, so if there’s a DLL, I’d expect a LIB, too. For example, the LIBs of MITK modules are in MITK-superbuild/MITK-build/lib/, and the DLL counterparts are located in MITK-superbuild/MITK

Re: [mitk-users] Testing modules problem

If your library does not export any symbols, there will be no import .lib file. As far as I know mitk does not support static linking officially yet. It wouldn't help much in your case anyways. How is the test using your module? If it is via some indirection, you need to load your module manual

Re: [mitk-users] Testing modules problem

Hello, Thanks for that. I was missing the export declaration in front of exposed classes. Everything compiles perfectly now, I used the export macro generated by the first-pass superbuild. Regards, Aurelien Le 20/04/2016 14:39, Sascha Zelzer a écrit : If your library does not export any symb