From: Takashi Iwai <tiwai@suse.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Karsten Wiese <annabellesgarden@yahoo.de>,
alsa-devel@lists.sourceforge.net
Subject: Re: Re: [PATCH]usx2yloader hotplugging in HEAD
Date: Tue, 02 Dec 2003 17:16:24 +0100 [thread overview]
Message-ID: <s5hy8tvci07.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5hwu9fec5j.wl@alsa2.suse.de>
At Tue, 02 Dec 2003 11:39:52 +0100,
I wrote:
>
> At Tue, 02 Dec 2003 11:35:47 +0100 (MET),
> Clemens Ladisch wrote:
> >
> > Takashi Iwai wrote:
> >
> > > Karsten Wiese wrote:
> > > >
> > > > Later there should also be some magic to (not) include the "/local" substring,
> > > > I don't know yet how to do that; anybody?
> > >
> > > fixed on cvs.
> > > tascam_fw and tascam_fpga will be generated via configure script now.
> >
> > Such scripts should not be generated by configure but by the Makefile.
> > For the reason and an example, see
> > http://www.gnu.org/software/autoconf/manual/autoconf-2.57/html_node/autoconf_24.html
>
> well, it means that the direct use $datadir is not adequet for C,
> etc. but for shell script it's ok - although it'd be better to define
> such a path explicitly. i'll work on it.
it turned out that we need define $bindir too.
but i don't think it's worthy to add extra options for that.
so, i think the current style is ok.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-12-02 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 8:31 [PATCH]usx2yloader hotplugging in HEAD Karsten Wiese
2003-12-02 10:05 ` Takashi Iwai
2003-12-02 10:35 ` Clemens Ladisch
2003-12-02 10:39 ` Takashi Iwai
2003-12-02 16:16 ` Takashi Iwai [this message]
2003-12-02 11:30 ` Karsten Wiese
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=s5hy8tvci07.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=annabellesgarden@yahoo.de \
--cc=clemens@ladisch.de \
/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