hail_bird

You could set CDROM=install before calling the cmd.

Hi, I met a Visual Studio co-mingle problem. I provided a FPrintStructA( FILE *fp, struct A *sp ) function in a shared library built using Visual Studio 2000 with /MD option. This function print the content of structure sp into the file fp. The user of the shared library usually print out some prompts in to the file, before calling FPrintStructA(). The shared library works well when the caller of the shared library also developed using Visual Studio 2000. However, if the caller is developed using Visual Studio 2005 or 2003, there will be an exception. The reason is the conflict of runtime library (MSVCRT vs MSVCR80 and MSVCR71). Is it possible for me to work out a Visual Studio 2000 shared library, which provides usable FPrintStructA to VS2005 or VS2003 users? howie bao