Problem with dependency (using VS2005)

[Lloyd Dupont]

I'm trying to write a small utility DLL for my InnoSetup script so it could
detect the presence of abscence of some system component.

When I looked at the DLL produced by VS.NET I have a dependency on
MSVCR80.DLL
That's rather annoying as my utility DLL is supposed to tell me if this
MSVCR80 is present or not.

How do I change the library I'm compiled against?
I linked only with shell32.lib & advapi32.liband I would like to depends
only on very widespread DLL, such as MSVCRT.DLL or, at worst MSVCR70.DLL

I did work around this issue by using gcc/MinGW to compile my utility DLL,
but I wonder if it's possible using VS2005?

 

[Carl Daniel [VC++ MVP]]

I'm trying to write a small utility DLL for my InnoSetup script so it
could detect the presence of abscence of some system component.

When I looked at the DLL produced by VS.NET I have a dependency on
MSVCR80.DLL
That's rather annoying as my utility DLL is supposed to tell me if
this MSVCR80 is present or not.

How do I change the library I'm compiled against?
I linked only with shell32.lib & advapi32.liband I would like to
depends only on very widespread DLL, such as MSVCRT.DLL or, at worst
MSVCR70.DLL
I did work around this issue by using gcc/MinGW to compile my utility
DLL, but I wonder if it's possible using VS2005?

Compile with /MT instead of /MD to get your DLL linked with the static
runtime library.

-cd

 

[Lloyd Dupont]

Compile with /MT instead of /MD to get your DLL linked with the static
runtime library.

Cool stuff, thanks!