Closed treeswift closed 2 years ago
Wow! I didn't realize that was the issue. Flew right over my head. I think personally that including pthreads instead of getting rid of it would be a better idea. That's just me, though.
The intention never was to remove pthreads though. No clue why it's removed from the build.
git-blame
says:
commit 7b2f8beb9d2663e6e04e4d11b8b899e74943c4c8
Author: Volker Grabsch
Date: 3/5/09, 7:54 AM
disable threading in package cairo, because it conflicts with glib's threading
In my understanding though,
-lharfbuzz
is a separate beast;pthread
.Then the fix would probably be as narrow as adding -lpthread
to freetype2.pc
as described above. Once I finally build a GTK GUI app and see that it works, I can refine a pull request.
Sounds good
Looking into this now, likely going to just use sed to add -lpthread
to freetype2.pc
cause it just seems like a better alternative than likely adding more issues to building than it's worth
My initial attempt to build gtk3 on WSL hit the following ./configure error:
The configure log looks as follows:
IOW, a missing Cairo symbol is mistakenly reported because a different (pthread) symbol is missing from the linker input.
For myself, I kinda quickfixed the build by providing
-lpthread
infreetype2.pc:Libs.private
. However, sincecairo.mk
contains--disable-pthread
, I assume the intention was to get rid of PThread in Cairo+dependencies. Therefore, I need a clarification what a desired permanent fix should be (either declare the pthread dependency or get rid of it in libhafbuzz).My build environment is WSL v2, Ubuntu 20.04 on Windows 10. No Docker.