Commit to FindOpenBabel.cmake

Guten Morgen

I just synced Avo with KDEs Find*.cmake-files. Commit r190 is this, I don’t
know if you can those commits as emails. In KDE we have a
kde-commits-mailinglist which recieves every commit in KDEs svn. Then we have
a nice filter, so that for example I only get commits in kdeedu and kdelibs.
Very handy and easy to install (feature is called “svn hook”). No idea if you
are technically able to install it on sf.net… Ok, just to be sure you all
get the commit with my questions:

===============================================================

This syncs Avo with KDE again. Beside some cosmetic sugar this adds much
improved support for Windows (I think…). Anyway, we now have for
example this line in the file:

[HKEY_CURRENT_USER\SOFTWARE\OpenBabel\ 2.0.2]

I think that we all agree that both Kalzium and Avo want to depend on OB
2.1.0, right? The current beta still installs as 2.0.2 which cannot be
the correct way to do, I think. Geoff told us yesterday that branching
is about 2 weeks in the future, please lets increase that version number
then so that those clashes can be fixed!
– Diese und die folgenden Zeilen werden ignoriert –

M modules/FindOpenBabel2.cmake

===============================================================

On Mar 15, 2007, at 4:05 AM, Carsten Niehaus wrote:

Very handy and easy to install (feature is called “svn hook”). No
idea if you
are technically able to install it on sf.net

Yes, it’s avogadro-updates
https://lists.sourceforge.net/lists/listinfo/avogadro-updates

I think that we all agree that both Kalzium and Avo want to depend
on OB
2.1.0, right? The current beta still installs as 2.0.2 which cannot be
the correct way to do, I think.

I don’t think there’s a Windows installer for OB 2.1 betas yet. If
so, please report it to the developer list, so the Windows installer
can be updated. Certainly on UNIX, it reports itself as 2.1.0b6 or
2.1.0b7.

Cheers,
-Geoff

Am Donnerstag, 15. März 2007 13:39 schrieben Sie:

I think that we all agree that both Kalzium and Avo want to depend
on OB
2.1.0, right? The current beta still installs as 2.0.2 which cannot be
the correct way to do, I think.

I don’t think there’s a Windows installer for OB 2.1 betas yet. If
so, please report it to the developer list, so the Windows installer
can be updated. Certainly on UNIX, it reports itself as 2.1.0b6 or
2.1.0b7.

Sorry, on windows it installs itself as 2.0.2 it seems. I have no windows and
cannot test this. The 2.0.2-stuff was added by somebody porting KDE to
windows so I took it for granted.
Perhaps that guy simply mixed 2.0.x and 2.1.x.

Carsten