[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious
From: |
Thomas Schmitt |
Subject: |
Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious |
Date: |
Sun, 27 Jan 2019 18:54:02 +0100 |
Hi,
> I wonder if the errors should only be shown if an environment variable
> is set or something?
You could sort the messages of lib/driver/netbsd.c into libcdio's log level
spectrum, rather than using fprintf(stderr) or perror():
cdio_debug(), cdio_info(), cdio_warn(), cdio_error().
(I dimly remember to have had problems when trying to enable or disable
printing of those in the demo programs. But cdio_log_level_t in
include/cdio/logging.h gives hope that it can be done.)
Have a nice day :)
Thomas
- [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Edd Barrett, 2019/01/26
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Thomas Schmitt, 2019/01/26
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Edd Barrett, 2019/01/26
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Thomas Schmitt, 2019/01/26
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Edd Barrett, 2019/01/27
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Edd Barrett, 2019/01/27
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Thomas Schmitt, 2019/01/27
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Edd Barrett, 2019/01/27
- Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious,
Thomas Schmitt <=
Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Thomas Schmitt, 2019/01/26
Re: [Libcdio-devel] OpenBSD vs libcdio vs Audacious, Rocky Bernstein, 2019/01/26