Re: Qt and the Loki Library
Could you verify the linker command arguments that the loki library indeed is getting linked with the executable?
Re: Qt and the Loki Library
Thanks for the response. We confirmed it as best we can.
As we said, we also added the source and header files to our project and ignored the library but got the same error.
We have have looked into low-level Qt headers and MS C library headers to see if we can find a clue. Not long ago we found that some programs with Loki and Qt have no problem, so we may be missing a library somewhere.
The hunt goes on...
Re: Qt and the Loki Library
Are you sure the Loki lib is compiled for MSVC and not MinGW? Do you have a corresponding dll file, by the way?
Re: Qt and the Loki Library
Also, does the library have necessary import/export macros for its public classes?
Re: Qt and the Loki Library
We used the MSVC solution for 2005 that came with the library. It produces a static library (.lib).
Note that we get the same errors if we drop the source and header files into our program source and do not link with the library.
It has been suggested that _write may be a Qt macro that is somehow confusing the linker. We do know that Qt has a QT_WRITE macro but are not sure how that works in the IO system.
Re: Qt and the Loki Library
This is "Loki::_write" and not "_write". If the name "_write" is reported by the linker, it is not a macro as macros are expanded by the preprocessor. Check if your Loki library indeed has the referenced symbol (Loki::_write) in it.
Re: Qt and the Loki Library