| Re: [hatari-devel] Hatari Windows 2.4.1 release and PortMidi? |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
Le 24/08/2022 à 15:15, Thorsten Otto a écrit :
While we are at it, would you mind if i make a hatari binary for windows
available with portmidi support, or do you plan to do that yourself?
Hi
no problem, you can do so and post link to your binary in case people
want to try the portmidi part (maybe we will need some fixes for it too,
as we never really tested it under windows) (we already have daily
builts at http://antarctica.no/~hatari/latest/)
I think i have all the dependencies now available locally, though there are
some subtle differences:
- since i didn't have capsimage available yet, i compiled that from source.
That worked, until some plain C file (floppy_ipf.c in this case) tried to
include the header file. Reason is that the macro "ExtSub" from ComLib.h
expands to "extern "C"" in the official sources, which of course does not work
when not using cplusplus code. Are you using some fixed version of capsimage
to build the binaries?
At one point (several years ago), I helped SPS guys to do some linux
changes for v5 of the lib, but not everything was included in the end
and the sources need to be manually fixed at some place because they
sometimes conflict with system's includes or with mingw's includes.
So, it seems "normal" to me if you had to adapt the source to make it
compile.
- Your archive does not contain libstdc++6.dll, and apparently it is not
needed. In the version i compiled it is however referenced. Do you explicitcly
link to the static version of that lib, or how is it that it is not referenced
in your binary?
no static linking, I'm using mingw64-gcc-12.1.1-1.mga9 and
mingw32-gcc-12.1.1-1.mga9 as my main compiler, depending on whether I
want to build the 64 bit or 32 bit version.
Maybe the mingw-gcc you're using was built with different parameters, I
can't tell.
Nicolas