August 2003 - Boost-users - lists.boost.org

Graph component question
by Stefan Slapeta 15 Aug '03

15 Aug '03

Hi all, finding edges of cycles in a directed graph is a solved problem and done by the strong_components algorithm. Is there also any a good solution for finding the path (= the exact sequence of vertices) that encloses a strong component? (Note that in a strong component there can be also smaller subcycles that are not of interest.) With other words: I want to find the way through a strong component that visits all its edges. Thanks in advance! Stefan

3 2

Using shared_ptr<> with boost::lamda
by limaxtt 15 Aug '03

15 Aug '03

shared_ptr<> can't be easily used in lambda expressions, because there is no operator->* defined. So, there are two problems in two different libraries: 1) operator->* needs to be added to Smart Pointers library. It can be easily done for data-members, but not for methods, since it includes return type deduction from template parameters. So there is another problem: 2) boost::function_traits<> from Type Traits library (result_type particulary) does not work for class methods.

1 0

[Patch] Boost Jamfiles
by Administrator 15 Aug '03

15 Aug '03

The following changelog and patch do three things: 1. Change to common naming scheme for libs 2. Common subdir for compiled libs 3. Test and date_time dll's suppressed for NT builds. Would appreciate any and all feedback on this patch. Thanks. Dale Hirt Changelog: ---------- 2003-08-14 17:40 pm Dale Hirt <administrator(a)sbcltd.com> Jamfile * Added in boost-stage-tag rule. This appends a "d" to the end of the lib name if it is being compiled in debug mode, and "_pydebug", if being compiled in debug-python mode. Allows for common naming scheme across entire Boost tree. libs/date_time/build/Jamfile * Changes compilation options so that shared lib is not built if we're on NT. * Adds in stage rule to place libs in common subdir, and also to use common naming scheme per debug builds. libs/filesystem/build/Jamfile * Adds in stage rule to place libs in common subdir, and also to use common naming scheme per debug builds. libs/python/build/Jamfile * Changes stage rule to place libs in common subdir, and also to use common naming scheme per debug and debug-python builds. libs/regex/build/Jamfile * Changes stage rule to place libs in common subdir. libs/signals/build/Jamfile * Changes stage rule to use common naming scheme per debug builds. libs/test/build/Jamfile * Changes compilation options so that shared lib is not built if we're on NT. * Changes stage rule to use common naming scheme per debug builds. libs/thread/build/Jamfile * Changes stage rule to place libs in common subdir, and also to use common naming scheme per debug builds. Patch: -------- Index: Jamfile =================================================================== RCS file: /cvsroot/boost/boost/Jamfile,v retrieving revision 1.7 diff -r1.7 Jamfile 2a3,21 > # Common rules for libs > rule boost-stage-tag ( toolset variant : properties * ) > { > local lib-debug-opt = "" ; > if [ MATCH .*(debug).* : $(variant) ] > { > lib-debug-opt = d ; > } > > local lib-pydebug-opt = "" ; > if [ MATCH .*(debug-python).* : $(variant) ] > { > lib-pydebug-opt = _pydebug ; > lib-debug-opt = "" ; > } > > return $(properties) <tag><$(variant)>$(lib-debug-opt)$(lib-pydebug-opt) ; > } > Index: libs/date_time/build/Jamfile =================================================================== RCS file: /cvsroot/boost/boost/libs/date_time/build/Jamfile,v retrieving revision 1.9 diff -r1.9 Jamfile 24d23 < 29c28,29 < dll boost_date_time : ../src/gregorian/$(CPP_SOURCES).cpp --- > > lib boost_date_time : ../src/gregorian/$(CPP_SOURCES).cpp 34c34,37 < lib boost_date_time : ../src/gregorian/$(CPP_SOURCES).cpp --- > if ! ${NT} > { > > dll boost_date_time : ../src/gregorian/$(CPP_SOURCES).cpp 38a42,55 > stage ../../../lib > : <lib>boost_date_time <dll>boost_date_time > : boost-stage-tag > : debug release > ; > } > else > { > stage ../../../lib > : <lib>boost_date_time > : boost-stage-tag > : debug release > ; > } Index: libs/filesystem/build/Jamfile =================================================================== RCS file: /cvsroot/boost/boost/libs/filesystem/build/Jamfile,v retrieving revision 1.5 diff -r1.5 Jamfile 17c17,24 < ; \ No newline at end of file --- > ; > > stage ../../../lib > : <lib>boost_filesystem > : boost-stage-tag > : debug release > ; > Index: libs/python/build/Jamfile =================================================================== RCS file: /cvsroot/boost/boost/libs/python/build/Jamfile,v retrieving revision 1.29 diff -r1.29 Jamfile 78,83c78,81 < stage bin-stage : <dll>boost_python <lib>boost_python < : <tag><debug>"_debug" < <tag><debug-python>"_pydebug" < : < debug release < ; --- > stage ../../../lib : <dll>boost_python <lib>boost_python > : boost-stage-tag > : debug release > ; Index: libs/regex/build/Jamfile =================================================================== RCS file: /cvsroot/boost/boost/libs/regex/build/Jamfile,v retrieving revision 1.17 diff -r1.17 Jamfile 131c131 < stage bin-stage : <lib>boost_regex <dll>boost_regex --- > stage ../../../lib : <lib>boost_regex <dll>boost_regex Index: libs/signals/build/Jamfile =================================================================== RCS file: /cvsroot/boost/boost/libs/signals/build/Jamfile,v retrieving revision 1.6 diff -r1.6 Jamfile 27,28c27,28 < : <dll>boost_signals < : <tag><debug>"d" --- > : <dll>boost_signals <lib>boost_signals > : boost-stage-tag Index: libs/test/build/Jamfile =================================================================== RCS file: /cvsroot/boost/boost/libs/test/build/Jamfile,v retrieving revision 1.8 diff -r1.8 Jamfile 67a68,92 > stage ../../../lib : > <lib>boost_prg_exec_monitor > <lib>boost_test_exec_monitor > <lib>boost_unit_test_framework > <dll>boost_prg_exec_monitor > <dll>boost_test_exec_monitor > <dll>boost_unit_test_framework > : > boost-stage-tag > : > debug release > ; > } > else > { > stage ../../../lib : > <lib>boost_prg_exec_monitor > <lib>boost_test_exec_monitor > <lib>boost_unit_test_framework > : > boost-stage-tag > : > debug release > ; > Index: libs/thread/build/Jamfile =================================================================== RCS file: /cvsroot/boost/boost/libs/thread/build/Jamfile,v retrieving revision 1.20 diff -r1.20 Jamfile 47c47 < stage bin-stage --- > stage ../../../lib 50c50 < <tag><debug>"d" --- > boost-stage-tag

