January 2006 - Boost-users - lists.preview.boost.org

Re: [Boost-users] gcc3.2 preprocessor concatenation or not on negative numbers
by Merrill Cornish 20 Jan '06

20 Jan '06

Andy, I _think_ I may know why concatenation is working like it is. I believe the purpose of the ## concatentation operator is to cause one symbol (i.e., letters, numbers, underscore) to be created out of two symbols. Since the result of the concatenation that you specified is _not_ a legal symbol, the preprocessor appears to have made a best guess at what should be done rather than flag an error. Merrill

2 1

Compiling with egcs-2.91.66
by Emre Birol 20 Jan '06

20 Jan '06

Hi all, My application uses Graph library files of Boost 1.33.1. It is a very very simple shortest path implementation. When I try to compile it with egcs-2.91.66, Red Hat 6.2 (don't ask why), I get this weird error: boost/mpl/aux_/integral_wrapper.hpp:72: sorry, not implemented: conversion of template_type_parm as template parameter In file included from boost/mpl/integral_c.hpp:32, .... ... It uses following headers from boost: #include <boost/config.hpp> #include <boost/graph/graph_traits.hpp> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/dijkstra_shortest_paths.hpp> Any idea? How can I fix it? thanks, Emre

2 2

Re: [Boost-users] STL-PORT and VC 7.1
by Nat Goodspeed 20 Jan '06

20 Jan '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Sliwa, Przemyslaw (London) > Sent: Friday, January 20, 2006 10:32 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] STL-PORT and VC 7.1 > > I have a quick question - I would like to build the static library and > not the DLL. > Could you tell me what should be changed in the project apart form the > "General->static lib"? [Nat] Um, no. But since .vcproj files are specially-formatted text files, I assume the worst case would involve building a new static-library project by manually setting things the same way in your new project file as in my old one. The IDE may let you change the root type of a project after the fact; I've never tried. > Do you know how to disable the auto-link of boost? [Nat] These are things we changed in boost/boost/config/user.hpp: // BOOST_WHATEVER_DYN_LINK: Forces library "whatever" to be linked as a dll // rather than a static library on Microsoft Windows: replace the WHATEVER // part of the macro name with the name of the library that you want to // dynamically link to, for example use BOOST_DATE_TIME_DYN_LINK or // BOOST_REGEX_DYN_LINK etc (this macro is used to turn on __declspec(dllimport) // modifiers, so that the compiler knows which symbols to look for in a dll // rather than in a static library). // Note that there may be some libraries that can only be statically linked // (Boost.Test for example) and others which may only be dynamically linked // (Boost.Threads for example), in these cases this macro is unsupported. // #define BOOST_WHATEVER_DYN_LINK #define BOOST_FILESYSTEM_DYN_LINK #define BOOST_SIGNALS_DYN_LINK #define BOOST_PYTHON_DYN_LINK // BOOST_ALL_NO_LIB: Tells the config system not to automatically select // which libraries to link against. // Normally if a compiler supports #pragma lib, then the correct library // build variant will be automatically selected and linked against, // simply by the act of including one of that library's headers. // This macro turns that feature off. #define BOOST_ALL_NO_LIB

1 0

Re: [Boost-users] STL-PORT and VC 7.1
by Sliwa, Przemyslaw (London) 20 Jan '06

20 Jan '06

Thanks a lot for this. I have a quick question - I would like to build the static library and not the DLL. Could you tell me what should be changed in the project apart form the "General->static lib"? Do you know how to disable the auto-link of boost? Many thanks for help, Pshemek Kind regards Pshemek Przemyslaw Sliwa Global Foreign Exchange FX Risk Engine Development Merrill Lynch ( +44 (0)20 7995 4182 ) +44 (0)79 6325 2319 * Email: przemyslaw_sliwa(a)ml.com -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Nat Goodspeed Sent: 20 January 2006 14:35 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] STL-PORT and VC 7.1 > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Sliwa, Przemyslaw (London) > Sent: Friday, January 20, 2006 8:18 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] STL-PORT and VC 7.1 > > I did not understand your statement properly -> did you create your own > VC 7.1 projects for the three libraries? [Nat] Yes, using the IDE, we made new VC 7.1 projects, which I've attached for you to review & modify to suit your own needs. (There's already a libs/python/build/VisualStudio/boost_python.dsp file, which we loaded into VC 7.1, implicitly converting it to .vcproj.) We created them in libs/filesystem/build libs/signals/build libs/python/build/VisualStudio under the Boost main directory. (It's important to know where we put the .vcproj files because we use .. in the projects' include paths. We do that because the project file is checked into our version control system, and we want people to be able to check out multiple copies in different locations on their own machine and build each of them independently.) The include paths reference $(STLPORTDIR), which you must set in the environment. boost_python.vcproj additionally references $(PYTHONDIR), which you must likewise set. > Is this a standard procedure what people do when something is not > working in boost? [Nat] It's a standard procedure for when bjam produces build errors and you don't even WANT to learn enough about its idiosyncrasies to try to coax it. :-) -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

