MAMEdev
What is the build environment the official windows binary using? #97
Replies: 3 comments 2 replies
-
|
The vl70 screen communication was broken by commit
6643bd0e8b19120725108ac330d62aec9ae8b8fe done on Feb. 9 and will be fixed
soon (thanks for reporting the bug actually, we hadn't noticed). I guess
your compile of 0.262 used a later source by mistake.
You need to checkout the tag mame0262 to get the exact mame 0.262 sources.
Note that it was created on Jan. 31, so clearly did not include the
problematic commit.
…On Sun, Mar 10, 2024 at 4:17 AM qazmko1029 ***@***.***> wrote:
Hi. I'm currently using msys2 env provided on mamedev.org with all
packages updated, mingw-w64 gcc 13.2.0, and using "make -j4 PTR64=1" to
build MAME windows executable. Previously in 0.262 yamaha vl70m emulation
has a good display and it's now broken in 0.263, both not playing sound
correctly anyway. The problem is, my compilation seems always having worse
result than official binary.
0.262 official binary:
2024-03-10_105144.png (view on web)
<https://github.com/mamedev/discussions/assets/26039619/ee6686e6-a357-44c8-88e7-24cc07f363b2>
0.263 official binary and my previous compilation on 0.262 and earlier
version:
2024-03-10_111522.png (view on web)
<https://github.com/mamedev/discussions/assets/26039619/1517a47a-566b-4641-806f-d5a04d9a8f2b>
The latest development tool hosted on the website have gcc 11.2.0, the
official binary looks like built with gcc 10.3.0, so how do I get the
environment and command to build the exact same binary as the website
provided?
—
Reply to this email directly, view it on GitHub
<#97>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACGSF4NMIGFPYIS6H44GVMTYXPGDVAVCNFSM6AAAAABEOTR2ECVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWGM2DQMJWGE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
qazmko1029
-
|
Thanks, I tried mame0262 tag commit and it worked. BTW, is there any instruction on building the same binary provided on mamedev.org? Is it possible for a reproducible build? |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
MSYS2 is essentially a Windows compatibility layer with pacman as package manager Build instructions are at: |
Beta Was this translation helpful? Give feedback.
-
|
I think they're more asking what packages versions official builds currently use. Here’s a list of the MinGW package versions in the current release build environment (obviously not all of these actually end up affecting the built MAME binaries): |
Beta Was this translation helpful? Give feedback.
-
Thanks for the list! The discussion can now be closed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I'm first time here. I'm currently using msys2 env provided on mamedev.org with all packages updated, mingw-w64 gcc 13.2.0, and using "make -j4 PTR64=1" to build MAME windows executable. Previously in 0.262 yamaha vl70m emulation has a good display and it's now broken in 0.263, both not playing sound correctly anyway, I have verified the roms in both versions to be best available. The problem is, my compilation seems always having worse result than official binary.
0.262 official binary:
0.263 official binary and my previous compilation on 0.262 and earlier version:
The latest development tool hosted on the website have gcc 11.2.0, the official binary looks like built with gcc 10.3.0, so how do I get the environment and command to build the exact same binary as the website provided?
Beta Was this translation helpful? Give feedback.
All reactions