That's great Igor, it solves that
However it causes:
Linking...
LINK : warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/INCREMENTAL:NO'
specification
Creating library Debug/xp_emb.lib and object Debug/xp_emb.exp
LINK : warning LNK4098: defaultlib 'MSVCRTD' conflicts with use of other
libs; use /NODEFAULTLIB:library
msvcrt.lib(cinitexe.obj) : warning LNK4098: defaultlib 'libcmtd.lib'
conflicts with use of other libs; use /NODEFAULTLIB:library
I followed that article and my link command line thingy is now:
/OUT:"Debug/****.dll" /NOLOGO /LIBPATH:"C:\Documents and Settings\taylorb\My
Documents\Visual Studio Projects\Apps\xp_emb\reader\Debug" /DLL
/NODEFAULTLIB:"nochkclr.obj" /INCLUDE:"__DllMainCRTStartup@12" /DEBUG
/PDB:"Debug/xp_emb.pdb" /SUBSYSTEM:WINDOWS /NOENTRY /MACHINE:X86 msvcrt.lib
opends60.lib reader.lib kernel32.lib user32.lib gdi32.lib winspool.lib
comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib
odbc32.lib odbccp32.lib ".\reader\Debug\reader.lib"
It is an unmanaged extended stored procedure DLL in VC7.1, and reader.lib is
a managed static library project.
Any ideas?
"Igor Tandetnik" wrote:
"Bonj" <Bo**@discussions.microsoft.com> wrote in message
news:E4**********************************@microsof t.com LINK : warning LNK4243: DLL containing objects compiled with /clr is
not linked with /NOENTRY; image may not run correctly
See KB Article KB814472 "PRB: Linker Warnings When You Build Managed
Extensions for C++ DLL Projects"
--
With best wishes,
Igor Tandetnik
"On two occasions, I have been asked [by members of Parliament], 'Pray,
Mr. Babbage, if you put into the machine wrong figures, will the right
answers come out?' I am not able to rightly apprehend the kind of
confusion of ideas that could provoke such a question." -- Charles
Babbage