We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When trying to build the documentation via
mkdocs build
or
mkdocs serve
I observed the error
OSError: no library called "cairo-2" was found no library called "cairo" was found no library called "libcairo-2" was found
Setup:
The error is due to the corresponding lib files not linked to locations, where mkdocs is looking for it, when cairo is installed via brew.
cairo
Also observed here:
The described workaround is setting the fallback environment variable:
export DYLD_FALLBACK_LIBRARY_PATH=$DYLD_FALLBACK_LIBRARY_PATH:/opt/homebrew/lib
I suggest to mention this in our CONTRIBUTING.md.
CONTRIBUTING.md
The text was updated successfully, but these errors were encountered:
@mdbenito @AnesBenmerzoug did you have to install the non-python dependencies manually? So something like:
apt-get install libcairo2-dev libfreetype6-dev libffi-dev libjpeg-dev libpng-dev libz-dev
Sorry, something went wrong.
I am not 100% sure, but I would say yes.
schroedk
Successfully merging a pull request may close this issue.
When trying to build the documentation via
mkdocs build
or
mkdocs serve
I observed the error
OSError: no library called "cairo-2" was found no library called "cairo" was found no library called "libcairo-2" was found
Setup:
The error is due to the corresponding lib files not linked to locations, where mkdocs is looking for it, when
cairo
is installed viabrew.
Also observed here:
The described workaround is setting the fallback environment variable:
export DYLD_FALLBACK_LIBRARY_PATH=$DYLD_FALLBACK_LIBRARY_PATH:/opt/homebrew/lib
I suggest to mention this in our
CONTRIBUTING.md
.The text was updated successfully, but these errors were encountered: