-
-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: use new build script and kmc #2393
Conversation
This resolves issues around spaces in paths.
<DisplayFont>'"$displayFont"'</DisplayFont>' | ||
function do_clean() { | ||
rm -f ./source/fv_all.kps | ||
rm -rf ./build/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want to clean these files too?
rm -f build_targets.txt build_targets_temp.txt build_external_targets.txt build_fv_all.txt build_legacy.txt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah nvm - I meant in the top build.sh do_clean
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gotcha
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Fixes #2389.
Replaces the old build script with a cleaner version that utilizes builder.inc.sh, standardizing our build commands.
Uses
kmc
to build all source models, in a single command rather than one-by-one as previously. Handles external models more simply.TODO:
.../release/packages/fv_all/../../../resources/builder.inc.sh: line 1079: KEYMAN_ROOT: unbound variable
(See 3e1368d)Please note: this will merge into staging-17.0, in preparation for 17.0 release. Changes on the staging-17.0 branch will not be published to keyman.com, until they are merged into master when we go to release (or when we determine the updated build tools are sufficiently stable).
Please ignore the failing build in this PR, which is due to data clean required and is addressed in follow-up PRs in the chain (particularly #2404).
Other PRs in this chain: