From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <8a8adccc0712161449r135b552ct39f2cb9bcdeb543d@mail.gmail.com> Date: Sun, 16 Dec 2007 23:49:02 +0100 From: "Jaap A. Haitsma" Sender: jaap.haitsma@gmail.com To: "Marcel Holtmann" Subject: Re: [PATCH] Bluez build system Cc: bluez-devel@lists.sourceforge.net In-Reply-To: <1197841752.8050.42.camel@aeonflux> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <8a8adccc0709020615m38389d6axe49041f8fbe18c4b@mail.gmail.com> <1188768824.24968.9.camel@violet> <8a8adccc0712161246y3f435aefwdb6c92c464d19f96@mail.gmail.com> <1197841752.8050.42.camel@aeonflux> List-ID: On Dec 16, 2007 10:49 PM, Marcel Holtmann wrote: > Hi Jaap, > > > With a couple of months delay but here it is. > > > > Attached you find autogen.sh. Just put this file in the gnome > > directory of bluez and gnome-bluetooth can be build with jhbuild. NOTE > > you need to have the package gnome-common installed. gnome-common > > contains common scripts and macros to make developing GNOME apps > > easier > > that is not gonna happen since even if it is called bluez-gnome, it can > be build and used without GNOME. Its only dependency is GTK+. So > depending on gnome-common is not an option. It's a build time dependency only. There is no run time dependency. > > The files bootstrap and bootstrap-configure can be removed because > > autogen.sh is now doing that job. > > I actually like bootstrap and bootstrap-configure, because they do > exactly the right job for the developers. > I'd like to have autogen.sh because then bluez gnome can get build with jhbuild I then see two options 1) Add autogen.sh as is and also leave the bootstrap files in CVS 2) I'll need to hack up an autogen.sh which doesn't need gnome-common. I'm not an autofoo expert but I guess that can be done What's acceptable for you? Jaap