Actually, while doing the same thing, but with the 1.52 release, it worked!

Unfortunately, I cannot swear I didn't change anything in MSVS setup, but I 
don't think I did... maybe inadvertedly somehow...

________________________________________
From: Oleg Sivokon
Sent: Wednesday, June 20, 2018 2:38:16 PM
To: Gregg Smith; dev@apr.apache.org
Subject: Re: Linking with libapr-1.lib on MS Windows using MSVC 19

> No not really, but this gives me problems trying to build x86 on a x64
> computer so I just remove it from makefile.win.

> Just to make sure this is not an oversight: I'm on a x64 and am trying to 
> build x64, no 32-bit is desired.
>
> !IF [$(COMSPEC) /c cl /nologo /? \
>         | $(SystemRoot)\System32\find.exe "x64" >NUL ] == 0
> ARCH=x64 Release
> !ELSE
> ARCH=Win32 Release
> !ENDIF

Removing these lines made no difference


> Are you using the VS20xx x64 Native Tools Command Prompt?

Yes, I tried MSVS 2017 and MSVS 2015, should I try even earlier versions?

> If all else fails I believe you can bypass makefile.win
>
> nmake /f libapr.mak cfg="libapr - x64 Release"

This gives the exact same error (although, this time the executable that 
produces it isn't the rc.exe, but link.exe)

More information that might help / shed some light:

I was trying to convert worspace files into solutions, but it failed completely 
for all projects.  Unfortunately, MSVS doesn't produce any intelligible 
reports, just "failed".

I also tried to run nmake on apr-util Makefile, but it complains about syntax 
error in line 91, which reads:

!IF "$(XML_PARSER)" == "libexpat"

Is this symptomatic of anything?

But, in all honesty, I would really, really, want to avoid touching MSVS at 
all.  Personal preferences aside, I want this project to run in automated 
testing environment, and the very thought of having to deal with MSVS invokes a 
lot of painful memories...

Best.

Oleg


This communication and all information contained in or attached to it is 
confidential, intended solely for the addressee, may be legally privileged and 
is the intellectual property of one of the companies of NEX Group plc ("NEX") 
or third parties. If you are not the intended addressee or receive this message 
in error, please immediately delete all copies of it and notify the sender. We 
have taken precautions to minimise the risk of transmitting software viruses, 
but we advise you to carry out your own virus checks on any attachments. We do 
not accept liability for any loss or damage caused by software viruses. NEX 
reserves the right to monitor all communications. We do not accept any legal 
responsibility for the content of communications, and no communication shall be 
considered legally binding. Furthermore, if the content of this communication 
is personal or unconnected with our business, we accept no liability or 
responsibility for it. NEX Group plc is a public limited company registered in 
England and Wales under number 10013770 and certain of its affiliates are 
authorised and regulated by regulatory authorities. For further regulatory 
information please see www.NEX.com.

Reply via email to