Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 19825 invoked from network); 22 Aug 2006 14:06:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Aug 2006 14:06:57 -0000 Received: (qmail 98975 invoked by uid 500); 22 Aug 2006 14:06:57 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 98917 invoked by uid 500); 22 Aug 2006 14:06:57 -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 98906 invoked by uid 99); 22 Aug 2006 14:06:57 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Aug 2006 07:06:57 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [212.82.213.172] (HELO exkiv.kyiv.vdiweb.com) (212.82.213.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Aug 2006 07:06:56 -0700 Content-class: urn:content-classes:message Subject: RE: [PATCH] Windows infrastructure for generating VisualStudio projects and solution(s) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 22 Aug 2006 17:06:50 +0300 Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.5 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PATCH] Windows infrastructure for generating VisualStudio projects and solution(s) Thread-Index: Aca8F9B0SSvLz7w9Q/SXlBvnntos8AJ2FGmQ From: "Farid Zaripov" To: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > -----Original Message----- > From: Martin Sebor [mailto:sebor@roguewave.com]=20 > Sent: Thursday, August 10, 2006 3:56 AM > To: stdcxx-dev@incubator.apache.org > Subject: Re: [PATCH] Windows infrastructure for generating=20 > VisualStudio projects and solution(s) >=20 > Like Andrew, I would also suggest to stick to the same names=20 > as in the UNIX case (we have TOPDIR/util but BUILDDIR/bin). >=20 > As I might have already mentioned, we should probably reorg=20 > the directory structure a bit so as not to have all the utils=20 > in the same directory. Sooner or later we'd run into name=20 > clashes, and even if not, having each utility sources live in=20 > its own directory (except locale and localedef where there is=20 > a lot of overlap) will make it easier to manage each of them.=20 > (This is just a heads up on changes to come; we need to first=20 > decide on the exact structure we want.) The present direcroty structure on Windows is: %builddir%\bin\%buildtype% %builddir%\lib\%buildtype% %builddir%\examples\%buildtype% %builddir%\tests\%buildtype% I.e. after build of the all configurations the locale.exe and stdlibxxx.lib will be placed at: %builddir%\bin\11d\locale.exe %builddir%\lib\11d\stdlibxxx.lib %builddir%\bin\11s\locale.exe %builddir%\lib\11s\stdlibxxx.lib and so on. What about change the structure to this? %builddir%\%buildtype%\bin %builddir%\%buildtype%\lib %builddir%\%buildtype%\examples %builddir%\%buildtype%\tests With this changes the locale.exe and stdlibxxx.lib will be placed at: %builddir%\11d\bin\locale.exe %builddir%\11d\lib\stdlibxxx.lib %builddir%\11s\bin\locale.exe %builddir%\11s\lib\stdlibxxx.lib and so on, which is like to the directory structure on unix. Farid.