Debug/release libs

[Boni]

Dear all,

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:li brary

[Bruno van Dooren]

> 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:li brary

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.
br************* *********@hotma il.com
Remove only "_nos_pam"

[Carl Daniel [VC++ MVP]]

Boni wrote:

Dear all,

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?

You should, yes.

Alternatively, you can compile your code with /Zl to omit the default
library specification from the resulting .obj files (and hence, from the
..lib file). If you've compiled a release build with /Zl, your users should
be able to link against it in both debug and release builds.

-cd

PS: http://msdn2.microsoft.com/en-us/library/f1tbxcxh.aspx

[Boni]

Dear Carl,
if I compile with /ZI user gets following error.

Alternatively, you can compile your code with /Zl to omit the default
library specification from the resulting .obj files (and hence, from the
.lib file). If you've compiled a release build with /Zl, your users
should be able to link against it in both debug and release builds.

Linking...
LINK : warning LNK4075: ignoring '/INCREMENTAL' due to '/CLRIMAGETYPE'
specification
mylib.lib(eng.o bj) : error LNK2028: unresolved token (0A000006) "extern "C"
void __clrcall ___CxxCallUnwin dDtor(void (__clrcall*)(vo id *),void *)"
(?___CxxCallUnw indDtor@@$$J0YM XP6MXPAX@Z0@Z) referenced in function "void
__cdecl `anonymous namespace'::Rep ortErr(class std::basic_stri ng<char,struct
std::char_trait s<char>,class std::allocator< char> >,class
std::basic_stri ng<char,struct std::char_trait s<char>,class
std::allocator< char> >)"
(?ReportErr@?A0 x7e8edfa5@@$$FY AXV?$basic_stri ng@DU?$char_tra its@D@std@@V?$a llocator@D@2@@s td@@0@Z)
mylib.lib(param s.obj) : error LNK2001: unresolved external symbol
"?.cctor@@$$FYM XXZ" (?.cctor@@$$FYM XXZ)
mylib.lib(eng.o bj) : error LNK2001: unresolved external symbol
"?.cctor@@$$FYM XXZ" (?.cctor@@$$FYM XXZ)
....
Debug/fft_flpt.exe : fatal error LNK1120: 5 unresolved externals

[Carl Daniel [VC++ MVP]]

Boni wrote:

Dear Carl,
if I compile with /ZI user gets following error.

It looks like you've compiled your test library with /clr and your test
program without /clr, or something like that. I haven't tried using /Zl for
a long time - it's possible that it's no longer usable to build a
debug/release agnostic library as well.

-cd

[Boni]

Dear Carl ,
if I deploy debug build without pdb it is not easier to crack than release
build, isn't it. Im I right that all debug symbols are in pdb.

"Carl Daniel [VC++ MVP]" <cp************ *************** **@mvps.org.nos pam>
schrieb im Newsbeitrag news:%2******** *******@TK2MSFT NGP11.phx.gbl.. .

Boni wrote:

Dear Carl,
if I compile with /ZI user gets following error.

It looks like you've compiled your test library with /clr and your test
program without /clr, or something like that. I haven't tried using /Zl
for a long time - it's possible that it's no longer usable to build a
debug/release agnostic library as well.

-cd

[Carl Daniel [VC++ MVP]]

"Boni" <no****@parampa m.pam> wrote in message
news:eI******** ********@tk2msf tngp13.phx.gbl. ..

Dear Carl ,
if I deploy debug build without pdb it is not easier to crack than release
build, isn't it. Im I right that all debug symbols are in pdb.

All debug symbols are in the PDB, yes. That said, debug builds are
considerably easier to reverse engineer than release builds due to the lack
of optimization.

-cd