From: Jan Stary <hans@stare.cz>
To: sox-devel@lists.sourceforge.net
Subject: ladspa support detection
Date: Mon, 24 Aug 2020 00:23:45 +0200 [thread overview]
Message-ID: <20200823222345.GA89723@www.stare.cz> (raw)
Running the new ./configure (from the new-build branch)
autodetects LADSPA as enabled:
LADSPA effect plugins yes
I don't have anything ladspa-related installed
(or is nothing particular required to "enable" ladspa?)
I am not sure how ./configure decided that ladspa is available here.
I have not specified --with-ladspa; is it the default?
I cannot tell from ./configure --help, it uses both
--with-ladspa Enable LADSPA plugin support (yes/no/*)
--with-magic Use magic (YES/no/*)
What is the difference between "yes" and "YES"?
Also, there seems to be an inconsistency
in naming of the config variable - it's
/* Define if LADSPA support is enabled */
#define HAVE_LADSPA_H 1
For everything else, HAVE_*_H means presence of the header file, as in
/* Define to 1 if you have the <id3tag.h> header file. */
#define HAVE_ID3TAG_H 1
while the functionality is configured with
/* Define if id3_file_open exists in -l$sox_wl */
#define HAVE_ID3TAG 1
(I don't have ladspa.h if that's what is meant.)
Jan
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
next reply other threads:[~2020-08-23 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 22:23 Jan Stary [this message]
2020-08-24 11:09 ` ladspa support detection Måns Rullgård
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200823222345.GA89723@www.stare.cz \
--to=sox-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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).