Re: Debug/release libs
- From: "Bruno van Dooren" <bruno_nos_pam_van_dooren@xxxxxxxxxxx>
- Date: Mon, 27 Feb 2006 08:04:18 +0100
I have following problem. I created a static libruary (mylib.lib).
I compiled it with Multithreaded DLL runtime in release mode. Now I want
to give out this library. But users who use it should be able to debug
their programs (i.e. compile their programs in debug mode Multithreaded
DLL DEBUG runtime ).
But at link time following warning is shown and prog crashes. Do I have to
give out both debug and release?
Thanks a lot,
Boni
LINK : warning LNK4098: defaultlib 'MSVCRT' conflicts with use of other
libs; use /NODEFAULTLIB:library
If your program allocates memory that is deleted by the user application,
then yes.
This memory allocation can also happen through use of stl parameters and
things like that.
In that case you need to supply 2 libraries to save your users form having
to jump through hoops.
still, in that case you still have the problem that your users need to use
the same compiler version that you used for building the library.
--
Kind regards,
Bruno.
bruno_nos_pam_van_dooren@xxxxxxxxxxx
Remove only "_nos_pam"
.
- References:
- Debug/release libs
- From: Boni
- Debug/release libs
- Prev by Date: Re: LNK2005 from a C++/CLI dll linking against a non-CLR C++ static library
- Next by Date: Re: Debug/release libs
- Previous by thread: Debug/release libs
- Next by thread: Re: Debug/release libs
- Index(es):
Relevant Pages
|
