From 46272e78d22d8c2e59a6768bd084d9aa4d554c60 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Wed, 2 Sep 2009 11:40:24 +0200 Subject: Add a note about using the same VC++ runtime options --- dist/INSTALL | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/dist/INSTALL b/dist/INSTALL index f6fec6b..315b807 100644 --- a/dist/INSTALL +++ b/dist/INSTALL @@ -57,10 +57,17 @@ instructions in the comments in config\config.nmake and make the appropriate changes. The etc/ directory contains a number of sample configurations for various targets/toolchains. -If you are using an IDE (e.g., Visual Studio or eMbedded Visual -C++) to develop your applications, you can copy the compiler -options (such as CPU and Platform preprocessor macros, etc.) -from your project's C++ compiler settings. +If you are using an IDE (e.g., Visual Studio, eMbedded Visual C++, +or Rational Rhapsody) to develop your applications, you can copy +the compiler options (such as C++ language features, CPU and +Platform preprocessor macros, etc.) from your project's C++ +compiler settings. In particular, you need to make sure the +CFLAGS and CXXFLAGS variables in config.nmake contain the same +runtime option (one of /MD, /MDd, /ML, /MLd, /MT, /MTd) as your +application. A common symptom of using different runtime options +when building the XSD/e runtime library (xsde.lib) and your +application is a large number of link errors related to symbol +redefinitions. The next step is to start a new command prompt and execute the vcvars32.bat (or equivalent) file that is normally found -- cgit v1.1