On Thu, Mar 7, 2019 at 10:30 AM Matthias Apitz wrote:
>
> Re/ crosscompiling: I'm used to do so on FreeBSD amd64 for x86 target,
> but never compiled something on FreeBSD/Linux for Windows.
use the mingw-w64 toolchain (sould be available in your freebsd distribution)
i686-w64-mingw32-gcc,
El día Thursday, March 07, 2019 a las 09:36:28AM +0100, Vincent Torri escribió:
> > Below is the (very short) list of missing pieces which I can't see on my
> > Windows file system.
> >
> > Any ideas?
> > - -
> >
Personally I use
PATH="/usr/x86_64-w64-mingw32/sys-root/mingw/bin:$PATH" ldd DEADBEEF.exe
which is not exactly what you would like but still better than simply
launching ldd.
чт, 7 мар. 2019 г. в 11:27, Matthias Apitz :
> El día Wednesday, March 06, 2019 a las 11:20:05AM -0800, David Grayson
>
On 07.03.2019 11:26, Matthias Apitz wrote:
> El día Wednesday, March 06, 2019 a las 11:20:05AM -0800, David Grayson
> escribió:
>
>> Your experience matches mine: the Cygwin ldd utility does not work properly
>> with MinGW DLLs and prints a bunch of question marks. There is an ntldd
>> utility
On Thu, Mar 7, 2019 at 9:27 AM Matthias Apitz wrote:
>
> El día Wednesday, March 06, 2019 a las 11:20:05AM -0800, David Grayson
> escribió:
>
> > Your experience matches mine: the Cygwin ldd utility does not work properly
> > with MinGW DLLs and prints a bunch of question marks. There is an
El día Wednesday, March 06, 2019 a las 11:20:05AM -0800, David Grayson escribió:
> Your experience matches mine: the Cygwin ldd utility does not work properly
> with MinGW DLLs and prints a bunch of question marks. There is an ntldd
> utility you can use instead. If it's not on your path
Your experience matches mine: the Cygwin ldd utility does not work properly
with MinGW DLLs and prints a bunch of question marks. There is an ntldd
utility you can use instead. If it's not on your path already, I'm not
sure the best way to obtain it. I just use MSYS2, because it's basically a
Hello,
We have some bigger Java applications running as fat clients on
Windows PC. These clients are using some Windows services, for example for
printing, through some DLL written in C++ many years ago and then only
compiled as 32-bit DLL. Moving forward to OpenJDK 1.8 with a 64-bit JRE
we now
