Linker errors with VS 2008
Moderator: Moderator Team
Linker errors with VS 2008
Most of the DCMTK library works for me except for the new DCMRT module.
When I try to compile a project that links against dcmrt I get linker errors that all seem to do with "log4cplus."
Additionally, I get the infamous "warning LNK4098: defaultlib 'MSVCRT' conflicts with use of other libs; use /NODEFAULTLIB:library"
The LNK4098 error only happens if I use the new DCMRT module. I can use the rest of the module without such warnings or errors.
When I try to compile a project that links against dcmrt I get linker errors that all seem to do with "log4cplus."
Additionally, I get the infamous "warning LNK4098: defaultlib 'MSVCRT' conflicts with use of other libs; use /NODEFAULTLIB:library"
The LNK4098 error only happens if I use the new DCMRT module. I can use the rest of the module without such warnings or errors.
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
I can now build the latest dcmtk. I had to change a linker parameter to inherit dependencies.
Unfortunately, I can't instantiate any class in the dcmrt module. Anytime I do, I get this error:
Or the program becomes unresponsive and I have to manually terminate.
The other dcmtk classes that are not a part of the dcmrt module seem to work just fine.
BTW, This is using C++/CLI.
Unfortunately, I can't instantiate any class in the dcmrt module. Anytime I do, I get this error:
Code: Select all
STATUS_STACK_BUFFER_OVERRUN encountered
The other dcmtk classes that are not a part of the dcmrt module seem to work just fine.
BTW, This is using C++/CLI.
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
Who is online
Users browsing this forum: No registered users and 1 guest