sox-devel@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Ulrich Klauer <ulrich@chirlu.de>
To: sox-devel@lists.sourceforge.net
Subject: Re: Building a Windows binary
Date: Sun, 10 Mar 2013 06:57:12 +0100	[thread overview]
Message-ID: <20130310065712.Horde.x-t2XruWis5RPCC4Qt9lizA@webmail.df.eu> (raw)
In-Reply-To: <CAGzDe_Z8oqM_pDv5NR6NAYQyYbO8WV0+8eznFWgCXj_oCzetPg@mail.gmail.com>

Chris Bagwell <chris@cnpbagwell.com>:

> Sounds promising solution.  I especially like how it downloads everything
> so we can move between build computers much faster.

Yes, although "fast" is relative; it takes its time to build  
everything from scratch, especially GCC (about twenty minutes for me;  
a faster computer might help). But this can run in the background, of  
course.

> Can you tell MXE to build and prefer static libraries so that we can ship a
> minimal of DLL's?  Its not a show stopper if we don't but it does reduce
> some run-time issues.

Yes, it already builds static-only libraries by default. My test  
builds don't require any DLLs at all (not even zlib), except for those  
that have --enable-dl-XXX for legal reasons. (The newest is at  
http://www.chirlu.de/temp/sox-win32-experimental/, by the way; it is  
from relatively-current git master though, not from 14.4.0.)

I also found out recently that libtool recognizes an option  
"-all-static" when linking executables. It will then statically link  
everything, even indirect dependencies, and even when dynamic  
libraries are also present. I think I will make a configuration option  
for that and remove the workarounds.

Ulrich


------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev

      reply	other threads:[~2013-03-10  5:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 16:40 Building a Windows binary Ulrich Klauer
2013-03-09 17:55 ` Chris Bagwell
2013-03-10  5:57   ` Ulrich Klauer [this message]

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=20130310065712.Horde.x-t2XruWis5RPCC4Qt9lizA@webmail.df.eu \
    --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).