Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 79771 invoked from network); 19 Sep 2006 12:24:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Sep 2006 12:24:44 -0000 Received: (qmail 79298 invoked by uid 500); 19 Sep 2006 12:24:44 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 79288 invoked by uid 500); 19 Sep 2006 12:24:44 -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 79276 invoked by uid 99); 19 Sep 2006 12:24:44 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Sep 2006 05:24:44 -0700 X-ASF-Spam-Status: No, hits=2.4 required=5.0 tests=DNS_FROM_RFC_BOGUSMX,FORGED_RCVD_HELO,PLING_QUERY Received: from ([193.186.16.13:63100] helo=smtp.salomon.at) by idunn.apache.osuosl.org (ecelerity 2.1 r(10620)) with ESMTP id 71/24-26148-681EF054 for ; Tue, 19 Sep 2006 05:24:39 -0700 Received: from servex01.wamas.com (servex01.salomon.at [172.28.2.2]) by smtp.salomon.at (8.12.10/8.12.10) with ESMTP id k8JC78NR015537 for ; Tue, 19 Sep 2006 14:07:08 +0200 (METDST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: AW: boost ?! Date: Tue, 19 Sep 2006 14:07:03 +0200 Message-ID: <18597F2B47F1394A9B309945EC72411282DC52@servex01.wamas.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: boost ?! Thread-Index: AcbbOC1uEEj8Zad2TmKxsG5VZ5j2YAAhUvLQAAmfh/A= From: "Duft Markus" To: X-Spam-Info: -2.538 () ALL_TRUSTED,AWL,BAYES_00,DNS_FROM_RFC_BOGUSMX,PLING_QUERY X-Scanned-By: MIMEDefang 2.54 on 172.28.2.13 X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N OMG, i'm so blind...... I messed up 12d and 15d, maybe those should get = other names ;o) now it's all clear why it can't work.... Anyway thanks for your time, and sorry for messing around in here! Cheers, Markus=20 -----Urspr=FCngliche Nachricht----- Von: Duft Markus [mailto:Markus.Duft@salomon.at]=20 Gesendet: Dienstag, 19. September 2006 09:37 An: stdcxx-dev@incubator.apache.org Betreff: AW: boost ?! Hm, the struct thing was completely wrong, sorry.... Ok, i just digged a little into this: For example one of the unresolved symbols is: __imp_?begin@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@= @QAEPADXZ=20 Which would be: __declspec(dllimport) public: char * __thiscall = std::basic_string,class = std::allocator >::begin(void) The Stdcxx library has symbols some symbols which are close: __imp_?begin@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@= @QAE?AV?$__rw_debug_iter@V?$basic_string@DU?$char_traits@D@std@@V?$alloca= tor@D@2@@std@@PADPAD@__rw@@XZ Which would be: __imp_public: class __rw::__rw_debug_iter,class = std::allocator >,char *,char *> __thiscall = std::basic_string,class = std::allocator >::begin(void) I now think that somehow there is a problem with the headers thinking = they need to compile debug iterators (in build 15d!?) and when using the = lib, they think something else ;o// i looked at my config.h but there = was nothing i could see in there. I attached it, maybe you can see = something. Cheers, Markus -----Urspr=FCngliche Nachricht----- Von: Martin Sebor [mailto:sebor@roguewave.com] Gesendet: Montag, 18. September 2006 17:34 An: stdcxx-dev@incubator.apache.org Betreff: Re: boost ?! Duft Markus wrote: > Hey again! > =20 > I'm currently fighting to get boost compiled with stdcxx... ;o) It=20 > seems, that boost uses both char and wchar_t versions of methods from=20 > stdcxx, which at least seems to compile, but cannot link, since there=20 > is no wchar_t impl in the stdlib15d.lib/.dll. Now my question is: can=20 > i somehow use 15d and 15D together on windows, so that both kind of=20 > symbols are present? The difference between 15d and 15D is that the first is a 32-bit build = type (ILP32) while the second is a 64-bit or wide one (LLP64 on = Windows). The "wide" has nothing to do with wchar_t, it refers to the = width of the data type(s). Stdcxx has full support for wchar_t as long as the compiler supports it. = Keep in mind that the MSVC /Zc:wchar_t option changes the type and = mangling of wchar_t and thus is a binary incompatible option. Programs that link with the library must be compiled with same setting = of the option as the library (i.e., both on or both off). See http://msdn2.microsoft.com/en-us/library/dh8che7s.aspx > And there seem to be some differences from windows STL to this one in=20 > which files get included automatically from other includes and so on,=20 > since i need to explicitly include some files for some things to work=20 > (like std::hex and std::dec are not found, except i include istream or > so....) Stdcxx is much less promiscuous (i.e., a lot cleaner) than other = implementations of the C++ standard library when it comes to its headers = introducing unnecessary names into scope. std::hex and other = manipulators are required to be declared in the header and nowhere = else so in order to use them you must include that header. Martin