All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] btsco: help with autoconf cleanup
Date: Thu, 11 Nov 2004 11:49:55 -0700	[thread overview]
Message-ID: <4193B453.50005@xmission.com> (raw)

Hi

Can someone tell me which of these files shouldn't be in our btsco cvs 
module?

acinclude.m4
aclocal.m4
config.status
configure
configure.in
Makefile
Makefile.am
Makefile.in
missing
mkinstalldirs

I know some projects even make you generate "configure" but I'm not sure 
I want to go that far.

btw, I added a sort of placeholder "a2play.c" to the project for sending 
preencoded audio to an a2dp player. I want to make sure our autoconf 
mess is cleaned up before putting it in the build.

Brad


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel/listinfo/bluez-devel

             reply	other threads:[~2004-11-11 18:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-11 18:49 Brad Midgley [this message]
2004-11-11 18:56 ` [Bluez-devel] btsco: help with autoconf cleanup Marcel Holtmann
2004-11-11 21:04   ` Brad Midgley
2004-11-11 21:16     ` Marcel Holtmann
2004-11-11 23:14       ` Brad Midgley
2004-11-12  1:02         ` Marcel Holtmann
2004-11-15 17:31 ` David Woodhouse
2004-11-15 21:29   ` Brad Midgley
2004-11-16  6:39     ` Simon Vogl

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=4193B453.50005@xmission.com \
    --to=bmidgley@xmission.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.