From 7513f0c265643e6373bfe3fd97933a06d80bcfe2 Mon Sep 17 00:00:00 2001 From: David Rose Date: Wed, 14 Jun 2006 21:22:24 +0000 Subject: [PATCH] add clarifying comments --- dtool/Config.FreeBSD.pp | 13 +++++++++++++ dtool/Config.Irix.pp | 13 +++++++++++++ dtool/Config.Linux.pp | 13 +++++++++++++ dtool/Config.Win32.pp | 13 +++++++++++++ dtool/Config.osx.pp | 15 +++++++++++++++ dtool/Config.pp | 15 +++++++++++++++ 6 files changed, 82 insertions(+) diff --git a/dtool/Config.FreeBSD.pp b/dtool/Config.FreeBSD.pp index 90dbf6e12b..a0870f19a2 100644 --- a/dtool/Config.FreeBSD.pp +++ b/dtool/Config.FreeBSD.pp @@ -6,6 +6,19 @@ // etc. // +// ******************************************************************* +// NOTE: you should not attempt to copy this file verbatim as your own +// personal Config.pp file. Instead, you should start with an empty +// Config.pp file, and add lines to it when you wish to override +// settings given in here. In the normal ppremake system, this file +// will always be read first, and then your personal Config.pp file +// will be read later, which gives you a chance to override the +// default settings found in this file. However, if you start by +// copying the entire file, it will be difficult to tell which +// settings you have customized, and it will be difficult to upgrade +// to a subsequent version of Panda. +// ******************************************************************* + // What additional flags should we pass to interrogate? #define SYSTEM_IGATE_FLAGS -D__i386__ -D__const=const diff --git a/dtool/Config.Irix.pp b/dtool/Config.Irix.pp index f91f0e95e1..086bed4830 100644 --- a/dtool/Config.Irix.pp +++ b/dtool/Config.Irix.pp @@ -6,6 +6,19 @@ // etc. // +// ******************************************************************* +// NOTE: you should not attempt to copy this file verbatim as your own +// personal Config.pp file. Instead, you should start with an empty +// Config.pp file, and add lines to it when you wish to override +// settings given in here. In the normal ppremake system, this file +// will always be read first, and then your personal Config.pp file +// will be read later, which gives you a chance to override the +// default settings found in this file. However, if you start by +// copying the entire file, it will be difficult to tell which +// settings you have customized, and it will be difficult to upgrade +// to a subsequent version of Panda. +// ******************************************************************* + // What additional flags should we pass to interrogate? #define SYSTEM_IGATE_FLAGS -D__mips__ -D__MIPSEB__ -D_LANGUAGE_C_PLUS_PLUS -D_MIPS_SZINT=32 -D_MIPS_SZLONG=32 -D_MIPS_SZPTR=32 diff --git a/dtool/Config.Linux.pp b/dtool/Config.Linux.pp index 88a379657b..8e9ab6676d 100644 --- a/dtool/Config.Linux.pp +++ b/dtool/Config.Linux.pp @@ -6,6 +6,19 @@ // etc. // +// ******************************************************************* +// NOTE: you should not attempt to copy this file verbatim as your own +// personal Config.pp file. Instead, you should start with an empty +// Config.pp file, and add lines to it when you wish to override +// settings given in here. In the normal ppremake system, this file +// will always be read first, and then your personal Config.pp file +// will be read later, which gives you a chance to override the +// default settings found in this file. However, if you start by +// copying the entire file, it will be difficult to tell which +// settings you have customized, and it will be difficult to upgrade +// to a subsequent version of Panda. +// ******************************************************************* + // What additional flags should we pass to interrogate? #define SYSTEM_IGATE_FLAGS -D__i386__ -D__const=const -Dvolatile= diff --git a/dtool/Config.Win32.pp b/dtool/Config.Win32.pp index 32ae7b8c93..26f7d6e1c9 100644 --- a/dtool/Config.Win32.pp +++ b/dtool/Config.Win32.pp @@ -6,6 +6,19 @@ // compiler features, etc. // +// ******************************************************************* +// NOTE: you should not attempt to copy this file verbatim as your own +// personal Config.pp file. Instead, you should start with an empty +// Config.pp file, and add lines to it when you wish to override +// settings given in here. In the normal ppremake system, this file +// will always be read first, and then your personal Config.pp file +// will be read later, which gives you a chance to override the +// default settings found in this file. However, if you start by +// copying the entire file, it will be difficult to tell which +// settings you have customized, and it will be difficult to upgrade +// to a subsequent version of Panda. +// ******************************************************************* + // What additional flags should we pass to interrogate? // NSPR versions prior to 4.4 used _declspec instead of __declspec. #define SYSTEM_IGATE_FLAGS -longlong __int64 -D_X86_ -DWIN32_VC -D"_declspec(param)=" -D"__declspec(param)=" -D_near -D_far -D__near -D__far -D_WIN32 -D__stdcall -Dvolatile= diff --git a/dtool/Config.osx.pp b/dtool/Config.osx.pp index b4e1e5043b..a07c4fee0d 100644 --- a/dtool/Config.osx.pp +++ b/dtool/Config.osx.pp @@ -5,6 +5,21 @@ // platform. It makes some initial guesses about compiler features, // etc. // + +// ******************************************************************* +// NOTE: you should not attempt to copy this file verbatim as your own +// personal Config.pp file. Instead, you should start with an empty +// Config.pp file, and add lines to it when you wish to override +// settings given in here. In the normal ppremake system, this file +// will always be read first, and then your personal Config.pp file +// will be read later, which gives you a chance to override the +// default settings found in this file. However, if you start by +// copying the entire file, it will be difficult to tell which +// settings you have customized, and it will be difficult to upgrade +// to a subsequent version of Panda. +// ******************************************************************* + + //#define PYTHON_IPATH /Library/Frameworks/Python.framework/Headers //#define PYTHON_LPATH /Library/Frameworks/Python.framework/Headers diff --git a/dtool/Config.pp b/dtool/Config.pp index 2f10887bf5..796872e116 100644 --- a/dtool/Config.pp +++ b/dtool/Config.pp @@ -5,6 +5,21 @@ // into the various make scripts. It is processed by ppremake (along // with the Sources.pp files in each of the various directories) to // generate build scripts appropriate to each environment. +// + +// ******************************************************************* +// NOTE: you should not attempt to copy this file verbatim as your own +// personal Config.pp file. Instead, you should start with an empty +// Config.pp file, and add lines to it when you wish to override +// settings given in here. In the normal ppremake system, this file +// will always be read first, and then your personal Config.pp file +// will be read later, which gives you a chance to override the +// default settings found in this file. However, if you start by +// copying the entire file, it will be difficult to tell which +// settings you have customized, and it will be difficult to upgrade +// to a subsequent version of Panda. +// ******************************************************************* + // // ppremake is capable of generating makefiles for Unix compilers such // as gcc or SGI's MipsPRO compiler, as well as for Windows