Stiletto![Administrator Administrator](//www.mameworld.info/ubbthreads/images/adm.gif) |
They're always after me Lucky ROMS!
|
|
|
Reged: 03/07/04
|
Posts: 6472
|
|
|
Send PM
|
|
|
Changes for Future Releases
#372125 - 12/21/17 03:31 PM
|
|
|
http://mamedev.org/?p=451
Quote:
We’ll be making a few changes to the Windows binaries from MAME 0.193 onwards. This will only affect pre-built Windows binaries distributed from mamedev.org and github.com – packaged source won’t be affected, and default build settings won’t change. If everything goes to plan, the following changes will be made:
- Both 32-bit and 64-bit binaries will be built with GCC 7.2 (changed from GCC 6.3). This change shouldn’t be noticeable for most users.
- 32-bit binaries will require SSE2. Minimum CPU required will be Intel Pentium 4, AMD Opteron, AMD Athlon 64, or equivalent.
A number of Linux distributions have already switched to GCC 7, and a significant number of MAME developers and users build MAME with GCC 7 on Windows. We don’t anticipate any major issues as a result. The minimum supported GCC version is still GCC 5.1 and is unlikely to change for some time yet.
Requiring SSE 2 improves performance and makes behaviour of 32-bit and 64-bit builds more consistent. Note that this only affects our packaged binary releases – by default, 32-bit x86 builds won’t require SSE. You’ll just have to compile MAME yourself if the SSE 2 requirement is a problem for your use case. However, recent MAME versions are unlikely to perform well on x86 CPUs that predate SSE 2 support.
In other news, the latest version of the Visual Studio 2017 C++ compiler is capable of building MAME. Visual Studio 2015 will be the primary supported version of Visual Studio for a few more releases, but if you were holding off updating to Visual Studio 2017 because of problems compiling variable templates and constexpr, you’ll be pleased to know that Microsoft has resolved these issues.
|
|
|
Stiletto![Administrator Administrator](//www.mameworld.info/ubbthreads/images/adm.gif) |
They're always after me Lucky ROMS!
|
|
|
Reged: 03/07/04
|
Posts: 6472
|
|
|
Send PM
|
|
|
Re: Changes for Future Releases
[Re: Stiletto]
#372126 - 12/21/17 03:38 PM
|
|
|
> http://mamedev.org/?p=451 > > > We’ll be making a few changes to the Windows binaries from MAME 0.193 onwards. This > will only affect pre-built Windows binaries distributed from mamedev.org and > github.com – packaged source won’t be affected, and default build settings won’t > change. If everything goes to plan, the following changes will be made: > > > Both 32-bit and 64-bit binaries will be built with GCC 7.2 (changed from GCC 6.3). > This change shouldn’t be noticeable for most users. > 32-bit binaries will require SSE2. Minimum CPU required will be Intel Pentium 4, AMD > Opteron, AMD Athlon 64, or equivalent. > > > A number of Linux distributions have already switched to GCC 7, and a significant > number of MAME developers and users build MAME with GCC 7 on Windows. We don’t > anticipate any major issues as a result. The minimum supported GCC version is still > GCC 5.1 and is unlikely to change for some time yet. > > Requiring SSE 2 improves performance and makes behaviour of 32-bit and 64-bit builds > more consistent. Note that this only affects our packaged binary releases – by > default, 32-bit x86 builds won’t require SSE. You’ll just have to compile MAME > yourself if the SSE 2 requirement is a problem for your use case. However, recent > MAME versions are unlikely to perform well on x86 CPUs that predate SSE 2 support. > > In other news, the latest version of the Visual Studio 2017 C++ compiler is capable > of building MAME. Visual Studio 2015 will be the primary supported version of Visual > Studio for a few more releases, but if you were holding off updating to Visual Studio > 2017 because of problems compiling variable templates and constexpr, you’ll be > pleased to know that Microsoft has resolved these issues.
Yes, I'm a week late with reblogging this. I blame the holiday craziness. Fortunately, it's not terribly important news.
- Stiletto
|
|
|
|
Re: Changes for Future Releases
[Re: Stiletto]
#372141 - 12/21/17 08:40 PM
|
|
|
I still get GCC 6.3.0 detected and MINGW32 is not set. Any advise ?
|
|
|
smf |
I've been here before
|
|
|
Reged: 01/16/15
|
Posts: 130
|
|
|
Send PM
|
|
|
Re: Changes for Future Releases
[Re: haynor666]
#372176 - 12/22/17 08:40 AM
|
|
|
> I still get GCC 6.3.0 detected and MINGW32 is not set. Any advise ?
Follow the advice in updating build tools
http://mamedev.org/tools/
As for your "MINGW32 is not set" error, it sounds like you have a conflict between CONFIG_ARCHITECTURE and PTR64. If you don't specify them at all then they should default the correct way.
A simple way to check would be open a standard windows command prompt and run these commands
set PTR64= set CONFIG_ARCHITECTURE= \msys64\win32\env.bat cd WHEREVERYOURSOURCEISDOWNLOADED make clean make REGENIE=1
if that does the same thing then for x86 builds you want set PTR64=0 and for x64 builds you want set PTR64=1, while set CONFIG_ARCHITECTURE=x86 or set CONFIG_ARCHITECTURE=x64
If you change CONFIG_ARCHITECTURE then you need to run \msys64\win32\env.bat again, if you change PTR64 then you ought to run make REGENIE=1 again.
|
|
|
|
Re: Changes for Future Releases
[Re: smf]
#372193 - 12/22/17 09:16 PM
|
|
|
I don't think there is anything to update because I've downloaded latest tools yesterday from mamedev site. Even running command You mentioned pacman clearly says there is nothing to update.
I did as mentioned
Quote:
If you have 64-bit Windows but wish to build for both 32-bit and 64-bit. To switch between different mingw versions use config32.bat and config64.bat)
But this didn't help either. I'll try standalone mingw64 package.
http://www.mameworld.info/ubbthreads/sho...true#Post364709
|
|
|
|
Re: Changes for Future Releases
[Re: Stiletto]
#372201 - 12/23/17 12:19 AM
|
|
|
|
|
Re: Changes for Future Releases
[Re: haynor666]
#372383 - 12/27/17 12:30 PM
|
|
|
I've downloaded latest tools just released but still I have the same error about MINGW32. Any other advise ?
According to instructions only config64.bat is required to switch between 32 and 64 bit. Tools are in C:\msys64
|
|
|
Dullaron |
Mitchell or Dunard Garaus
|
|
|
Reged: 07/22/05
|
Posts: 6134
|
Loc: Fort Worth, Tx
|
|
Send PM
|
|
|
Someone falling a sleep? Wrong places. :)
[Re: Stiletto]
#372384 - 12/27/17 12:52 PM
|
|
|
Windows 64-bit (x64) - msys32-2017-12-26.exe Windows 32-bit (x86) - msys64-2017-12-26.exe
should be like this.
Windows 32-bit (x86) - msys32-2017-12-26.exe Windows 64-bit (x64) - msys64-2017-12-26.exe
|
W11 Home 64-bit + Nobara OS / AMD Radeon RX 5700 XT / AMD Ryzen 7 3700X 8-Core 3.59 GHz / RAM 64 GB
|
|
|
Re: Someone falling a sleep? Wrong places. :)
[Re: Dullaron]
#372385 - 12/27/17 01:35 PM
|
|
|
I've downloaded dual tools (x32 x64). Compiling works correctly only from win32env.bat but not from mingw64.exe
|
|
|
|
Re: Someone falling a sleep? Wrong places. :)
[Re: haynor666]
#372386 - 12/27/17 01:38 PM
|
|
|
> I've downloaded dual tools (x32 x64). Compiling works correctly only from > win32env.bat but not from mingw64.exe
Sounds about right. I do this every time I start devving for the day:
![](https://i.imgur.com/1UUtYIA.png)
Eventually it almost becomes muscle-memory.
|
|
|
Stiletto![Administrator Administrator](//www.mameworld.info/ubbthreads/images/adm.gif) |
They're always after me Lucky ROMS!
|
|
|
Reged: 03/07/04
|
Posts: 6472
|
|
|
Send PM
|
|
|
Re: Someone falling a sleep? Wrong places. :)
[Re: Dullaron]
#372403 - 12/27/17 08:02 PM
|
|
|
> Windows 64-bit (x64) - msys32-2017-12-26.exe > Windows 32-bit (x86) - msys64-2017-12-26.exe > > should be like this. > > Windows 32-bit (x86) - msys32-2017-12-26.exe > Windows 64-bit (x64) - msys64-2017-12-26.exe
Fixed. And yes, I was! Micko made the packages, but I updated the HTML, and wrongly.
- Stiletto
|
|
|
Dullaron |
Mitchell or Dunard Garaus
|
|
|
Reged: 07/22/05
|
Posts: 6134
|
Loc: Fort Worth, Tx
|
|
Send PM
|
|
|
Re: Someone falling a sleep? Wrong places. :)
[Re: Stiletto]
#372420 - 12/28/17 02:10 AM
|
|
|
> > Windows 64-bit (x64) - msys32-2017-12-26.exe > > Windows 32-bit (x86) - msys64-2017-12-26.exe > > > > should be like this. > > > > Windows 32-bit (x86) - msys32-2017-12-26.exe > > Windows 64-bit (x64) - msys64-2017-12-26.exe > > Fixed. And yes, I was! Micko made the packages, but I updated the HTML, and wrongly. > > - Stiletto
No problem.
|
W11 Home 64-bit + Nobara OS / AMD Radeon RX 5700 XT / AMD Ryzen 7 3700X 8-Core 3.59 GHz / RAM 64 GB
|
|