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 00:13:11 +0200 [thread overview]
Message-ID: <1130364791.32634.1.camel@blade> (raw)
In-Reply-To: <435FFD9B.1030904@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:
>
> bmidgley@jag:/usr/src/bluez/utils/common$ make
> make: Nothing to be done for `all'.
> bmidgley@jag:/usr/src/bluez/utils/common$ touch textfile.h
> bmidgley@jag:/usr/src/bluez/utils/common$ make
> make: Nothing to be done for `all'.
> bmidgley@jag:/usr/src/bluez/utils/common$ touch textfile.c
> bmidgley@jag:/usr/src/bluez/utils/common$ make
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -Wall -O2 -c textfile.c
> rm -f libtextfile.a
> ar cru libtextfile.a textfile.o
> ranlib libtextfile.a
> /bin/sh ../libtool --tag=CC --mode=link gcc -Wall -O2 -o
> test_textfile test_textfile.o libtextfile.a
> gcc -Wall -O2 -o test_textfile test_textfile.o libtextfile.a
>
> Makefile.am has a line that mentions textfile.h:
>
> libtextfile_a_SOURCES = textfile.h textfile.c
>
> but that doesn't seem to be enough.
look at the bootstrap file. I forced this behavior.
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
next prev parent reply other threads:[~2005-10-26 22:13 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 [this message]
2005-10-27 3:09 ` Brad Midgley
2005-10-27 8:07 ` Marcel Holtmann
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=1130364791.32634.1.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