On Tue, Oct 16, 2012 at 10:26:24AM +0100, Noel O'Boyle wrote:
> My only concern is that this adds to the complexity of maintaining the
> bindings (or am I wrong about this? - is it the same?). For your own
> purposes, could you not copy out the installed binding files (there
> are just two), before rerunning against a different Python (no rebuild
> of the entire OB library required). I do something similar when
> creating the Windows Python packages.

Obviously it adds to the complexity, even more so because the
new code is really bare-bones. But I don't think the added
overhead is large and I tried to keep it at minimum. Suggestions
how to improve it are welcome.

For my own purposes I can build also OB five times as I did
before the release to test with Python 2.6, 2.7, 3.1 and 3.2 and
also the static build (+most of them also with eigen2 and 3).
And I didn't even look at other bindings yet. I have a couple of
bash convenience functions which help to symlink right build_dir
for each configuration, so I don't have to change configuration
each time and can use one alias to set paths so I can use any
one of them if I choose so.

But what I want to do here is different. I don't want to compile
OB library and plugins at all if I already have system install
with right version (which is the case currently on Gentoo where
bindings are compiled after the rest of the OB has already been
installed). I want to compile just the bindings against system
install, run all Python tests and install bindings (taking care
for the RPATHs if necessary) where Python can find them and do
that for each Python version I have asked for (now normally that
would be 2.7 and 3.2). But without these changes I can't do it.
With these I can do it and have written an ebuild using it.

I haven't yet pushed the new ebuilds because I want to know if
it is acceptable to have it in OB so I don't have to maintain it
outside for Gentoo (in which case maintaining the old setup.py
file is much more easy).

Still I think this would be useful to have also in OB outside
Gentoo packaging. Current implementation shifts all the burden
of installing to user, but we can at least to try to make that
easier. This doesn't change default behaviour, but it exposes
for customization some of build system variables.

Note that this patch still requires manual copying of bindings
to site-packages if building together with the rest of OB, since
there is no way to provide different install dirs for bindings.
I could try to look into it, but it is not really necessary for
what I'm using it.


Reinis

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
OpenBabel-Devel mailing list
OpenBabel-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbabel-devel

Reply via email to