sox-devel@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: manus@riseup.net
To: sox-devel@lists.sourceforge.net
Subject: Re: Build systems
Date: Mon, 03 Aug 2020 05:40:55 -0700	[thread overview]
Message-ID: <c75d9138e43719c1df286b0dad1fe377@riseup.net> (raw)
In-Reply-To: <20200803113114.GA30556@www.stare.cz>

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?

Magnus

On 2020-08-03 13:31, Jan Stary wrote:
> On Aug 03 11:38:29, claude@xenei.com wrote:
>> Would the new tool work on strange platforms like pi-zero?
> 
> It's matter of the OS, not the HW platform.
> 
> 
>> On Mon, Aug 3, 2020 at 10:09 AM Måns Rullgård <mans@mansr.com> wrote:
>>
>> > Jan Stary <hans@stare.cz> writes:
>> >
>> > > On Aug 02 15:21:55, mans@mansr.com wrote:
>> > >> In the SoX tree, there are currently support files for autotools, CMake,
>> > >> and two ancient versiona of Visual Studio.
>> > >>
>> > >> Out of the box, the CMake build fails, but with the right options it
>> > >> completes successfully, for now.  The Visual Studio projects are almost
>> > >> certainly broken.
>> > >>
>> > >> Maintaining multiple build systems seems to me like an unnecessary
>> > >> burden.  I am therefore tempted to simply delete all but the autotools
>> > >> based one.  If nobody makes a compelling argument for keeping these
>> > >> extra build systems, I intend to do this next time a change would
>> > >> require updating them.
>> > >
>> > > Please do kill the VS build and the CMake build with fire.
>> >
>> > With pleasure, but I'll wait a little while in case someone has a good
>> > reason to keep it.  Given the lack of development activity the last few
>> > years, though, I'm quite confident nobody will object.
>> >
>> > > That being said, I would like to replace
>> > > the autotools hell with something like
>> > > https://cvsweb.bsd.lv/mandoc/configure
>> > > - a short, simple ./configure script written by hand,
>> > > as opposed to produced by auto*
>> >
>> > While I'm no fan of autotools, the existing script works.  I'll consider
>> > replacements if maintaining it becomes too much of a burden.
>> >
>> > --
>> > Måns Rullgård
>> >
>> >
>> > _______________________________________________
>> > SoX-devel mailing list
>> > SoX-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/sox-devel
>> >
>>
>>
>> --
>> I like: Like Like - The likeliest place on the web
>> <http://like-like.xenei.com>
>> LinkedIn: http://www.linkedin.com/in/claudewarren
> 
> 
> _______________________________________________
> SoX-devel mailing list
> SoX-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-devel


_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel

  reply	other threads:[~2020-08-03 12:41 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 [this message]
2020-08-03 17:01           ` Måns Rullgård
2020-08-03 17:21             ` Taylor Holberton
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=c75d9138e43719c1df286b0dad1fe377@riseup.net \
    --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).