1 0

Re: [Boost-users] STL-PORT and VC 7.1
by Nat Goodspeed 20 Jan '06

20 Jan '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Sliwa, Przemyslaw (London) > Sent: Friday, January 20, 2006 8:18 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] STL-PORT and VC 7.1 > > I did not understand your statement properly -> did you create your own > VC 7.1 projects for the three libraries? [Nat] Yes, using the IDE, we made new VC 7.1 projects, which I've attached for you to review & modify to suit your own needs. (There's already a libs/python/build/VisualStudio/boost_python.dsp file, which we loaded into VC 7.1, implicitly converting it to .vcproj.) We created them in libs/filesystem/build libs/signals/build libs/python/build/VisualStudio under the Boost main directory. (It's important to know where we put the .vcproj files because we use .. in the projects' include paths. We do that because the project file is checked into our version control system, and we want people to be able to check out multiple copies in different locations on their own machine and build each of them independently.) The include paths reference $(STLPORTDIR), which you must set in the environment. boost_python.vcproj additionally references $(PYTHONDIR), which you must likewise set. > Is this a standard procedure what people do when something is not > working in boost? [Nat] It's a standard procedure for when bjam produces build errors and you don't even WANT to learn enough about its idiosyncrasies to try to coax it. :-)

1 0

Re: [Boost-users] [Review] Formal review of Fixed Strings librarystarts today
by Sohail Somani 20 Jan '06

20 Jan '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Hartmut Kaiser > The fixed_strings library is a buffer-overrun safe version of using > fixed-size character array data buffers. It provides > integration with the C > API allowing strcpy, et. al. to be used safely for a fixed string and > provides a basic_string interface allowing easy migration to > C++ strings. Wouldn't the typical user have to replace all the char * and char [] with boost::fixed_string<n>? What are the advantages over replacing them with string or even boost array and overloading the appropriate C api calls? Thanks Sohail

2 1

Re: [Boost-users] STL-PORT and VC 7.1
by Sliwa, Przemyslaw (London) 20 Jan '06

20 Jan '06

Hi, Thanks for help, I did not understand your statement properly -> did you create your own VC 7.1 projects for the three libraries? Is this a standard procedure what people do when something is not working in boost? Could you give me your compiler/linker options and setting so that I could make something similar? Thanks Pshemek Kind regards Pshemek Przemyslaw Sliwa Global Foreign Exchange FX Risk Engine Development Merrill Lynch ( +44 (0)20 7995 4182 ) +44 (0)79 6325 2319 * Email: przemyslaw_sliwa(a)ml.com -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Nat Goodspeed Sent: 20 January 2006 12:05 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] STL-PORT and VC 7.1 > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Sliwa, Przemyslaw (London) > Sent: Friday, January 20, 2006 5:05 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] STL-PORT and VC 7.1 > > I had a quick look at the regression test for boost using > vc-7_1-stlport. It seems none of the tests has been passed. > The question is, what is the point to add and release something if is > does not work at all? [Nat] I haven't looked at the regression tests page -- sorry. But I can tell you that our product is built with STLport and VC 7.1, and we're using Boost filesystem, signals, Boost.Python, bind, shared_ptr, lambda, iterators, and undoubtedly a few others I can't remember off the top of my head. But as I've remarked a few times previously, we only briefly crossed swords with bjam. Then we backed away slowly, making the sign to ward off complexity, and built VC "projects" of our own for the three Boost libraries we use that need to be prebuilt: filesystem, signals and Boost.Python. It's only fair to add that we're still using Boost 1.31. The migration from 1.30 to 1.31 cost us a week, and we have since been shy about jumping into new Boost versions. I'm hoping that someday soon I'll be able to reserve a week to attempt the quantum leap to 1.33... :-) _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

1 0

