> There are more pngs. There are more binary files. You just gotta find em all (like
> pokemon).
There is one png in the src/ tree (uismall.png) which will break the build if you line ending-ize it, which is what's relevant here.
> Now when you're changing byte 13 to 10, things are gonna get tricky. You wouldn't
> wanna change every file on your computer would you? NO of course not. Just all the
> text files that came from windows.
Everything under src/ except uismall.png needs to have the endings changed. The compile problem people reported is specifically because Python doesn't handle foreign line endings gracefully like gcc and recent versions of patch can.
> The real question is why is the MAME dev (i think his name is italian or french)
> puttin out zip files that are all CRLF? Is he a windows fanboy? Maybe. probably. I
> think he's the real enemy in all this.
Windows is the lead platform. That isn't going to change, even though several of the developers are working on OS X and Linux nowadays. Linux users are expected to pull the nice binary packages that all of my excellent partners create (they're usually promptly available for Fedora/RH/CentOS, Ubuntu/Debian, Slackware, and Arch, at least) or use SVN which nicely avoids any line ending problems.
Seriously, integer releases are completely meaningless the way development operates now (there were major scary changes going into 0.149 less than 8 hours before release), so don't be afraid of SVN.
|
Index 
Flat 
Re: MAME 0.149
Reply
Re: MAME 0.149
