Currently, if both Visual Studio and the Windows SDK are installed on a
system, configure will favor the sdk as the source for a build
environment. This works equally well for OpenJDK, but not for OracleJDK.
Using the Windows SDK also isn't the officially supported way of
building. This patch c
Hi.
I'm successfully building two configurations on windows (lambda/lambda)
make CONF=windows-x86-normal-server-release images
make CONF=windows-x86_64-normal-server-release images
But when I try to build them both:
$ make CONF= images
Building target 'images' in the following configurations (m
Hi.
I'm sucessfuly building two configurations on windows (lambda/lambda)
make CONF=windows-x86-normal-server-release images
make CONF=windows-x86_64-normal-server-release images
But when I try to build them both:
$ make CONF= images
Building target 'images' in the following configurations (mat
For the JCE builds, I'm hoping to have a look at this soon along with
some other back-burnered tasks. Unfortunately, some unexpected family
matters cut into my availability the last three weeks.
Brad
On 6/4/2013 6:22 AM, Erik Joelsson wrote:
On 2013-06-04 14:13, Alan Bateman wrote:
On 04
Erik:
Currently, if both Visual Studio and the Windows SDK are installed on
a system, configure will favor the sdk as the source for a build
environment. This works equally well for OpenJDK, but not for
OracleJDK. Using the Windows SDK also isn't the officially supported
way of building. This
Erik:
Looks good to me.
Tim
On 2013-06-07 04:08, David Holmes wrote:
On 4/06/2013 10:38 PM, David Holmes wrote:
On 4/06/2013 9:21 PM, Erik Joelsson wrote:
On 2013-06-04 06:56, David Holmes wrote:
I think we should add a (configure time?) check to watch for the
illegal: BUILD_CRYPTO=no,
