Re: Linking with libapr-1.lib on MS Windows using MSVC 19

2018-06-19 Thread Oleg Sivokon
As I continue to struggle with this issue, I realized that nmake -f Makefile.win would compile a 32-bit library, but, I I need the 64-bit version, so I tried this: nmake -f Makefile.win ARCH="x64 Release" And after installing a lot of MS garbage SDKs and code editors, when I think I finally

Re: Linking with libapr-1.lib on MS Windows using MSVC 19

2018-06-19 Thread Gregg Smith
No not really, but this gives me problems trying to build x86 on a x64 computer so I just remove it from makefile.win. !IF [$(COMSPEC) /c cl /nologo /? \ | $(SystemRoot)\System32\find.exe "x64" >NUL ] == 0 ARCH=x64 Release !ELSE ARCH=Win32 Release !ENDIF Are you using the VS20xx x64

Re: Linking with libapr-1.lib on MS Windows using MSVC 19

2018-06-19 Thread William A Rowe Jr
On Tue, Jun 19, 2018 at 9:17 AM, Oleg Sivokon wrote: > Hello list! > > Later, in Release directory I discovered libapr-1.lib which, as far as I > understand is analogous to an *.a file (archive), and is used by MSVC to > look up symbol definitions. > Note, it looks them up, but the code exists

Linking with libapr-1.lib on MS Windows using MSVC 19

2018-06-19 Thread Oleg Sivokon
Hello list! I'm trying to compile my Python extension which uses APR library. I could do this on Linux, but on MS Windows... well, I really know very little about MS tool-chain and how things work, so would appreciate some help. I followed the instructions in the README in the project and

Re: svn commit: r1833786 - /apr/apr/branches/1.6.x/STATUS

2018-06-19 Thread Yann Ylavic
Hi Jean-Frédéric, On Tue, Jun 19, 2018 at 10:01 AM, wrote: > Author: jfclere > Date: Tue Jun 19 08:01:45 2018 > New Revision: 1833786 > > URL: http://svn.apache.org/viewvc?rev=1833786=rev > Log: > proposal for review. Usually APR backports are CTR (Commit Then Review), but it does not prevent