-
Notifications
You must be signed in to change notification settings - Fork 88
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
Facing issues in triggering travis build #120
Comments
Hi @odidev, and sorry for the delay. |
Hi @rougier , Thanks for the reply. I have tested in my own repository. It is working after I have updated global python version from 3.5 to 3.7 and disabled deployment phase. I want to add a PR as well for adding arm64 jobs in travis. I have one more question regarding cmake installation in multibuild_config.sh, Is it required for building and running freetype_py tests? |
cmake is used to orchestrate the build of the freetype library that is embedded in the wheel packages |
unless Lines 20 to 21 in c578643
|
Thanks for the info. While building freetype wheel, I am facing below error in travis: Report link: https://travis-ci.org/github/ossdev07/freetype-py/jobs/675620306 Could you please have a look and suggest me if I am missing anything. Thanks. |
you want to build freetype for arm64? |
oh sorry, I just read your comment above about multibuild
well, that's good to hear. I don't have experience building for arm64, so I can't be of help. Maybe others reading this will. |
Thanks for the help. I will check. |
Hi @rougier ,
Travis has added support for ARM64. I have added arm64 jobs and was facing issues with multibuild docker test image. It has been resolved by multibuild as they have added architecture check in install_run function. I have rebased and tried to trigger the build but it is giving error "Build config did not create any jobs."
Requests link: https://travis-ci.org/github/odidev/freetype-py/requests?requestId=206745125
Can you suggest me on what needs to be done for triggering a travis build?
The text was updated successfully, but these errors were encountered: