Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/dkosmari/devkitpro-autoconf

Autoconf macros for using devkitPro in homebrew projects.
https://github.com/dkosmari/devkitpro-autoconf

3ds autoconf automake devkitpro gamecube nds switch wii wii-u wiiu

Last synced: 5 days ago
JSON representation

Autoconf macros for using devkitPro in homebrew projects.

Awesome Lists containing this project

README

        

# Devkitpro Autoconf

This is a collection of Autoconf macros to make it easier to use the devkitPro toolchain.

The macros all use the [all-permissive
license](https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html). They
depend on [Autoconf Archive](https://www.gnu.org/software/autoconf-archive/) macros, which
are usually installed alongside base Autoconf.

## Installation

0. `./bootstrap`

1. `./configure --prefix=/usr`

2. `make`

3. `make install`

Note the `--prefix=` option is needed to ensure the macros are installed in
`/usr/share/aclocal`. Check the output of `aclocal --print-ac-dir` to see it's pointing to
a non-standard directory, and modify the `--prefix=` option accordingly.

## Examples

Some usage examples are provided in the [examples](examples) directory.

Note that they use a [`./bootstrap`](common/bootstrap) script that just creates links to
the `.m4` macros in the [`macros`](macros) directory, to make sure the examples always use
the latest version.

When you use these macros for your own project, your `bootstrap` script should look like
this instead:

```
# Copy all non-standard macros to our local macro repository.
aclocal -I m4 --install
# Now invoke autoreconf to generate the configure script.
exec autoreconf --install "$@"
```

You should also add your `m4` directory to the source control, so any clones will have the
exact same macro versions as you.