Hello Mathis,

On Tue, 2007-28-08 at 17:40 +0200, Mathis Ahrens wrote:
> Hi all,
>
> (sorry, if this should be a dupiclate ...
> I found searching yahoo difficult.)
>
> I saw on the wiki (Blackboard:What_goes_on), there is on-going
> work regarding the build system (at least windows).
>
> I just tried to install beagle on gentoo/linux and had a few issues
> that you might want to consider. I am not an active user/developer
> (yet), so feel free to discard everything I say...
>
> 1. rename the package to openbeagle
> Yeah, you will probably not be keen on this, and I know that
> the other beagle [0] is more recent.
> Still, there are already name clashes right now regarding the
> file /usr/lib/libbeagle.so [1], and others may follow.
> And actually, you are half way there, considering this mailing list. ;)

I am aware of the "other" Beagle, and of the name clash it causes on
Gentoo. Few months ago, I mentionned the problem to developers list, but
nothing has been done yet.

http://sourceforge.net/mailarchive/message.php?msg_id=1173129315.20747.138.camel\
%40sad-consul03.drev.dnd.ca

I proposed to change the name of the libbeagle.so file for something
like libbeagle-core.so. But the suggestion of using the openbeagle
prefix, such as in libopenbeagle-ga.so or libopenbeagle-beagle.so, is
interesting. I will consider it as a permanent fix to avoid any future
name clashes.

> 2. change the default install to use 'openbeagle'-subdirs
> Right now, configuring and installing using default values, the
> result seems a little bit messy IMO. I cannot imagine any distribution
> wanting /usr/include/{Threading,Math,XML}.hpp being provided
> by an arbitrary package. Why not use /usr/include/openbeagle/* and
> /usr/lib/openbeagle/* ?
> Well, maybe rename /usr/include/openbeagle/beagle/* but maybe not.

PACC is a distinct project made by Marc Parizeau, one of the other of
Open BEAGLE.

http://manitou.gel.ulaval.ca/~parizeau/pacc/

Recent versions of PACC has the "PACC" prefix added in the include path,
as in "PACC/XML.hpp". Libraries are also starting with pacc
(libpacc-xml.so) and installed in a distinct directory (by
default, /usr/local/include/PACC). So any future name clashing with any
other common libraries should now being avoided.

An for Open BEAGLE, all header files are under the directory beagle (by
default, /usr/local/include/beagle). Inclusion in source code makes use
of prefix "beagle", such as in "beagle/System.hpp". I don't think it is
necessary to change it as the installation directory can be changed
easily via the configure script (--prefix or --includedir command-line
switches) in case of problems with other packages.

> 3. use pkgconfig
> Being useful for linking and compiling against openbeagle, this may
> help the transition. Seems to me that stuffing a single macro
> into your configure should create the necessary *.pc file. [2]

The CVS version of Open BEAGLE already provides pkgconfig files. I agree
it would help making transition smoother. That will be part of
forthcoming release of development version 3.1.0.

> Well, so much for my initial frustration ;)
> Let me know what you think.

I release of stable version 3.0.2 is scheduled soon. The code is ready,
I just need to do some testing on Windows and to package everything. But
no change regarding clashing with the other Beagle will be done -- it is
only a bug fix release, I tried to keep thing as similar as possible to
version 3.0.1. But for the development version (3.1.0), I will make the
necessary to avoid any name clashes.

Cheers,

Christian



> Cheers,
> Mathis
>
> [0] http://www.beagle-project.org
> [1] http://bugs.gentoo.org/show_bug.cgi?id=141137
> [2] http://autoconf-archive.cryp.to/ax_create_pkgconfig_info.html
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
--
Christian Gagné
http://cgagne.googlepages.com