Hi tcb, Thanks a lot for taking the time to do this! I don't have macos myself, so I could not fix those issues. I planned to install it on a VM on my laptop, but never got around to it due to lack of time.
I'll include your patches, but first I have to understand this libtool thing. I generated the tarballs with libtool version 2.2.6b, which as far as I know is the newest one, so what you are using must be a specific non-official modification for macos. The libtool script (ltmain.sh) is not included in graph-tool itself, and is generated (copied from the system) when the tarball is created. I don't know hot to include it, other than generating the tarball in a macos environment... Could you guys check if you run ./autogen.sh (with the git version of graph-tool) before building the package solves the libtool issue without copying it by hand? Could you also send me the ltmain.sh/libtool script you use? There are some more answers below. On 01/22/2010 01:25 AM, tcb wrote: > That's a great idea to take it into macports. I am only just checking > out graph-tool and it looks really nice, and a macports would > certainly be very useful. It also doesnt seem like it would be too > much work- I'm sure the macports guys would help out with the > autotools configuration- and other than the numpy patch it seems to > compile and run just fine on the mac. I have only compiled it 32-bit > with gcc44- I have not tried a 64-bit compile and I dont know if its > written to be 64bit safe (this would be very nice if it was). There > don't seem to be any tests which would be helpful in verifying that > the port was working- but a 32bit macport would be a start at least. 64 bit should not be a problem at all, and I use it on 64 bit machines all the time. > I initially found this project when I was looking for a working > version of the python bindings for the boost graph library- > development seems to be discontinued for some time. Can anyone confirm > if graph-tool is effectively a customised python binding for the bgl? > What would be involved in updating the python bgl bindings? I think graph-tool works as an effective python binding for the bgl, even though there are some algorithms there which are not (at this time) in the BGL, such as random graph generation, rewiring, community detection, triangulation and others. There are also some algorithms in the BGL which are not reflected in graph-tool, but I'm in the gradual process of incorporating them. Regarding python-bgl, I believe all it needs is a maintainer, since no one seems to be interested. The actual implementation is quite different from graph-tool, since they opt for a list-based adjacency list (which can be a performance killer) and try to be very close to the C++ API. In graph-tool I kept a certain distance from it to make things more comfortable in the python side (for instance, property map handling is way easier in graph-tool IMHO), and included other nice things such as graph filtering. Thanks again for helping out! Cheers, Tiago
signature.asc
Description: OpenPGP digital signature
_______________________________________________ graph-tool mailing list graph-tool@forked.de http://lists.forked.de/mailman/listinfo/graph-tool
