From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] no-install clients in sbc project
Date: Mon, 15 Jan 2007 19:35:46 +0100 [thread overview]
Message-ID: <1168886146.31200.12.camel@violet> (raw)
In-Reply-To: <45ABC674.6000402@xmission.com>
Hi Brad,
> Is there a better way to put sbcenc and sbcdec into the sbc project and
> have them link than this? It seems a little underhanded to link libsbc.a
> this way:
>
> Index: src/Makefile.am
> ===================================================================
> RCS file: /cvsroot/sbc/sbc/src/Makefile.am,v
> retrieving revision 1.3
> diff -u -r1.3 Makefile.am
> --- src/Makefile.am 18 Feb 2006 22:19:47 -0000 1.3
> +++ src/Makefile.am 15 Jan 2007 18:20:44 -0000
> @@ -1,4 +1,6 @@
>
> -bin_PROGRAMS = sbcinfo
> +bin_PROGRAMS = sbcinfo sbcenc sbcdec
> +sbcenc_LDADD = ../lib/.libs/libsbc.a
> +sbcdec_LDADD = ../lib/.libs/libsbc.a
>
> MAINTAINERCLEANFILES = Makefile.in
that is totally wrong. Tell me what you are trying to achieve and I tell
you the autoconf/automake trick.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-01-15 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 18:22 [Bluez-devel] no-install clients in sbc project Brad Midgley
2007-01-15 18:35 ` Marcel Holtmann [this message]
2007-01-15 18:46 ` Brad Midgley
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=1168886146.31200.12.camel@violet \
--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 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.