Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Makefile.am dependency problem
Date: Thu, 27 Oct 2005 10:07:38 +0200	[thread overview]
Message-ID: <1130400458.32634.14.camel@blade> (raw)
In-Reply-To: <436044E9.8020703@xmission.com>

Hi Brad,

> >>I noticed a strange dependency problem... it's common in bluez where a
> >>library is used. Header file changes don't force a recompile:
> > 
> > look at the bootstrap file. I forced this behavior.
> 
> The principle of "least surprise" would suggest that 'make' always
> rebuilds everything as necessary. At least I would do that in my project
> if I could figure out how to do it in the autosplat stuff.

I changed it in the BlueZ CVS to give it a try again. I can't remember
why I disabled it, but there was a reason for it. You might wanna take a
look at bootstrap and bootstrap-configure now.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-10-27  8:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-26 22:05 [Bluez-devel] Makefile.am dependency problem Brad Midgley
2005-10-26 22:13 ` Marcel Holtmann
2005-10-27  3:09   ` Brad Midgley
2005-10-27  8:07     ` 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=1130400458.32634.14.camel@blade \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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