CanvasKit compilation error since chrome/m139

25 views
Skip to first unread message

sudo

unread,
Oct 17, 2025, 11:04:56 AM (yesterday) Oct 17
to skia-discuss
I tried to upgrade from m135 to m142, but got a compilation error. Went to check earlier branches to see when it last worked and found that to be m138.

OS: win10
In skia/modules/canvaskit and running compile.sh no_font no_skottie

wasm-ld: error: obj/modules/canvaskit/canvaskit.canvaskit_bindings.o: undefined symbol: Simplify(SkPath const&, SkPath*)
wasm-ld: error: obj/modules/canvaskit/canvaskit.canvaskit_bindings.o: undefined symbol: Op(SkPath const&, SkPath const&, SkPathOp, SkPath*)
wasm-ld: error: obj/modules/canvaskit/canvaskit.canvaskit_bindings.o: undefined symbol: Op(SkPath const&, SkPath const&, SkPathOp, SkPath*)
wasm-ld: error: obj/modules/canvaskit/canvaskit.canvaskit_bindings.o: undefined symbol: AsWinding(SkPath const&, SkPath*)

William Candillon

unread,
12:42 PM (10 hours ago) 12:42 PM
to skia-discuss
Sounds interesting, it looks like a regression since libpathops has been moved to core.
I can confirm the issue mon side as well, it's interesting in the config, everything looks ok. 
@Skia Team: This is tested part of CI right?

I only took a brief look but I might try to take a deeper look.

Kind regards,

William

Reply all
Reply to author
Forward
0 new messages