Hi,
Here is newer version,
- include files are at /usr/local/include/alsa-lib/{alsa/...}
- libraries at /usr/local/lib/alsa-lib/...
- alsa.m4 is at /usr/local/share/aclocal
- pkg-config files are at /usr/local/lib/pkgconfig
but renamed to alsa -> alsa-lib, alsa-topology -> alsa-lib-topolog
Hi,
> They do not, files would go in /usr/local/include/alsa-lib/alsa/xxx,
> add -I/usr/local/include/alsa-lib to CPPFLAGS (or CFLAGS if the build
> system doesn't cope with CPPFLAGS).
>
> Similar with LDFLAGS for libraries (and setting rpath may be needed
> too).
like inotify,
/usr/local/includ
On 2023/01/15 10:22, SASANO Takayoshi wrote:
> Hi,
>
> > Let's keep it simple like:
> > /usr/local/lib/alsa-lib/...
> > /usr/local/include/alsa-lib/...
>
> Really? I thought:
>
> /usr/local/alsa-lib/include
> /usr/local/alsa-lib/lib
>
> (how about /usr/local/linux-alsa/{include,lib}?)
>
> Both
On Sun, Jan 15, 2023 at 10:22:17AM +0900, SASANO Takayoshi wrote:
> Hi,
>
> > Let's keep it simple like:
> > /usr/local/lib/alsa-lib/...
> > /usr/local/include/alsa-lib/...
>
> Really? I thought:
>
> /usr/local/alsa-lib/include
> /usr/local/alsa-lib/lib
Sure this is fine as well :-)
> (how abo
Hi,
> Let's keep it simple like:
> /usr/local/lib/alsa-lib/...
> /usr/local/include/alsa-lib/...
Really? I thought:
/usr/local/alsa-lib/include
/usr/local/alsa-lib/lib
(how about /usr/local/linux-alsa/{include,lib}?)
Both are not difficult to write alsa-lib's Makefile
but very hard to porting
On Sat, Jan 07, 2023 at 12:39:00PM +, Stuart Henderson wrote:
> On 2023/01/07 13:25, Antoine Jacoutot wrote:
> > On Sat, Jan 07, 2023 at 08:11:22PM +0900, SASANO Takayoshi wrote:
> > > Hello,
> > >
> > > alsa-lib.tgz (take3) attached.
> > >
> > > > The most common method to deal with this in
Hi,
aaauuuggghhh, here is the archive. sorry!
On Sat, 07 Jan 2023 21:23:19 +0900,
Stuart Henderson wrote:
>
> On 2023/01/07 20:11, SASANO Takayoshi wrote:
> > Hello,
> >
> > alsa-lib.tgz (take3) attached.
> >
> > > The most common method to deal with this in ports is to continue to
> > > use /
On 2023/01/07 13:25, Antoine Jacoutot wrote:
> On Sat, Jan 07, 2023 at 08:11:22PM +0900, SASANO Takayoshi wrote:
> > Hello,
> >
> > alsa-lib.tgz (take3) attached.
> >
> > > The most common method to deal with this in ports is to continue to
> > > use /usr/local but install under subdirectories wi
On Sat, Jan 07, 2023 at 08:11:22PM +0900, SASANO Takayoshi wrote:
> Hello,
>
> alsa-lib.tgz (take3) attached.
>
> > The most common method to deal with this in ports is to continue to
> > use /usr/local but install under subdirectories with a non-standard
> > prefix, often 'e'; for example librar
On 2023/01/07 20:11, SASANO Takayoshi wrote:
> Hello,
>
> alsa-lib.tgz (take3) attached.
>
> > The most common method to deal with this in ports is to continue to
> > use /usr/local but install under subdirectories with a non-standard
> > prefix, often 'e'; for example libraries under /usr/local/
Hello,
> Having two audio layers with different semantics increases the
> probability of subtle audio problems (stuttering, desynchronization,
> etc.), which are very time-consuming to fix. Furthermore,
> alsa-over-sndio is very unlikely to work in all
> program/device/configuration combinations.
Hello,
alsa-lib.tgz (take3) attached.
> The most common method to deal with this in ports is to continue to
> use /usr/local but install under subdirectories with a non-standard
> prefix, often 'e'; for example libraries under /usr/local/lib/ealsa
> and headers under /usr/local/include/ealsa.
Ma
On Thu, Jan 05, 2023 at 03:31:57PM +0900, SASANO Takayoshi wrote:
> Hi,
>
> > Unless installed in a way to make it hard to pick up accidentally (e.g.
> > a non-standard directory, which has its own problems) I expect the
> > amount of work needed to cope with this in the rest of the ports tree
> >
On 2023/01/05 15:31, SASANO Takayoshi wrote:
> Hi,
>
> > Unless installed in a way to make it hard to pick up accidentally (e.g.
> > a non-standard directory, which has its own problems) I expect the
> > amount of work needed to cope with this in the rest of the ports tree
> > is likely to be quit
Hi,
> Unless installed in a way to make it hard to pick up accidentally (e.g.
> a non-standard directory, which has its own problems) I expect the
> amount of work needed to cope with this in the rest of the ports tree
> is likely to be quite a lot more than that needed to port a couple of
> appli
I'm worried that a lot of other ports will pick this up if installed.
'grep -wiR alsa' over build logs suggests it's in the order of a hundred
ports - apart from the problem of missing deps, we don't want it taking
priority over native sndio support in applications.
Unless installed in a way to ma
Hello,
> SHARED_LIBS = asound 0.0 # 2.0
> SHARED_LIBS += atopology 0.0 # 2.0
I will fix them before commit.
> with that fixed the port looks fine to me, and builds fine too. What
> I don't know is how it's supposed to be used. Is it needed to port
On 2023/01/04 16:48:05 +0900, SASANO Takayoshi wrote:
> Hello,
>
> - patch for configure.ac is simplified by your idea.
> (new diff is also posted to github)
thanks!
> - warning of pcm.c is fixed, but I use (long)status->x.tv_sec cast
> because of other printf() uses same thing. no %ld
Hello,
- patch for configure.ac is simplified by your idea.
(new diff is also posted to github)
- warning of pcm.c is fixed, but I use (long)status->x.tv_sec cast
because of other printf() uses same thing. no %ld -> %lld format change.
- add comment before NO_TEST
ok?
--
SASANO Takayosh
On 2023/01/03 11:25:23 +0900, SASANO Takayoshi wrote:
> Hi,
>
> previous ports cannot support alsa-plugin due to libdl detection,
> here is new ports with patch. (the patch is sent same as pull-request at
> https://github.com/alsa-project/alsa-lib/pull/290 )
looked for curiosity; the patch for c
Hi,
previous ports cannot support alsa-plugin due to libdl detection,
here is new ports with patch. (the patch is sent same as pull-request at
https://github.com/alsa-project/alsa-lib/pull/290 )
--
SASANO Takayoshi (JG1UAA)
alsa-lib.tgz
Description: Binary data
Hello,
to acclerate alsa-utils and alsa-plugin ports development,
post alsa-lib ports first. (I sent pull-request of alsa-utils for *BSD;
https://github.com/alsa-project/alsa-utils/pull/186 if there is no enough
time for us, use same diff in ports until they are merged)
--
SASANO Takayoshi (JG1U
22 matches
Mail list logo
