Return-Path: Delivered-To: apmail-stdcxx-dev-archive@www.apache.org Received: (qmail 40285 invoked from network); 12 Feb 2008 22:45:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Feb 2008 22:45:46 -0000 Received: (qmail 38250 invoked by uid 500); 12 Feb 2008 22:45:40 -0000 Delivered-To: apmail-stdcxx-dev-archive@stdcxx.apache.org Received: (qmail 38236 invoked by uid 500); 12 Feb 2008 22:45:40 -0000 Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stdcxx.apache.org Delivered-To: mailing list dev@stdcxx.apache.org Received: (qmail 38227 invoked by uid 99); 12 Feb 2008 22:45:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2008 14:45:40 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.30.140.160] (HELO moroha.roguewave.com) (208.30.140.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2008 22:45:06 +0000 Received: from exchmail01.Blue.Roguewave.Com (exchmail01.blue.roguewave.com [10.22.129.22]) by moroha.roguewave.com (8.13.6/8.13.6) with ESMTP id m1CMjDgp030053 for ; Tue, 12 Feb 2008 22:45:13 GMT 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: [Vote] stdcxx naming in sourcepro builds Date: Tue, 12 Feb 2008 15:45:44 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Vote] stdcxx naming in sourcepro builds Thread-Index: AchtmJhJn2uy12m+SR+2Ofqdo7pcEQALQ1QA References: <47B1D041.3080401@roguewave.com> From: "Eric Lemings" To: Cc: "Scott Zhong" , "_RW_SourcePro Development" <_RW_spro-dev@roguewave.com> X-Virus-Checked: Checked by ClamAV on apache.org =20 > -----Original Message----- > From: Andrew Black [mailto:ablack@roguewave.com]=20 > Sent: Tuesday, February 12, 2008 9:59 AM > To: Eric Lemings > Cc: Scott Zhong; _RW_SourcePro Development > Subject: Re: [Vote] stdcxx naming in sourcepro builds >=20 >=20 > Eventually, it will be necessary to add build tags to the=20 > library name, > in order to resolve bugzilla 5128 (and whatever bug(s) it duplicates), > but that will also require resolution of STDCXX-336. On the > infrastructure side, it will be necessary to devise a mechanism to > communicate the complete build tag to the glue scripts. To resolve these installation-related issues, I suspect the STDCXX distribution will need functionality similar to pkg-config (http://pkg-config.freedesktop.org/wiki/) which provides clients with the necessary details (install directories, compiler flags, library names, etc.) but also extended to provide a list of installed build configurations. (Some open source projects use this utility directly, others use a stand-alone, hand-written script.) For example, a hypothetical script and usage: Usage: stdcxx-config [TAG OPTIONS] Options: --prefix Prints the directory where TAG is installed --cxxflags Prints the necessary compile flags for building with TAG --ldlibs Prints the necessary link libraries for building with TAG --ldflags Prints the necessary link flags for building with TAG ...other pkg-config-like options... If no options are specified, stdcxx-config prints a list of configuration tags, one per line, for each build configuration installed on this system. This will allow STDCXX to install builds built with different compilers, different diagnostic tools, etc. though a user-defined build tag may be required when configuring the build to identify it. Brad.