MAMEWorld Forums - Programming

> > Cool, please stay up to date with github because I've already found two bugs:
>
> I attempted to integrate it and Micko and I made the decision to abort.
>
> 1) The code requires a horrifying soup of compiler options to build -Wall, and it
> gets worse when you include Clang and MSVC++ builds, both of which are routinely done
> by devs and users.

Any compiler options can be moved into a common header file that only the webm codes knows about.

> 2) There's no plain C version of WebM to fulfill NOASM=1 builds.

Incorrect, you can enable the plain C version by setting all of the HAVE_* and ARCH_* defines to 0 in vpx_config.h

> 3) It pulls in Boost, which is larger than all of MAME.

It only needs boost::thread. You can replace this with any threading library (there's probably already one in mame, although I couldn't find it)

> 4) The WebM code isn't much like what Google ships, which set off alarm bells.

It's exactly what google ships, but it's over 2 years old. Replacing with a more recent version would be great for both of us, and shouldn't cause any issues.

> 5) The YASM requirement is a blocker until they ship a packaged installer for OS X.
> MAME is currently easier to compile on OS X than on any other operating system when
> you follow my instructions and install SDL as a framework, and disrupting that is not
> acceptable.

See (2)

>
> Almost none of this is your fault (it's primarily Google's), but we're going to
> pursue alternate methods of logging compressed videos.

This makes it my fault. Let me know if you still can't move forward.

Check out MAMEHub here: http://www.mamehub.info/