Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow cross compiling #17

Open
wants to merge 8 commits into
base: master
Choose a base branch
from
Open

Allow cross compiling #17

wants to merge 8 commits into from

Commits on Dec 29, 2020

  1. build: simplify linking 

    The Makefile already calls gcc to link together mame, so use $(CC)
instead of $(LD) for the final link step.
    @devnull42
    devnull42 committed Dec 29, 2020
    Configuration menu
    Copy the full SHA
    50530c0 View commit details
    Browse the repository at this point in the history

  2. build: move strip into its own step 

    Within the Makefile, mame is first linked together and then stripped. If
the strip step fails, the end result is an unstripped mame binary.
Running 'make' again will not try to re-strip it because a file named
'mame' now exists.

Modify the final steps of the build process. Place the unstripped binary
into $(OBJ), and the stripped binary into $(PWD) as before.
    @devnull42
    devnull42 committed Dec 29, 2020
    Configuration menu
    Copy the full SHA
    dc8bc9e View commit details
    Browse the repository at this point in the history

  3. build: Support cross-compilation 

    So as to allow mame4all-pi to be built via cross-compilation, honor the
environment variable CROSS_COMPILE as a prefix to build tools. Then to
match autotools standards, rename the variable "CPP" to "CXX". All build
tools' names can now be overridden by the calling environment.
    @devnull42
    devnull42 committed Dec 29, 2020
    Configuration menu
    Copy the full SHA
    6ffa642 View commit details
    Browse the repository at this point in the history

  4. build: use pkg-config for SDL 

    Attempt to detect if pkg-config is installed. If so, then use SDL's pc
file for its CFLAGS and LIBS. Otherwise, default back to the hard-coded
values that were previously within the Makefile.
    @devnull42
    devnull42 committed Dec 29, 2020
    Configuration menu
    Copy the full SHA
    76f095d View commit details
    Browse the repository at this point in the history

  5. build: use pkg-config for VCSM 

    If pkg-config is installed, use VideoCore Shared Memory (VCSM)'s pc file
for its CFLAGS and LIBS. Otherwise, default back to the hard-coded
values that were previously within the Makefile.
    @devnull42
    devnull42 committed Dec 29, 2020
    Configuration menu
    Copy the full SHA
    e60c022 View commit details
    Browse the repository at this point in the history

  6. build: use pkg-config for EGL 

    If pkg-config is installed, use EGL's pc file for its CFLAGS and LIBS.
Otherwise, default back to the hard-coded values that were previously
within the Makefile.
    @devnull42
    devnull42 committed Dec 29, 2020
    Configuration menu
    Copy the full SHA
    07db68d View commit details
    Browse the repository at this point in the history

  7. build: use pkg-config for GLib-2.0 

    If pkg-config is installed, use glib-2.0's pc file for its CFLAGS and
LIBS. Otherwise, default back to the hard-coded values that were
previously within the Makefile.
    @devnull42
    devnull42 committed Dec 29, 2020
    Configuration menu
    Copy the full SHA
    241463a View commit details
    Browse the repository at this point in the history

  8. build: use pkg-config for ALSA 

    If pkg-config is installed, use alsa's pc file for its CFLAGS and LIBS.
Otherwise, default back to the hard-coded values that were previously
within the Makefile.
    @devnull42
    devnull42 committed Dec 29, 2020
    Configuration menu
    Copy the full SHA
    7a8c7b1 View commit details
    Browse the repository at this point in the history