3 2

FW: Patch File For Common Library Subdir
by Administrator 15 Aug '03

15 Aug '03

Jeff, I do have a patch that will do the trick. It also deals with placing all libs into a common subdir of the root directory. If anyone is interested, let me know. Dale > -----Original Message----- > From: Jeff Garland [mailto:jeff@crystalclearsoftware.com] > Sent: Thursday, August 14, 2003 5:19 PM > To: Boost-Users(a)yahoogroups.com > Subject: RE: [Boost-Users] [date_time] library binaries for VC7.1? && > Comm on lib placement <snip> > > Exactly. I think the problem is that the build appears to be building > a valid .dll. I've wanted to turn this off, but I couldn't > figure out the > jamfile magic to make this happen and ran out of time to > pursue it. It's on > my todo list to fix this, but for now just use the static lib. > > Jeff

1 0

RE: [Boost-Users] Re: Using Boost as a Library Dependency
by Administrator 14 Aug '03

14 Aug '03

Jason, Speaking as someone who downloads and uses lots of open-source libraries, I expect that if another library is required, it will be stated in the documentation, and that it is up to me, the library user, to ensure that paths are correctly set up for my compiler. Just don't forget to include the website where I can download the required libraries. There should be no need to modify any of your (the developer's) library files in order for it to work. Compiler include paths are very easy to set up, both on Unix, where you would use something like autoconf to help set everything up, and on Windows, where Visual Studio has a simple directory include dialog box to type into. Again, you (the developer) should only need to state that the library requires another library(i.e. Boost), and me (the user) should be able to deal with it. If I can't, I (the user) actually need to RTFM about my compiler. Dale Hirt > -----Original Message----- > From: Jason Winnebeck [mailto:yg-boost-users@m.gmane.org] > Sent: Thursday, August 14, 2003 5:38 AM > To: boost-users(a)yahoogroups.com > Subject: [Boost-Users] Re: Using Boost as a Library Dependency > > > David Abrahams wrote: > > Jason Winnebeck <yg-boost-users(a)m.gmane.org> writes: > >>What do you want it to do? What is the least you expect it to > >>handle? > > > > > > ?? I don't understand your questions. You're the one with a problem > > that needs to be solved. > > Perhaps I was unclear. I was asking it in the sense of "were you to > download some non-commercial 3rd party library today that required > Boost, what would you reasonably expect to be required to do > to get it > to use your boost?" The next question was sort of a second > one asking > what you would have to do ideally but the answer there is > always nothing > ;). Ideally what I would expect is something where it is very simple > that requires you to type the path to your Boost once and only once. > > > Sure, or you're going to have to tell me about a location that gets > > put in the path used by your makefile so I can drop (a > symlink to) my > > boost tree there. The use of angle-includes is irrelevant to all > > this, at least as far as GCC/mingw are concerned. > > There are no symlinks in Windows. I suppose I can make an "include" > makefile where you place your Boost directory in there. For > some reason > this solution is trivial and I just thought of it. Well that makes > makefiles easy. As for Visual Studio... It's a bit more > complicated I > can look more to see what options I have. I know of at least one > solution if I can't find a better one. > > Jason > > > > > ------------------------ Yahoo! Groups Sponsor > ---------------------~--> > Buy Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark > Printer at Myinks.com. Free s/h on orders $50 or more to the > US & Canada. http://www.c1tracking.com/l.asp?cid=5511 > http://us.click.yahoo.com/l.m7sD/LIdGAA/qnsNAA/EbFolB/TM > -------------------------------------------------------------- > -------~-> > > Info: <http://www.boost.org> > Wiki: <http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl> > Unsubscribe: <mailto:boost-users-unsubscribe@yahoogroups.com> > > > Your use of Yahoo! Groups is subject to > http://docs.yahoo.com/info/terms/ > >

