-
Notifications
You must be signed in to change notification settings - Fork 98
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
Search for MS FontValidator.exe in the system path #1336
Comments
...load it from the system path, instead of the hardcoded prebuilt/fval directory on the FontBakery source tree. (issue fonttools#1336)
OK. I tried to setup this on my system by adding the prebuilt/fval directory to the system path:
...but got this error:
|
...but that's not a PATH issue. I must be missing some extra mono-runtime package (I reinstalled my distro last week. Great opportunity for documenting the dependencies :-D) |
Probably this will do:
But I dislike installing everything! There must be a cleaner way of installing only what is needed in our case. |
I had a hunch that maybe this would be a cleaner solution for satisfying this dependency:
But it didn't. I'll resort to installing mono-complete for now. If someone has a hint of a smaller install footprint I'll be glad to update the docs. |
hey! I just figured it out! This is a good one:
Installed and running! Yay! |
Sweet :)
|
We have a binary of MS FontVal available at the prebuilt/fval directory in our repository (I built it from sources a while ago because I could not find any other way of installing it on my system and on the kubernetes cluster).
The code invokes it with the explicit path of the prebuilt/fval directory (thus assuming incorrectly that the code will always be running from the root of the git tree). The recent split of repos with the dashboard going to its own repo, made it clear that it is wiser to make FontBakery look for third-party tools in the system path. Anything else should be done as an installation procedure.
The goal of this issue is to make this change to the check.py code as well as to add documentation on README.md instructing the users (and @graphicore :-D) on how to setup MS FontValidator on their systems (and on the FontBakery-Dashboard kubernetes cluster).
The text was updated successfully, but these errors were encountered: