From: Richard Levitte <levitte@openssl.org>
Date: Fri, 15 Jul 2016 10:57:27 +0000 (+0200)
Subject: Windows: allow input and output flags to end with a space, or not
X-Git-Tag: OpenSSL_1_1_0-pre6~227
X-Git-Url: https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff_plain;h=1fc431ba57d12189a9bdacd3999ea2a7b91458d8;hp=1fc431ba57d12189a9bdacd3999ea2a7b91458d8

Windows: allow input and output flags to end with a space, or not

With a number of tools, especially those coming with Visual Studio,
some command options are separated from their argument with a space,
others with a space.  Since we parametrise them, we can't know
beforehand which it will be, so we must allow the input and output
options to have either.

However, spaces at the end of nmake macro values are trimmed, so allow
spaces to exist by adding a reference to an undefined macro at the end.

Reviewed-by: Andy Polyakov <appro@openssl.org>
---