| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
just noticed md + code blocks need these
|
|
|
| |
converting file from mediawiki to md format
|
| |
|
| |
|
|
|
|
|
|
|
| |
Produce a warning if MXE_DIR != /usr/lib/mxe
When making a debug build, it is better to get a warning
than set MXE_DIR manually each time.
|
|
|
|
|
|
|
| |
It produced the following erroneous warning:
> Item x86_64-unknown-linux-gnu~mxe-conf
> built item x86_64-unknown-linux-gnu~.gitkeep.
|
| |
|
|
|
|
| |
See https://git.io/vuDJY
|
| |
|
|
|
|
| |
touch all installed/* files after checkout.
|
|
|
|
|
|
|
| |
`git merge -s recursive -X ours` turned out to fail on binary
files. (I can't reproduce this behaviour in test repo, maybe
it is Git's bug.) So I switched to `checkout --ours`, which
worked in that case.
|
|
|
|
| |
gitCheckout() will use gitCommit()
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Result of build by previous commit:
https://gist.github.com/32309209c467853deedc
If a conflict happens, build-pkg should "resolve" it by selecting
one of versions. Git has a merge strategy "recursive" with an
option "ours" which does exactly what is needed but works only
for two heads. That is why multi-merge was replaced by multiple
merges of two heads.
|
|
|
|
|
|
|
| |
This is an implementation of detection of undeclared requiremenets
using Git branches.
See #1111
|
|
|
|
|
|
|
|
|
| |
check-requirements creates directories usr/<target> for all
targets. By default, MXE_TARGETS=i686-w64-mingw32.static, so
it creates a directory for i686-w64-mingw32.static only.
(Currently this doesn't affect history in usr/.git as git ignores
empty directories.)
|
| |
|
| |
|
|
|
|
| |
Warnings fixed: https://gist.github.com/b563dfd7708e1ef209b4
|
|
|
|
|
|
| |
* remove `build-only*` - too low level for general use
* add new patch related commands and catch-all completions
* `mxe-make` alias is more descriptive
|
|
|
|
|
| |
See https://github.com/mxe/mxe/pull/1134#issuecomment-168873410
See https://github.com/mxe/mxe/pull/1134#issuecomment-169867926
|
| |
|
|
|
|
| |
fix #1063
|
|
|
|
|
| |
* use bash for brace expansion
* http://sprunge.us/ is down (fixes #1145)
|
|
|
|
| |
closes #1135
|
|
|
|
| |
Fixes #1074.
|
|\
| |
| | |
build-pkg: add toposort checks and implement it internally, without tsort tool
|
| |
| |
| |
| | |
Instead of invoking tsort tool.
|
| | |
|
| | |
|
|/
|
|
|
| |
Otherwise it provides binary diff for jack/waf file,
which is a mix of Python and tar.
|
|\
| |
| | |
build-pkg: fix .deb installation
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The installation failed with the following note:
> Noting disappearance of mxe-requirements,
> which has been completely replaced.
Add an empty file mxe-requirements.dummy.$release
to prevent this.
|
|\ \
| | |
| | | |
build-pkg: update list of files back from .tar.xz
|
| |/
| |
| |
| | |
fix #1067
|
|\ \
| | |
| | | |
build-pkg: pack Debian packages with xz not gzip
|
| |/
| |
| |
| | |
fix #1068
|
|/ |
|
|\
| |
| | |
patch-tool-mxe: do not replace object id with 000
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously patch-tool-mxe produced the following diffs:
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 0000000..0000000 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
patch tool refused to apply this patch:
The next patch would create the file CMakeLists.txt,
which already exists! Assume -R? [n]
This commit replaces 0000000..0000000 with 1111111..2222222.
|
|\ \
| | |
| | | |
build-pkg: exit with code 1 if a package is broken
|
| |/ |
|
|\ \
| | |
| | | |
build-pkg: do not provide empty dependency list
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Debian packages with "Depends: " do not work:
> Reading package lists... Error!
> E: Problem parsing dependency Depends
> E: Error occurred while processing mxe-source (NewVersion2)
> E: Problem with MergeList /var/lib/apt/lists/pkg.mxe.cc_repos_apt_debian_dists_wheezy_main_binary-amd64_Packages
> E: The package lists or status file could not be parsed or opened.
|
|\ \
| | |
| | | |
build-pkg: build empty dependencies of non-empty
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Otherwise empty dependency produces no .deb file
preventing non-empty package from being installed.
Example: non-empty package gcc depends on empty
package mingw-w64.
|
|/ |
|
| |
|