2024-12-14, 02:37 PM
(This post was last modified: 2024-12-14, 02:39 PM by raulo1985. Edited 3 times in total.)
(2024-12-13, 06:51 AM)qwerty12 Wrote: I've never built JMP from source, so take what you will from this.
(2024-12-13, 12:01 AM)raulo1985 Wrote: [...](on x64_x86 Cross Tools of VS 2022)[...]
Quote:lib /def:mpv\mpv.def /out:mpv\mpv.dll.lib /MACHINE:X64
LNK4272 warnings: library machine type 'x64' conflicts with target machine type 'X86'.
Well, which is it: are you trying to cross-compile a 32-bit build of JMP on a 64-bit machine, or do you actually want a 64-bit build of JMP? If it's the former, I'd start by changing/MACHINE:X64
and if it's the latter, you should be running "x64 Native Tools Command Prompt for VS 2022" instead.
Quote:PS: on a side note, I can only get to that point with older versions of libmpv1, because newer ones don't include a mpv.def file, which is required apparently. How can I try with a newer libmpv1 version without the mpv.def file? Or you can just use one that came with an older version?
Look at the workflow file for JMP. You'll notice it runsgendef
as part of the build process to produce a def file from a given libmpv.dll. If you want a copy of that program, you can take an executable from here: https://packages.msys2.org/packages/ming...-tools-git
Thanks for your reply, greatly appreciate it. I'm trying to create a x64 build, I used Cross tools because that's what the instructions said. When I use x64 Native Tools Command Prompt for VS 2022 I get many "PlayerComponent.cpp.obj : error LNK2019: unresolved external symbol" messages (related to mpv) and it ends with a fatal error. So I'm still stuck.