Re: [Boost-users] STL-PORT and VC 7.1
by Nat Goodspeed 20 Jan '06

20 Jan '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Sliwa, Przemyslaw (London) > Sent: Friday, January 20, 2006 5:05 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] STL-PORT and VC 7.1 > > I had a quick look at the regression test for boost using > vc-7_1-stlport. It seems none of the tests has been passed. > The question is, what is the point to add and release something if is > does not work at all? [Nat] I haven't looked at the regression tests page -- sorry. But I can tell you that our product is built with STLport and VC 7.1, and we're using Boost filesystem, signals, Boost.Python, bind, shared_ptr, lambda, iterators, and undoubtedly a few others I can't remember off the top of my head. But as I've remarked a few times previously, we only briefly crossed swords with bjam. Then we backed away slowly, making the sign to ward off complexity, and built VC "projects" of our own for the three Boost libraries we use that need to be prebuilt: filesystem, signals and Boost.Python. It's only fair to add that we're still using Boost 1.31. The migration from 1.30 to 1.31 cost us a week, and we have since been shy about jumping into new Boost versions. I'm hoping that someday soon I'll be able to reserve a week to attempt the quantum leap to 1.33... :-)

1 0

Re: [Boost-users] STL-PORT and VC 7.1
by Sliwa, Przemyslaw (London) 20 Jan '06

20 Jan '06

I had a quick look at the regression test for boost using vc-7_1-stlport. It seems none of the tests has been passed. The question is, what is the point to add and release something if is does not work at all? Thanks Pshemek Kind regards Pshemek Przemyslaw Sliwa Global Foreign Exchange FX Risk Engine Development Merrill Lynch ( +44 (0)20 7995 4182 ) +44 (0)79 6325 2319 * Email: przemyslaw_sliwa(a)ml.com -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Rene Rivera Sent: 19 January 2006 17:23 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] STL-PORT and VC 7.1 Sliwa, Przemyslaw (London) wrote: > This is the program taken from the tutorial I am trying to compile/link: > http://www.boost.org/libs/filesystem/example/simple_ls.cpp From below I can't see which of the filesystem lib variants it's trying to link to. Somewhere in your compile log you should have a "linking to ..." mentioning the filesystem lib. Could you post that. > "_WIN32_WINNT=0x0501" /D "WINVER=0x0501" /D "_STLP_DEBUG" /D "_MBCS" /FD Well during building bjam sets: /D "_STLPORT_DEBUG=1", but I can't remember if the value matters. > Linking... > main.obj : error LNK2019: unresolved external symbol "public: class > _STL::basic_string<char,class _STL::char_traits<char>,class The "_STL::..." is a sign that it's not using STLport somehow. Because it should be using something like "stlp_std::...". -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

1 0

Re: [Boost-users] STL-PORT and VC 7.1
by Sliwa, Przemyslaw (London) 20 Jan '06

20 Jan '06

Thanks for help, I would like to build (compile and link) some examples from the filesystem directory. Can anyone tell me how to do this? In which file I can find the compiler and linker flags used by bjam for vc-7_1-stlport build? Perhaps if I will not be able to link this will indicate some errors in the compiler flags I am using in my program. Thank Pshemek Kind regards Pshemek Przemyslaw Sliwa Global Foreign Exchange FX Risk Engine Development Merrill Lynch ( +44 (0)20 7995 4182 ) +44 (0)79 6325 2319 * Email: przemyslaw_sliwa(a)ml.com -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Rene Rivera Sent: 19 January 2006 17:23 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] STL-PORT and VC 7.1 Sliwa, Przemyslaw (London) wrote: > This is the program taken from the tutorial I am trying to compile/link: > http://www.boost.org/libs/filesystem/example/simple_ls.cpp From below I can't see which of the filesystem lib variants it's trying to link to. Somewhere in your compile log you should have a "linking to ..." mentioning the filesystem lib. Could you post that. > "_WIN32_WINNT=0x0501" /D "WINVER=0x0501" /D "_STLP_DEBUG" /D "_MBCS" /FD Well during building bjam sets: /D "_STLPORT_DEBUG=1", but I can't remember if the value matters. > Linking... > main.obj : error LNK2019: unresolved external symbol "public: class > _STL::basic_string<char,class _STL::char_traits<char>,class The "_STL::..." is a sign that it's not using STLport somehow. Because it should be using something like "stlp_std::...". -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

1 0