Re: removing all dependency on MSVCR*.DLL

Cartoper wrote:
There is one little C static library to manage the serial number and
unlock key for my application. Today it is compiled with VC6 and
linked into both VC6 modules and VS2005 modules. It is not a lot of
code, but obviously it is very important code that is used all over:

VS2005: used in a C++/CLI module for .Net
VS2005: Apache module
VC6: DLL that is called by the installation program

There are two things I need to do:

1: Upgrade the VC6 module to VS2005.
2: Prepare this static library to go cross platform.

#1 is an issue because I don't want the installer to require the user
have the VS2005 runtime installed simply to run the installer.

#2 is really important because I am going to start working on the
Linux and Mac version of the software and want to keep the source code
for this C static library the same. As it stands now the ONLY
functions the library is using from the CRT are string manipulation
functions, the library does not allocate any memory right now and is
pure C.

Obviously I don't want to use any Microsoft proprietary string
functions. Any suggestions on good alternatives to the standard
string functions that are NOT proprietary Microsoft string functions
and are in a static library or source code I can simply build add to
this library?

Cartoper:

I guess I don't understand the problem. MSVCRT*.dll is just the standard C runtime library. Its equivalent will be on any C/C++ platform.

Or if you use static linking (/MT) everywhere you will not have any DLL dependency on Microsoft platform.

Have you thought carefully about the necessity of porting this app to Mac/Linux? Most Windows programs run pretty well under CrossOver Mac/Linux. Even if your app does not run on CrossOver out of the box, it would almost certainly be less trouble to make it run, rather than port the whole application.

--
David Wilkinson
Visual C++ MVP
.

Relevant Pages

  • removing all dependency on MSVCR*.DLL
    ... linked into both VC6 modules and VS2005 modules. ... have the VS2005 runtime installed simply to run the installer. ... Linux and Mac version of the software and want to keep the source code ... string functions that are NOT proprietary Microsoft string functions ...
    (microsoft.public.vc.language)
  • Re: independent string functions
    ... Today it is compiled with Microsoft ... VC6 and linked into both VC6 modules and VS2005 modules. ... the standard string functions, something I can simply include in this ... when I compile it with VS2005 nor with the Linux and ...
    (comp.lang.c)