-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
building harfbuzz with freetype support symbol errors #381
Comments
I guess freetype know about harfbuzz and use a function declared into the harfbuzz. But Harfbuzz don't know about freetype and don't compile the needed method. It might be due to a invalid set of flags / ordering during the compilation maybe ? |
you might be right, i am still trying to figure this out when i get some time as its stopping me progressing with my app. I have tried various different flags and different orderings, but i am stabbing around in the dark quite a bit :/ |
I have created a simple gist which will throw the error when loading freetype. https://gist.github.com/olymk2/d5801d9e1df0459625a3 My current progress is below, i believe it may need the nostdinc option, i believe its building against local libraries but i can convince it to work with nostdinc option. the buildozer.spec file i am using has a hard coded py4a folder so if you use that update it. I am testing on my device by running |
The harfbuzz recipe has changed a lot since this was created, please reopen if it's still a current issue causing a problem. |
Hoping some one can help me out i have spent quite a bit of time on this and not progressed.
From googling around it sounds like this means those methods are not available in the built .so file.
however I can inspect the built files with objdump
I wonder if its a case of freetype cant find harfbuzz to call the method perhaps ?
but i am delving deeper and deeper out of my knowledge level with this stuff.
any one able to lend a hand or offer some things to try ?
you can see my current branch here #378
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: