qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Liviu Ionescu <ilg@livius.net>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] MinGW build
Date: Fri, 28 Nov 2014 07:20:38 +0100	[thread overview]
Message-ID: <54781436.7020604@weilnetz.de> (raw)
In-Reply-To: <2861033C-03F0-4895-B00F-DE19BF4EEC5C@livius.net>

Am 27.11.2014 um 22:38 schrieb Liviu Ionescu:
> 
> On 27 Nov 2014, at 23:14, Stefan Weil <sw@weilnetz.de> wrote:
> 
>> Do you really need statically linked executables
> 
> actually I don't know, my experience with Windows is limited :-(
> 
> on OS X, if I distribute a folder containing an executable and a bunch of dynamic libraries, the folder where the executable is located is the first choice for searching the libraries, so I don't have to mess with library versions in any system library folders.
> 
> on Windows I could not make this work. if this is possible, and you have a procedure to create a setup that does a reasonable job without messing other things, ok, I don't mind packing an executable and several dynamic libraries, I'll use it too.

Windows dynamic libraries (DLL files) are also loaded from the
executable's directory if they exist there. You don't need a special
setup to make that work, it's the standard behaviour.

Regards
Stefan

  reply	other threads:[~2014-11-28  6:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 19:55 [Qemu-devel] MinGW build Liviu Ionescu
2014-11-26 20:13 ` Peter Maydell
2014-11-26 20:19   ` Stefan Weil
2014-11-26 21:44   ` Liviu Ionescu
2014-11-27 16:43   ` Liviu Ionescu
2014-11-27 19:34     ` Peter Maydell
2014-11-27 19:57       ` Liviu Ionescu
2014-11-27 20:09         ` Stefan Weil
2014-11-27 20:14           ` Liviu Ionescu
2014-11-27 20:18           ` Peter Maydell
2014-11-27 20:27             ` Liviu Ionescu
2014-11-27 22:04               ` Peter Maydell
2014-11-28  0:30                 ` Liviu Ionescu
2014-11-28  7:14             ` Stefan Weil
2014-11-28  8:41               ` Peter Maydell
2015-11-27 18:49               ` Peter Maydell
2015-11-27 19:16                 ` Stefan Weil
2015-11-27 21:05                   ` Peter Maydell
2015-11-29 12:03                     ` Juan Quintela
2015-12-03 11:58                       ` Peter Maydell
2015-12-03 14:15                         ` Peter Maydell
2015-12-03 14:30                           ` Juan Quintela
2015-11-30 13:24                 ` Juan Quintela
2015-11-30 13:29                   ` Stefan Weil
2014-11-27 20:52           ` Liviu Ionescu
2014-11-27 21:14             ` Stefan Weil
2014-11-27 21:38               ` Liviu Ionescu
2014-11-28  6:20                 ` Stefan Weil [this message]
2014-11-28  6:23                   ` Liviu Ionescu
2014-11-28  7:03                     ` Stefan Weil
2014-12-01 10:30                       ` Liviu Ionescu
2014-12-01 18:42                         ` Stefan Weil
2014-12-02 18:28                           ` Liviu Ionescu

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-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54781436.7020604@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=Qemu-devel@nongnu.org \
    --cc=ilg@livius.net \
    --cc=peter.maydell@linaro.org \
    /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.
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 NNTP newsgroup(s).