Changeset 20363 for juggler/branches/2.2/modules/gadgeteer/gadget/gadgetConfig.h

Timestamp:

06/27/07 15:40:03 (1 year ago)

Author:

patrick

Message:

Merges from the trunk:

r20345: Change the preprocessor symbols that we use for identifying debug

and optimized builds. Instead of using _DEBUG and _OPT, we now look
for JUGGLER_DEBUG and JUGGLER_OPT or module-specific identifiers
such as GADGET_DEBUG and GADGET_OPT. Using _DEBUG was a bad idea
because it is used by Visual C++ to identify when the debug runtime
is to be linked. This caused us a lot of problems over the years.

On Windows, we now support three types of builds:

1. Optimized and linked against the release runtime
   
2. Debug-enabled and linked against the release runtime (the
   "_g" variant)
   
3. Debug-enabled and linked against the debug runtime (the "_d"
   variant)
   

Automatic linking takes care of choosing the correct .lib file as
long as _DEBUG is not defined explicitly. Instead, it should only
be defined implicitly as a result of using /MDd when compiling.
User-level code on any platform should define JUGGLER_DEBUG or the
module-specific …_DEBUG symbol to indicate that debugging
capabilities are desired.

r20357: Using /DEBUG when linking causes problems with Visual C++ 7.1 and

automatic linking when the desired outcome is to link against the
"_g" DLL variant. For some reason, /DEBUG causes linking against
both the "_g" variant and the "_d" variant, and that makes
application execution go quite poorly. Visual C++ 8.0 does not
seem to exhibit this behavior, but I have changed those .vcproj
files, too.

This change includes incidental modifications made by Visual Studio
as a result of editing the linker settings in the project files.

Files:

• juggler/branches/2.2/modules/gadgeteer/gadget/gadgetConfig.h (modified) (1 diff)

juggler/branches/2.2/modules/gadgeteer/gadget/gadgetConfig.h

@@ -48 +48 @@
-#undef PACKAGE_VERSION
-
-
+
+
+
+
+
-#   define GADGET_DEBUG
-
+
+
-#   define GADGET_OPT
-#endif