This is a rudimentary start to having unit tests for keyman32.
At present, it will build only in win32/debug and requires you
to manually run make -DDEBUG beforehand. The tests currently
run in Visual Studio and are not integrated.
* Move old notes into an old/ folder to clarify their pending removal
and add a note to the top of each file.
* Cleanup macos.sh script to fix various issues.
For auto-generating help files we need `buildtools`, so we can't
exclude it from source package. Also, we now include our version
of `help2man`, so we no longer need it as a build dependency,
but instead directly depend on `perl`.
During a package build we don't have access to `scripts/reconf.sh`.
However, we don't really need it since we already ran it before.
This change adds a `--no-reconf` flag that allows skipping
`reconf.sh`.
Fixes#5316.
Keyman for macOS did not recognise the updated version number 0x0E00,
which is version 14.0. There are no changes to the file format which
impact Keyman for macOS -- the only change is support for notany and
context for Keyman Engine for Web.
Relates to #5316.
Keyman for mac is still reading from kmp.inf, but was treating it as
UTF-8. However, it is windows-1252 encoding. This was stopping Keyman
from loading the file due to the presence of a (C) symbol.
Keyman for mac *should* be loading kmp.json. This needs to be addressed
as a separate issues.
help2man is an improved version of the tool available on Linux. It
has a few bugs fixed.
help2md is based on help2man and converts the python --help and
--version output to a markdown help page.
As the build environment documentation is duplicated across each of the
Keyman platform projects, it has become somewhat convoluted and
inconsistent. This PR moves all the mac-based and shared documentation
into docs/build, with placeholders for Windows and Linux documentation
to be moved in the next PR.
The idea is that a developer can configure their box to build any of the
available projects for that platform (web and android build on all three
main dev platforms).
Keeping the build documentation in one place makes it much simpler to
keep it consistent and up-to-date as well, as well as keeping us aware
of potential dependency conflicts between projects.
The icing on the cake is the resources/devbox/macos/macos.sh script,
which I have tested and takes a bare metal mac box through to a full
Keyman development environment (except XCode, there's always something!)
The changelogs should match what got uploaded (and accepted) to
Debian so that the changelog reflects the upload history to Debian.
(cherry picked from commit f91b52d3ea)
