On 09/23/2015 09:52 AM, John Snow wrote:
>>> +Windows platform portability
>>> +
>>> +
>>> +On Windows all binaries have a 'exe' suffix, so all the Makefile rules
>>
>> This was
>>
>> "a .exe suffix"
>>
>> before, and Jon commented that you probably pronounced it as "
On 09/23/2015 11:46 AM, Laszlo Ersek wrote:
> I diffed this version against v1. Thank you for addressing my comments
> too; however I found some newly introduced typos:
>
> On 09/23/15 11:59, Daniel P. Berrange wrote:
>
>> +The utility code that is used by all binaries is built into a
>> +stati
I diffed this version against v1. Thank you for addressing my comments
too; however I found some newly introduced typos:
On 09/23/15 11:59, Daniel P. Berrange wrote:
> +The utility code that is used by all binaries is built into a
> +static archive called libqemuutil.a, which is then linked to al
On 09/23/15 17:46, Laszlo Ersek wrote:
> before, and Jon commented that you probably pronounced it as "a dot-exe
Aaargh, John <-> Jon drives me crazy. Sorry.
Laszlo
On 09/23/2015 05:59 AM, Daniel P. Berrange wrote:
> Developers who are new to QEMU, or have a background familiarity
> with GNU autotools, can have trouble getting their head around the
> home-grown QEMU build system. This document attempts to explain
> the structure / design of the configure scr
A few nits that missed my first review:
On 23/09/2015 11:59, Daniel P. Berrange wrote:
> +A further complication for the system and userspace emulator binaries is
> +that two separate binaries need to be generated.
A further complication for the system emulator binaries (Windows does
not support
Developers who are new to QEMU, or have a background familiarity
with GNU autotools, can have trouble getting their head around the
home-grown QEMU build system. This document attempts to explain
the structure / design of the configure script and the various
Makefile pieces that live across the sou
