: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
> 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 /? \
> |
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
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
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