1 0

[date_time] library binaries for VC7.1?
by Dan Muller 14 Aug '03

14 Aug '03

I've been using boost for a while, but now for the first time I'm using a component that isn't entirely header-based, namely date_time in boost 1.30.0. After building boost for VC7.1, I find a .lib file in boost_1_30_0\libs\date_time\build\bin\libboost_date_time.lib\msvc\debug \runtime-link-dynamic and a .dll in boost_1_30_0\libs\date_time\build \bin\boost_date_time.dll\msvc\debug\runtime-link-dynamic. There are a couple of things that I don't understand about these files. Is the .lib file supposed to be the import library for the .dll? Linking against the .lib file hasn't produced any import references in my applications. Perhaps I'm just not hitting any out-of-line functionality, but it sure seems like the .lib file is a static library rather than an import library. Also, running DUMPBIN /EXPORTS on the .dll file shows no exported symbols related to date_time classes, as far as I can see. It really looks like it's exporting a bunch of stuff related to the standard C++ library, which makes no sense to me. Can anyone clear up my confusion? -- Dan Muller "So that's what an invisible barrier looks like!" (Time Bandits)

1 0

[BGL] patch to graphviz.hpp (cvs version)
by Angus Leeming 14 Aug '03

14 Aug '03

The following trivial patch is needed to compile write_graphviz from today's CVS. Regards, Angus Index: graphviz.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/graph/graphviz.hpp,v retrieving revision 1.18 diff -u -p -r1.18 graphviz.hpp --- graphviz.hpp 12 Aug 2003 01:15:37 -0000 1.18 +++ graphviz.hpp 14 Aug 2003 11:15:49 -0000 @@ -249,7 +249,7 @@ namespace boost { GraphPropertiesWriter gpw) { typedef typename property_map<Graph, vertex_index_t>::const_type vimap_t; - vimap_t vertex_index = get(g, vertex_index_t()); + vimap_t vertex_index = get(vertex_index_t(), g); typedef typename graph_traits<Graph>::directed_category cat_type; typedef graphviz_io_traits<cat_type> Traits; std::string name = "G";

2 1

Using Boost as a Library Dependency
by Jason Winnebeck 14 Aug '03

14 Aug '03

I recently decided to refactor my library's API using the benefits given by boost::shared_ptr, so this now means my library uses boost. I'm trying to figure out how my installation process should go. Since I'm only using shared_ptr I've trimmed down a custom boost version that is only a few hundred k (rather than 10 megs) of just the files that I use. I've put the minimum boost files in my own directory structure so that my library can compile on its own. But when using the library, then what would the user do? Ideally I could have the installer for my library by copy the files to the compiler's include directory, but that's not particularly nice, espically since Boost is quite a popular library, and I don't want to litter up their include directory and most espically not overwrite any installation of Boost they have placed there. One thing that might work, if compilers support include directory "overrides" is if the user is using the full Boost library, to place its -I line before (or after?) the -I for my library, so that they can see my includes, but any boost includes will be "overridden" by their full version of Boost. But this leads to another question: If I compile my library with Boost x but the user has Boost y installed when he links with my library (I DO pass shared_ptr back and forth between user code, so it's not just used internally), what will happen? The shared_ptr interface seems to be oft changing, and so right now my code would only compile for Boost 1.30 (or later? Speaking of that, anyone know why there are no files listed for download for Boost 1.30.1 but it was announced a week ago?). I'm new to these things so I appreciate any feedback or answers you have. The library is just an open-source library I'm writing on my own free time, and I don't have a lot of experience from using/installing commercial C++ libraries to draw upon. Jason Winnebeck

5 13

visitors question
by Jérémie Leguay 14 Aug '03

14 Aug '03

Hi! I would like to use the breadth breadth_first_search with simultaneaously 2 different visitors: -the distance recorder one -one of mine I was thinking about a code like: class bfs_my_visitor:public default_bfs_visitor { ... public: bfs_stop_visitor(...) {} template < typename Vertex, typename Graph > void finish_vertex(Vertex u, const Graph & g) const { ... } }; use in: bfs_my_visitor vis(...); breadth_first_search (g,s, visitor(make_bfs_visitor(std::make_pair(record_distances(&d[0],on_tree_edge()), vis ))); But it doesn't work, can you tell the way to combine thoses visitors in the call of breadth_first_search. regards Jérémie leguay Lip6 - Paris ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

Filesystem lib
by ALMAZ_N 13 Aug '03

13 Aug '03

Can someone help me? Has anyone used the above boost Filesystem library on Mac OS X? If you have can you tell me the obstacles you faced and how you overcame them? I am currently including the lib in my windows project and don't seem to have any problems. Thank you Almaz

1 0