Re: [Alsa-user] Fireworks
Brought to you by:
perex
|
From: Susie B. <su...@po...> - 2020-11-18 00:28:52
|
Hi,
(I'm sorry for the very long reply below...)
On Sun, 15 Nov 2020 23:39:22 +0900 Takashi Sakamoto <o-t...@sa...> wrote:
> The snd-firewire-ctl-services has dependencies to:
> - alsa-gobject
> - libhinawa
Yes. So now I'm trying to install the alsa-gobject at first.
> They are software I write, and have similar design. Both depends
> on GLib/GObject with GObject Introspection.
>
> GLib is a fundamental library for many applications, especially
> appliations of GNOME desktop environment, therefore I guess that
> you can easily find the way to resolve the dependency to build
> GLib/GObject applications in Linux distributions which has desktop
> environment.
>
> GObject Introspection is used to produce FFI functionality for
> language bindings. You can easily find the way to resolve the
> dependency as well. Recent release of Gtk supports GObject
> Introspection. As a tips, below files should be installed under
> the directory in which libgirepository searches typelib.
>
> * ALSACtl-0.0.gir
> * ALSAHwdep-0.0.gir
> * ALSARawmidi-0.0.gir
> * ALSASeq-0.0.gir
> * ALSATimer-0.0.gir
> * Hinawa-3.0.gir
>
> Additionally, alsa-gobject uses libudev to query kobject information
> in sysfs filesystem. You can find many applications use libudev and
> easily find the way to resolve dependency.
I checked my system and found it had these dependencies of the version below:
glib-2.46.2
gobject-introspection-1.46.0
eudev-3.1.5
I did't seek for the gir files because I guessed that they would be made in the build of alsa-gobject or libhinawa.
Then I made a clone of the project of alsa-gobject;
root@darkstar:/tmp# git clone https://github.com/alsa-project/alsa-gobject.git
and I moved into the directory and setup:
root@darkstar:/tmp/alsa-gobject# meson . build
Meson gave me the message below, and I guessed the setup was done well.
(Because there wasn't any "No" nor "Error".)
The Meson build system
Version: 0.55.3
Source dir: /tmp/alsa-gobject
Build dir: /tmp/alsa-gobject/build
Build type: native build
Using 'PKG_CONFIG_PATH' from environment with value: '/usr/local/lib64/pkgconfig:/usr/local/share/pkgconfig:/usr/lib64/pkgconfig:/usr/share/pkgconfig'
Using 'PKG_CONFIG_PATH' from environment with value: '/usr/local/lib64/pkgconfig:/usr/local/share/pkgconfig:/usr/lib64/pkgconfig:/usr/share/pkgconfig'
Project name: alsa-gobject
Project version: 0.1.0
C compiler for the host machine: ccache cc (gcc 5.5.0 "cc (GCC) 5.5.0")
C linker for the host machine: cc ld.bfd 2.26.20160125
Host machine cpu family: x86_64
Host machine cpu: x86_64
Found pkg-config: /usr/bin/pkg-config (0.29.2)
Using 'PKG_CONFIG_PATH' from environment with value: '/usr/local/lib64/pkgconfig:/usr/local/share/pkgconfig:/usr/lib64/pkgconfig:/usr/share/pkgconfig'
Run-time dependency gobject-2.0 found: YES 2.46.2
Using 'PKG_CONFIG_PATH' from environment with value: '/usr/local/lib64/pkgconfig:/usr/local/share/pkgconfig:/usr/lib64/pkgconfig:/usr/share/pkgconfig'
Run-time dependency libudev found: YES 220
Program glib-mkenums found: YES
Program glib-mkenums found: YES
Found pkg-config: /usr/bin/pkg-config (0.29.2)
Using 'PKG_CONFIG_PATH' from environment with value: '/usr/local/lib64/pkgconfig:/usr/local/share/pkgconfig:/usr/lib64/pkgconfig:/usr/share/pkgconfig'
Program glib-genmarshal found: YES
Using 'PKG_CONFIG_PATH' from environment with value: '/usr/local/lib64/pkgconfig:/usr/local/share/pkgconfig:/usr/lib64/pkgconfig:/usr/share/pkgconfig'
Build-time dependency gobject-introspection-1.0 found: YES 1.46.0
Program g_ir_scanner found: YES (/usr/bin/g-ir-scanner)
Program g_ir_compiler found: YES (/usr/bin/g-ir-compiler)
Dependency gobject-2.0 found: YES 2.46.2 (cached)
Dependency libudev found: YES 220 (cached)
Program glib-mkenums found: YES
Program glib-mkenums found: YES
Dependency gobject-2.0 found: YES 2.46.2 (cached)
Dependency libudev found: YES 220 (cached)
Program glib-mkenums found: YES
Program glib-mkenums found: YES
Dependency gobject-2.0 found: YES 2.46.2 (cached)
Dependency libudev found: YES 220 (cached)
Program glib-mkenums found: YES
Program glib-mkenums found: YES
Dependency gobject-2.0 found: YES 2.46.2 (cached)
Dependency libudev found: YES 220 (cached)
Program glib-mkenums found: YES
Program glib-mkenums found: YES
Program alsactl-enums found: YES
Program alsactl-card found: YES
Program alsactl-card-info found: YES
Program alsactl-elem-info found: YES
Program alsactl-elem-value found: YES
Program alsatimer-enums found: YES
Program alsatimer-device-info found: YES
Program alsatimer-device-status found: YES
Program alsatimer-device-params found: YES
Program alsatimer-user-instance found: YES
Program alsatimer-instance-info found: YES
Program alsatimer-instance-params found: YES
Program alsatimer-instance-status found: YES
Program alsaseq-enums found: YES
Program alsaseq-system-info found: YES
Program alsaseq-client-info found: YES
Program alsaseq-user-client found: YES
Program alsaseq-port-info found: YES
Program alsaseq-client-pool found: YES
Program alsaseq-subscribe-data found: YES
Program alsaseq-queue-info found: YES
Program alsaseq-queue-status found: YES
Program alsaseq-queue-tempo found: YES
Program alsaseq-queue-timer found: YES
Program alsaseq-event-cntr found: YES
Program alsahwdep-enums found: YES
Program alsahwdep-device-info found: YES
Program alsarawmidi-enums found: YES
Program alsarawmidi-substream-info found: YES
Program alsarawmidi-stream-pair found: YES
Program alsarawmidi-substream-params found: YES
Program alsarawmidi-substream-status found: YES
Build targets in project: 27
But When I tested the build, ninja put an error:
root@darkstar:/tmp/alsa-gobject/build# meson test
ninja: Entering directory `/tmp/alsa-gobject/build'
[23/80] Compiling C object src/timer/l...alsatimer.so.0.1.0.p/user-instance.c.o
../src/timer/user-instance.c: In function ‘alsatimer_user_instance_open’:
../src/timer/user-instance.c:170:14: warning: implicit declaration of function ‘strerror’ [-Wimplicit-function-declaration]
generate_syscall_error(error, errno, "open(%s)", devnode);
^
../src/timer/user-instance.c:170:109: warning: format ‘%s’ expects argument of type ‘char *’, but argument 7 has type ‘int’ [-Wformat=]
../src/timer/user-instance.c:179:105: warning: format ‘%s’ expects argument of type ‘char *’, but argument 7 has type ‘int’ [-Wformat=]
../src/timer/user-instance.c: In function ‘alsatimer_user_instance_choose_event_data_type’:
../src/timer/user-instance.c:255:109: warning: format ‘%s’ expects argument of type ‘char *’, but argument 7 has type ‘int’ [-Wformat=]
../src/timer/user-instance.c: In function ‘alsatimer_user_instance_attach’:
../src/timer/user-instance.c:291:109: warning: format ‘%s’ expects argument of type ‘char *’, but argument 7 has type ‘int’ [-Wformat=]
../src/timer/user-instance.c: In function ‘alsatimer_user_instance_attach_as_slave’:
../src/timer/user-instance.c:330:105: warning: format ‘%s’ expects argument of type ‘char *’, but argument 7 has type ‘int’ [-Wformat=]
../src/timer/user-instance.c: In function ‘alsatimer_user_instance_get_info’:
../src/timer/user-instance.c:364:109: warning: format ‘%s’ expects argument of type ‘char *’, but argument 7 has type ‘int’ [-Wformat=]
../src/timer/user-instance.c: In function ‘alsatimer_user_instance_set_params’:
../src/timer/user-instance.c:399:109: warning: format ‘%s’ expects argument of type ‘char *’, but argument 7 has type ‘int’ [-Wformat=]
../src/timer/user-instance.c: In function ‘alsatimer_user_instance_get_status’:
../src/timer/user-instance.c:434:109: warning: format ‘%s’ expects argument of type ‘char *’, but argument 7 has type ‘int’ [-Wformat=]
../src/timer/user-instance.c: In function ‘alsatimer_user_instance_start’:
../src/timer/user-instance.c:584:109: warning: format ‘%s’ expects argument of type ‘char *’, but argument 7 has type ‘int’ [-Wformat=]
../src/timer/user-instance.c: In function ‘alsatimer_user_instance_stop’:
../src/timer/user-instance.c:611:109: warning: format ‘%s’ expects argument of type ‘char *’, but argument 7 has type ‘int’ [-Wformat=]
../src/timer/user-instance.c: In function ‘alsatimer_user_instance_pause’:
../src/timer/user-instance.c:638:109: warning: format ‘%s’ expects argument of type ‘char *’, but argument 7 has type ‘int’ [-Wformat=]
../src/timer/user-instance.c: In function ‘alsatimer_user_instance_continue’:
../src/timer/user-instance.c:666:109: warning: format ‘%s’ expects argument of type ‘char *’, but argument 7 has type ‘int’ [-Wformat=]
[42/80] Compiling C object src/seq/libalsaseq.so.0.1.0.p/client-info.c.o
FAILED: src/seq/libalsaseq.so.0.1.0.p/client-info.c.o
ccache cc -Isrc/seq/libalsaseq.so.0.1.0.p -Isrc/seq -I../src/seq -Isrc -I../src -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -fPIC -MD -MQ src/seq/libalsaseq.so.0.1.0.p/client-info.c.o -MF src/seq/libalsaseq.so.0.1.0.p/client-info.c.o.d -o src/seq/libalsaseq.so.0.1.0.p/client-info.c.o -c ../src/seq/client-info.c
../src/seq/client-info.c: In function ‘seq_client_info_get_property’:
../src/seq/client-info.c:105:40: error: ‘struct snd_seq_client_info’ has no member named ‘card’
g_value_set_int(val, priv->info.card);
^
../src/seq/client-info.c:108:50: error: ‘struct snd_seq_client_info’ has no member named ‘pid’
g_value_set_int64(val, (gint64)priv->info.pid);
^
[44/80] Compiling C object src/seq/libalsaseq.so.0.1.0.p/user-client.c.o
ninja: build stopped: subcommand failed.
Could not rebuild /tmp/alsa-gobject/build
I tried to build as well, but get another error again.
root@darkstar:/tmp/alsa-gobject/build# meson build
ERROR: Neither directory contains a build file meson.build.
There was't meson.build file actually:
root@darkstar:/tmp/alsa-gobject/build# ls
build.ninja doc/ meson-logs/ meson-uninstalled/ tests/
compile_commands.json meson-info/ meson-private/ src/
I'm ashamed to say I have no idea where I went wrong in the above steps.
But I would appreciate any help or suggestion to resolve these errors.
> > Can I continue to ask for help in this thread?
> > Or should I make a new thread or move to another mailing list below?
>
> I don't mind which list you ask. I subscribe them. But in LAD, Len
> Ovens reports his experience to test snd-fireworks-ctl-service and
> filed some issues. You might get any help from him. Of cource, I can
> assist your test.
Thank you for the suggestion and offer. But I'd like to continue in this thread because I guess the above is perhaps only a newbie's careless mistake and not development-related issue.
Regards,
Susie B.
|