summaryrefslogtreecommitdiff
path: root/pkg/fribidi
AgeCommit message (Collapse)Author
2021-11-17fribidi: Update to 1.0.11Michael Forney
2020-07-07fribidi: Update to 1.0.10Michael Forney
2020-03-02fribidi: Update to 1.0.9Michael Forney
2020-01-29Move toolchain config into config.luaMichael Forney
2020-01-29Add support for building multiple configurationsMichael Forney
Now, you can build in separate directories per configuration: mkdir foo (cd foo && ../setup.lua) samu -C foo
2019-12-16fribidi: Update to 1.0.8Michael Forney
2019-11-17Update ninja requirement to 1.8.0 and don't bother with atomic outputsMichael Forney
Since ninja 1.8.0[0] and samurai 0.2[1], output mtime is always recorded after a job succeeds, and outputs are considered dirty if the recorded mtime is older than any input. This means that even if a command partially writes its output then fails (for example, if run with stdout redirected to a file), it will still get re-run during the next build. This means that outputs no longer have to be written atomically (i.e. renamed into place) in order to ensure a correct build, and we can drop the idiom `command >$out.tmp && mv $out.tmp $out`. [0] https://github.com/ninja-build/ninja/commit/04d886b11041bb59d01df794cce7a1e8cad2250d [1] https://github.com/michaelforney/samurai/commit/799bc5a4719b90a1026c129b55b92c0bccf97eeb
2019-10-03fribidi: Update to 1.0.7Michael Forney
2019-07-07Revert "fribidi: Make function declarations match definitions"Michael Forney
This reverts commit d80bac0f9daa0b16494dfacdc200323da374cad5.
2019-06-15fribidi: Make function declarations match definitionsMichael Forney
2019-03-19Rename rev to ver, and keep track of package versions as wellMichael Forney
2018-08-26fribidi: Update to 1.0.5Michael Forney
2018-03-23fribidi: Update to 1.0.2Michael Forney
2018-02-16fribidi: Build code generation tools with the host toolchainMichael Forney
2018-02-04fribidi: Update to 1.0.1Michael Forney
2017-09-25Rewrite ninja generation scripts in LuaMichael Forney
2016-12-13Move to flat package hierarchyMichael Forney
Note to self: never try to move submodules again To migrate your existing submodules (more or less): set -x set -e mkdir .git/modules/pkg for old in */*/src ; do new="pkg/${old#*/}" if ! [ -f "$old/.git" ] || [ "${old%%/*}" = pkg ] ; then continue fi git -C ".git/modules/$old" config core.worktree "../../../../../$new" rmdir "$new" mv "$old" "$new" sed -e "s,$old,$new," "$new/.git" > "$new/.git.tmp" mv "$new/.git.tmp" "$new/.git" mkdir ".git/modules/${new%/src}" mv ".git/modules/$old" ".git/modules/$new" rm "${old%/src}"/*.ninja mv "${old%/src}"/*.tar.{gz,xz,bz2} "${new%/src}/" rmdir "${old%/src}" || true done sed -e 's,^\[submodule "[^/]*/,[submodule "pkg/,' .git/config > .git/config.tmp mv .git/config.tmp .git/config