From stdcxx-dev-return-4006-apmail-incubator-stdcxx-dev-archive=incubator.apache.org@incubator.apache.org Thu Jul 19 15:09:57 2007 Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 41589 invoked from network); 19 Jul 2007 15:09:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Jul 2007 15:09:57 -0000 Received: (qmail 4449 invoked by uid 500); 19 Jul 2007 15:09:33 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 4438 invoked by uid 500); 19 Jul 2007 15:09:33 -0000 Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stdcxx-dev@incubator.apache.org Delivered-To: mailing list stdcxx-dev@incubator.apache.org Received: (qmail 4423 invoked by uid 99); 19 Jul 2007 15:09:33 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jul 2007 08:09:33 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of Farid_Zaripov@epam.com designates 217.21.63.3 as permitted sender) Received: from [217.21.63.3] (HELO EPMSA009.epam.com) (217.21.63.3) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jul 2007 08:09:31 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Intel C++ build issues on Windows Date: Thu, 19 Jul 2007 18:09:14 +0300 Message-ID: <7BDB2168BEAEF14C98F1901FD2DE6438B00C90@epmsa009.minsk.epam.com> In-Reply-To: <469D9B2C.4020308@roguewave.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Intel C++ build issues on Windows Thread-Index: AcfI9vkWvghXr8FgQfy2x/eyRW5qFABH6Wow References: <4685352A.2020104@roguewave.com> <46854951.8000509@roguewave.com> <4685550B.8050503@roguewave.com> <7BDB2168BEAEF14C98F1901FD2DE64389D7445@epmsa009.minsk.epam.com> <7BDB2168BEAEF14C98F1901FD2DE64389D744B@epmsa009.minsk.epam.com> <4689CB94.8050800@roguewave.com> <7BDB2168BEAEF14C98F1901FD2DE6438A6E0E3@epmsa009.minsk.epam.com> <4691BD07.3020005@roguewave.com> <7BDB2168BEAEF14C98F1901FD2DE6438A6EA5D@epmsa009.minsk.epam.com> <46928457.7040102@roguewave.com> <7BDB2168BEAEF14C98F1901FD2DE6438A6EC85@epmsa009.minsk.epam.com> <469D9B2C.4020308@roguewave.com> From: "Farid Zaripov" To: X-Virus-Checked: Checked by ClamAV on apache.org > -----Original Message----- > From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of Martin Sebor > Sent: Wednesday, July 18, 2007 7:47 AM > To: stdcxx-dev@incubator.apache.org > Subject: Re: Intel C++ build issues on Windows >=20 > Another option is to rig one of the library headers (e.g., > _config.h) to optionally #include some header that we could=20 > then "insert" by defining the right magic macro. Like this: >=20 > // _defs.h > #ifdef _RWSTD_INCLUDE_HEADER > # include _RWSTD_INCLUDE_HEADER > #endif >=20 > then we'de compile our examples with the following option on=20 > the command line: > -D_RWSTD_INCLUDE_HEADER=3Dexamples/include/include.h Personally, I prefer this option. Farid.