-
Notifications
You must be signed in to change notification settings - Fork 206
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
Apple M1 MacBook Pro: winit bump #483
Comments
Pathfinder is not actively maintained, but pdf_render relying on a fork of pathfinder does make it harder. It looks like the API issue is due to the pathfinder fork exposing a method that this repository does not: s3bk@32497ee . What if you made a PR to update winit in pdf_render first? Would that be enough to allow updating the pdf_render dependency in this repository? |
I'll give that a go. |
Yes the |
Yep, sorry about that! |
This issue isn't fixed, despite merging #474, right? I'm still getting 'mismatched types' errors for |
Sorry, I will test it now. |
pdf_render does not have a fixed version of winit, so I would expect that a |
It runs on linux.. until it crashes. |
Just running
Edit: running macOS, btw |
well. I am a git "master". Turns out it helps to test in the correct repository ... I am trying now with #490 |
It compiles in #491 .. but instantly crashes.
|
Still getting the winit compilation errors. I mean, the version still seems to be on <0.19.4, right? |
Maybe your x11 errors are unrelated? |
Maybe. I will try updating winit to 0.26 |
Surfman needs updating too .... |
Yeah. Just found the surfman dep as well. |
We are using this commit it seems like: https://github.com/servo/surfman/blob/f3df871ac8c3926fe9106d86a3e51e20aa50d3cc/surfman/Cargo.toml |
Seems to be the @pcwalton's last commit on the project. That explains it. |
Updated to the latest surfman and got past the initial winit errors. Now I'm updating |
shall I send you my changes so far? I guess not really worth it... and it isn't finished. |
You could. I guess it's just a lot of winit changes to accommodate. |
Not the winit expert myself. Don't really know which of these errors just need their names changed and which need complete overhaul. Can't tell how much winit has changed since then. |
Same. But it is quite late here and I need to fix my font crate. |
BTW @s3bk, why are u trying to debug this? Are you interested in this crate because of glyph dilation as well? Or different reason? |
I was just trying to get the demo back working for you. I use pathfinder via https://github.com/s3bk/pathfinder_view which is working. The font crate is used to render pdfs... and extract text from it. |
Hello! Now that the servo project is being reactivated, are bugs like this one expected to be addressed moving forward? |
No. Pathfinder is not used in Servo at this point in time,and I'm not aware of plans to integrate it. |
Thank you. What does Servo currently use for vector graphics rasterization/rendering? |
Servo does not perform vector graphic rasterization at this time. |
@jdm Got it, thank you. How is Servo currently rendering text and vector-based graphics, such as svg? Is that CPU-based currently? |
Servo does not support svg at this point. It uses font-kit for rendering text. |
On an Apple M1 MacBook Pro, the
winit
dependency build fails with:This is fixed in
winit v0.24.x
(see rust-windowing/winit#1782 where this was reported originally).So, I bumped
winit
and made a bunch of changes to catch up with its more recent API. After that, I was able to run some of the examples on an M1 Mac (eg.canvas_minimal
is working). See this diff for the changes required tocanvas_minimal/src/main.rs
: lancelet@720785e#diff-53ffc830c4d0e3773cb67c3cedd3e24330ba22eccc7ccb66f731b9586fdf6584However, there's a circular dependency between both
pdf
andpathfinder
, which is making it difficult for me to complete the refactoring within pathfinder itself.pdf
andpdf_render
bring in a dependency onwinit
, and use a part of the pathfinder API that has been made private:To make things worse,
pdf
andpdf_render
seem to be using patches on top of pathfinder, so that confuses the matter still further.I don't know what the best way forward is. If
pdf
depends onpathfinder
, perhaps it's best not to usepdf
examples inpathfinder
itself, but rather put appropriate examples in thepdf
package instead? (Or in a third party repository which coordinates a minimum bound on the two?) Any suggestions? If I raised a PR to removepdf
andpdf_render
as dependencies for all of pathfinder (ie. removing those examples), would that be accepted?The text was updated successfully, but these errors were encountered: