|
Tutorial page for msys64?
#348713 - 01/02/16 12:48 AM
|
|
|
Is there a howto page on how to use the new msys build tools yet? The installer runs, but I have no idea how to use the command shell, or where to put the sources.
On another front, I can't get the old buildtools to install, they say that the "master" branch already exists and gives me a fatal error when run. I don't think these are being used any more. Is that right?
I am thoroughly confused, and any help will be appreciated. Thanks.
|
|
|
|
Re: Tutorial page for msys64?
[Re: Zaghadka]
#348715 - 01/02/16 01:18 AM
|
|
|
Okay. I figured it out. It's a bash shell, not a Windows Command shell. I have more questions though.
I stuck my source in my Home folder. I guess that's the best place for it.
The command:
Code:
make -j5 TOOLS=1
Doesn't seem to use all cores though. Just two. I had to use:
Code:
make --jobs=5 TOOLS=1
To get it to use all cores. Did I make a syntax error with the first line?
Also, how do we update the tools? "update" doesn't work any longer.
Thanks for your patience.
Zag
|
|
|
B2K24 |
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
Reged: 10/25/10
|
Posts: 2663
|
|
|
Send PM
|
|
|
Re: Tutorial page for msys64?
[Re: Zaghadka]
#348718 - 01/02/16 01:47 AM
|
|
|
> Is there a howto page on how to use the new msys build tools yet? The installer runs, > but I have no idea how to use the command shell, or where to put the sources. > > On another front, I can't get the old buildtools to install, they say that the > "master" branch already exists and gives me a fatal error when run. I don't think > these are being used any more. Is that right? > > I am thoroughly confused, and any help will be appreciated. Thanks.
A dev instructed me on IRC and I have it compiling right now.
If your msys64 is placed in default location *C:\msys64*
Then put the MAME source in location */home/[usr] (c:\msys64\home\[username])*
On my system it's *C:\msys64\home\Administrator*
Then you can open conemu.bat and paste there what you usually compile with.
|
|
|
Dullaron |
Diablo III - Dunard #1884
|
|
|
Reged: 07/22/05
|
Posts: 6125
|
Loc: Fort Worth, Tx
|
|
Send PM
|
|
|
Re: Tutorial page for msys64?
[Re: B2K24]
#348767 - 01/03/16 08:03 AM
|
|
|
> > Is there a howto page on how to use the new msys build tools yet? The installer > runs, > > but I have no idea how to use the command shell, or where to put the sources. > > > > On another front, I can't get the old buildtools to install, they say that the > > "master" branch already exists and gives me a fatal error when run. I don't think > > these are being used any more. Is that right? > > > > I am thoroughly confused, and any help will be appreciated. Thanks. > > A dev instructed me on IRC and I have it compiling right now. > > If your msys64 is placed in default location *C:\msys64* > > Then put the MAME source in location */home/[usr] (c:\msys64\home\[username])* > > On my system it's *C:\msys64\home\Administrator* > > Then you can open conemu.bat and paste there what you usually compile with.
Have my set up like this.
@echo off SET CONFIG_ARCHITECTURE=x64 call C:\msys64\win32\env.bat cd C:\source make -j6 TOOLS=1 SYMBOLS=0 pause
msys64 is way smaller than buildtools. Gonna trash the buildtools right away.
|
W11 Home 64-bit + Nobara OS / AMD Radeon RX 5700 XT / AMD Ryzen 7 3700X 8-Core 3.59 GHz / RAM 64 GB
|
|
|
Re: Tutorial page for msys64?
[Re: Dullaron]
#348784 - 01/04/16 12:38 AM
|
|
|
I managed to get an executable from the new msys64-2016-01-04 build tools, but I get a dependency error when I try to run mame64.exe:
"The program can't start because libwinpthread-1.dll is missing from your computer. Try reinstalling the program to fix this problem."
Mame used to be self-contained. Do we have a bug, or am I just using the new tools too soon?
I have found the file in msys64 and putting libwinpthread-1.dll in the Mame directory causes mame64 to run with this error:
"The application was unable to start correctly (0xc000007b). Click OK to close the application."
Yikes.
|
|
|
|
Re: Tutorial page for msys64?
[Re: Zaghadka]
#350284 - 02/15/16 01:51 AM
|
|
|
|