From: Marcel Holtmann <marcel@holtmann.org>
To: "Jaap A. Haitsma" <jaap@haitsma.org>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [PATCH] Bluez build system
Date: Wed, 19 Dec 2007 00:28:27 +0100 [thread overview]
Message-ID: <1198020507.8050.205.camel@aeonflux> (raw)
In-Reply-To: <8a8adccc0712181417n6c0b5052i4e37137c24748a6a@mail.gmail.com>
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.
> > > >
> > > > I am making no difference in build or runtime dependency here. Every
> > > > extra dependency is bad. Especially if they are useless.
> > > >
> > > > > > > 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
> > > >
> > > > Is it a modified autogen.sh or a standard one? Do it have to be inside
> > > > the tarball or is CVS enough?
> > > >
> > > Just needs to be in CVS. It won't be part of the tarball. I guess it's
> > > just a standard one, but as I said I'm not an expert at it. I'll look
> > > into other projects which use autogen.sh but don't use gnome-common
> >
> > if it only will be in the CVS for jhbuild, then you don't have to modify
> > anything. Simply make sure it is a really default one and I put it
> > there.
> >
> New autogen.sh with no dependencies on gnome-common attached
I put that on into the CVS now. Everything should be good then.
Regards
Marcel
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-12-18 23:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8a8adccc0709020615m38389d6axe49041f8fbe18c4b@mail.gmail.com>
[not found] ` <1188768824.24968.9.camel@violet>
2007-12-16 20:46 ` [PATCH] Bluez build system Jaap A. Haitsma
2007-12-16 21:49 ` [Bluez-devel] " Marcel Holtmann
2007-12-16 22:49 ` Jaap A. Haitsma
2007-12-17 1:00 ` [Bluez-devel] " Marcel Holtmann
2007-12-17 6:52 ` Jaap A. Haitsma
2007-12-17 19:06 ` [Bluez-devel] " Marcel Holtmann
2007-12-18 22:17 ` Jaap A. Haitsma
2007-12-18 22:39 ` [Bluez-devel] " Didier Link
2007-12-18 23:30 ` Marcel Holtmann
2007-12-18 23:28 ` Marcel Holtmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1198020507.8050.205.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jaap@haitsma.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).