summary |
shortlog | log |
commit |
commitdiff |
tree
first ⋅ prev ⋅ next
Mark Wooding [Wed, 19 Dec 2018 12:39:59 +0000 (12:39 +0000)]
Makefile, bin/ -> src/: Substitute scripts rather than chasing symlinks.
Move the original scripts to `src/' and leave placeholders, and have the
Makefile do seddery on them to create the `bin/' versions.
Mark Wooding [Wed, 19 Dec 2018 12:37:39 +0000 (12:37 +0000)]
Makefile: Use `SED' as the build-step label when hacking setup scripts.
Also, introduce a line break to match future additions.
Mark Wooding [Sat, 22 Dec 2018 09:22:46 +0000 (09:22 +0000)]
Makefile: Ensure that output directory exists before generating output.
Mark Wooding [Sat, 22 Dec 2018 09:29:58 +0000 (09:29 +0000)]
Makefile: Add silent-rules machinery for completely silent actions.
Mark Wooding [Thu, 13 Dec 2018 19:50:25 +0000 (19:50 +0000)]
linux-*-setup.sh.in: Add the cross tree's `bin' directory to `PATH'.
Mark Wooding [Thu, 13 Dec 2018 19:50:09 +0000 (19:50 +0000)]
android-cross-setup.sh.in: Explicitly export the `PATH'.
Mark Wooding [Wed, 12 Dec 2018 17:41:03 +0000 (17:41 +0000)]
*-cross-setup.sh.in: Set `PKG_CONFIG_PATH' correctly.
This got screwed by the recent refactoring. Oops.
Mark Wooding [Mon, 26 Nov 2018 13:16:49 +0000 (13:16 +0000)]
Bring `native' architectures into the collection.
Also fix Android `cross-gcc'. And other stuff.
Mark Wooding [Sat, 24 Nov 2018 17:58:14 +0000 (17:58 +0000)]
Rearrange everything.
* Have `setup.sh' define `CROSS_ARCH', which is the GNU triplet for
the target architecture. This is then exported and can be used by
`config.site' to define further things.
* Factor out the common machinery between Android and Linux
`config.site' files. This is, in fact, exactly the Linux
`config.site', so have `mdw-cross' select this as a default if
nothing more specific can be found.
* Factor out the common machinery for Android `config.site' files,
which was basically all of it.
* Move the compiler flags into the new `android-cross-config.site'
file.
* Replace `$ANDROID_CC' by `$CROSS_ARCH-gcc'. Factor out the
mandatory compiler flags into `$CROSS_gcc_FLAGS', and generalize this
so that we also set `$CROSS_gxx_FLAGS' for C++.
* Introduce a new program `crosstool' intended to be invoked via a
symlink, which just execs the appropriate cross-toolchain tool with
any necessary extra flags. Include a bunch of useful symlinks and
have `mdw-cross' hook them onto the path.
* Add a Makefile to build the `...-setup.sh' files for each target
architecture from skeletons. The Makefile is unnecessarily hairy
but I like them that way.
Mark Wooding [Thu, 22 Nov 2018 16:10:25 +0000 (16:10 +0000)]
Initial version.