From bluesky-dev-return-230-apmail-incubator-bluesky-dev-archive=incubator.apache.org@incubator.apache.org Mon Sep 08 14:55:54 2008 Return-Path: Delivered-To: apmail-incubator-bluesky-dev-archive@locus.apache.org Received: (qmail 28337 invoked from network); 8 Sep 2008 14:55:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Sep 2008 14:55:54 -0000 Received: (qmail 887 invoked by uid 500); 8 Sep 2008 14:55:52 -0000 Delivered-To: apmail-incubator-bluesky-dev-archive@incubator.apache.org Received: (qmail 874 invoked by uid 500); 8 Sep 2008 14:55:52 -0000 Mailing-List: contact bluesky-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bluesky-dev@incubator.apache.org Delivered-To: mailing list bluesky-dev@incubator.apache.org Received: (qmail 860 invoked by uid 99); 8 Sep 2008 14:55:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Sep 2008 07:55:52 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hecky.chen@gmail.com designates 209.85.217.19 as permitted sender) Received: from [209.85.217.19] (HELO mail-gx0-f19.google.com) (209.85.217.19) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Sep 2008 14:54:54 +0000 Received: by gxk12 with SMTP id 12so1174957gxk.12 for ; Mon, 08 Sep 2008 07:54:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=/1TVZrphXhigSXV0H4q8mlSMk5af7RFsBxpigMHRMmw=; b=F7mWjdTOzvgJADmKhPNlaFfsZeyAGzOXjVlKCjrwtdrZLcSNcINOxWl72NPPcMu/Vd ri5ZcoUFRCiLhqIFSi9IYzvNsvR7zGB8H9663qqTDMBW2lC2SdKanOVkj2Xp0NikrMjR QITIeToejjtfG/SJygpPYRzTiJz3JiYx8PaLE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=jvAf0Y4HcQaXBZZKvj/fjlcBL1L4phP/08mAP2ZzLaXFruTZFagPwfTdeVE4bV2xqr QwI78it4Q5X4yiRjuUB1sAek8jtV7+GvR8HMd5A1T9o8857cwcUCCV5JA2tAOUieyLqv VbqwQXGaALDOIxMbsi0Mk8feVLZHZy4CZmEJM= Received: by 10.150.54.1 with SMTP id c1mr21483131yba.62.1220885661509; Mon, 08 Sep 2008 07:54:21 -0700 (PDT) Received: by 10.150.11.1 with HTTP; Mon, 8 Sep 2008 07:54:21 -0700 (PDT) Message-ID: Date: Mon, 8 Sep 2008 22:54:21 +0800 From: "chen hecky" To: bluesky-dev Subject: A question in using STLport lib. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_78940_31789125.1220885661483" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_78940_31789125.1220885661483 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, everyone! As far as I know, STLport is not in conflict with ASL, it could be ASL.(Am I right?) We can replace the C++ lib(GPL) by using STLport. But it links to C++ lib in some code of STLport when we compile our code of Bluesky. Such as : . adminserver.h .. /usr/include/stlport/list ... /usr/include/stlport/stl/_prolog.h ... /usr/include/stlport/stl/_list.h .... /usr/include/stlport/stl/_algobase.h ..... /usr/include/stlport/cstddef ...... /usr/include/c++/3.4/cstddef ....... /usr/include/stlport/stddef.h ........ /usr/lib/gcc/i486-linux-gnu/3.4.6/include/../include/stddef.h ..... /usr/include/stlport/cstring ...... /usr/include/c++/3.4/cstring ....... /usr/include/stlport/string.h ...... /usr/include/stlport/using/cstring ..... /usr/include/stlport/climits ...... /usr/include/c++/3.4/climits ....... /usr/lib/gcc/i486-linux-gnu/3.4.6/include/limits.h ..... /usr/include/stlport/cstdlib ...... /usr/include/c++/3.4/cstdlib ....... /usr/include/c++/3.4/i486-linux-gnu/bits/c++config.h ........ /usr/include/c++/3.4/i486-linux-gnu/bits/os_defines.h ....... /usr/include/stlport/stdlib.h ........ /usr/include/../include/stdlib.h ......... /usr/include/stlport/stddef.h .......... /usr/lib/gcc/i486-linux-gnu/3.4.6/include/../include/stddef.h ......... /usr/include/bits/waitflags.h ......... /usr/include/bits/waitstatus.h ......... /usr/include/alloca.h We are puzzling about it at first. After checked the code of the STLport, we find that it is linking to C++ lib in some code of STLport. Such as: In cstddef of stlport: # if (__GNUC__ >= 3) && defined(__CYGWIN__) // this total HACK is the only expedient way I could cygwin to work with GCC 3.0 # define __need_wint_t // mostly because wint_t didn't seem to get defined otherwise :( # define __need_wchar_t # define __need_size_t # define __need_ptrdiff_t # define __need_NULL # endif # if defined (_STLP_USE_NEW_C_HEADERS) # include _STLP_NATIVE_CPP_C_HEADER(cstddef) // I think it must link to cstdd of C++ from here. ------> ...... /usr/include/c++/3.4/cstddef # else # include _STLP_NATIVE_C_HEADER(stddef.h) # endif # ifdef _STLP_IMPORT_VENDOR_CSTD _STLP_BEGIN_NAMESPACE using _STLP_VENDOR_CSTD::ptrdiff_t; using _STLP_VENDOR_CSTD::size_t; _STLP_END_NAMESPACE #endif /* _STLP_IMPORT_VENDOR_CSTD */ So, we must make our code be ASL, does it matter linking to C++(GPL) in STLport? Or how can we do to escape linking to C++? Thanks! ------=_Part_78940_31789125.1220885661483--