Re: Q: How to build garnome-2.12.1 under Fedora Core 4 (dbus/monodoc issues)?

["Joseph E. Sacco, PhD" <joseph_sacco comcast net>]

Once upon a time, mono/beagle required dbus-sharp. The post-install
target was added mono/mono to insure that dbus-sharp would be built if
it did not already exist.

The simplest thing to do to get you going is first build dbus without
any of the mono dependencies.

As to "who is to blame for this ugliness?"  I am... [:-)]

When I get some free cycles I will explore the consequences of building
GARNOME in the presence of a pre-existing mono-stack [which is a known
problem].  

The major issue to resolve is whether or not to use a pre-existing
mono-stack. The current thinking has been *not* to use a pre-existing
mono-stack to insure that GARNOME builds a mono-stack that is always
"appropriate" for the GARNOME mono-based applications.

If you take a look at the GARNOME Makefile for dbus, you can see how you
might resolve this issue by setting additional CONFIGURE_ARGS based on
the presence or absence of package configuration files.

-Joseph

====================================================================================
On Sun, 2005-10-09 at 04:07 +0200, Mirco "MacSlow" M�wrote:
> Greetings everybody!
> 
> 	I've got mono (monodoc etc.) installed system-wide on my Fedora Core 4
> box. This leads to a failure of the install make-target of the
> dbus-garball. During the configure-stage it finds the
> system-wide /usr/bin/monodoc and later (install-stage) tries to install
> stuff in /usr/lib/monodoc/sources, which is certainly != my set
> install-directory of...
> 
> 	/opt/garnome-2.12.1
> 
> which I stated in gar.conf.mk. Of course it fails to install anything
> in /usr/lib/monodoc/sources because I'm running this as a special
> build-user as advised in the garnome-docs, who dosen't a have the needed
> write-permissions for this.
> 
> 	Trying to force the installation of all the mono-bits from
> the ./garnome-2.12.1/mono directory leads to the very same issues. The
> dependency-chain runs me into the same issue with dbus again. I think
> commenting those mono-related lines in the Makefile of the dbus-garball
> and adding --disable-mono-doc and --disable-mono to the arguments passed
> to configure isn't the wisest idea either. So who's to blame for this
> ugliness? ;-)
> 
> Thanks in advance for your time and kind advice!
> 
> Best regards...
> 
> MacSlow
> 
> -- 
> Mirco "MacSlow" M�<macslow bangang de>
> 
-- 
joseph_sacco [at] comcast [dot] net