From: Taylor Holberton <taylorcholberton@gmail.com>
To: sox-devel@lists.sourceforge.net
Subject: Re: Build systems
Date: Mon, 3 Aug 2020 12:21:49 -0500 [thread overview]
Message-ID: <CAEj6FjbmDNf7bfuAZ4X6ptUf8O-4qod_csnXmyMpP-CFEBo=sQ@mail.gmail.com> (raw)
In-Reply-To: <yw1xzh7bwtmu.fsf@mansr.com>
[-- Attachment #1.1: Type: text/plain, Size: 1271 bytes --]
IMO without really knowing who uses SoX the most, it's really a shot in the
dark.
Personally, I think CMake is a way more capable system. But if the
developers of
SoX prefer Autotools, then go with that. Whoever contributes the most to
the project
should really have the final say, if you're not making the decision from a
user standpoint.
Just going on the fact that SoX is a C library that is licensed under GPL,
I'd be willing
to bet that most people who use it are also using Autotools.
On Mon, Aug 3, 2020 at 12:02 PM Måns Rullgård <mans@mansr.com> wrote:
> manus@riseup.net writes:
>
> > Hi all,
> >
> > the CMake builds fails for you? I just tested it on Windows and WSL and
> > on both platforms the build completes successfully. As it works for me,
> > I'm in favour of keeping it. Which options do you need to pass to CMake
> > for the build to succeed?
>
> It messes up with the gsm library.
>
> The fact that it works for you isn't a particularly strong argument for
> keeping it. Can you not use the autoconf system?
>
> --
> Måns Rullgård
>
>
> _______________________________________________
> SoX-devel mailing list
> SoX-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-devel
>
[-- Attachment #1.2: Type: text/html, Size: 1948 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
next prev parent reply other threads:[~2020-08-03 17:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 14:21 Build systems Måns Rullgård
2020-08-02 17:17 ` Jan Stary
2020-08-03 9:09 ` Måns Rullgård
2020-08-03 10:38 ` Claude Warren
2020-08-03 11:31 ` Jan Stary
2020-08-03 12:40 ` manus
2020-08-03 17:01 ` Måns Rullgård
2020-08-03 17:21 ` Taylor Holberton [this message]
2020-08-03 12:29 ` Måns Rullgård
2020-08-11 14:25 ` Jan Stary
2020-08-11 14:29 ` Måns Rullgård
2020-08-11 16:18 ` Jan Stary
2020-08-11 16:34 ` 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='CAEj6FjbmDNf7bfuAZ4X6ptUf8O-4qod_csnXmyMpP-CFEBo=sQ@mail.gmail.com' \
--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).