Skip to content
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

cjs port to mozjs-128 #124

Closed
willysr opened this issue Sep 18, 2024 · 6 comments
Closed

cjs port to mozjs-128 #124

willysr opened this issue Sep 18, 2024 · 6 comments

Comments

@willysr
Copy link

willysr commented Sep 18, 2024

Hi,

is there a plan to move to mozjs 128?
gjs seems to move already
https://gitlab.gnome.org/GNOME/gjs/-/commit/e2ce7205f67feede3dd11e4e10ccf56d545ad647

@Fantu
Copy link
Contributor

Fantu commented Oct 6, 2024

There is also an open bug related in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081039

@willysr
Copy link
Author

willysr commented Oct 15, 2024

@fulalas
Copy link

fulalas commented Oct 15, 2024

Although it compiles, when I try to load the actual Cinnamon desktop, it fails to run the panel, muffin, etc. By reverting to no patch and mozjs115 it works straightaway.

@Fantu
Copy link
Contributor

Fantu commented Oct 15, 2024

I don't understand exactly what is that big patch without details, seems a rebase, anyway a rebase need to be accurate and can require big amount of time and is very good to specify the exact version (and/or commit) of rebase to make easier check upstream fixes and make faster import them.
Need to check also if in the new version there are important changes that need changes also in cinnamon to adapt to the new version of cjs the first thing to look at is the api changes, you may start to see certain changes from any debug symbols added or removed, but further changes may still be needed.
Also for this reason it is useful to mark the exact version of gjs every rebase, so you can see on gjs the relevant changes between the 2 versions of rebases that require changes to the software that uses it

@clefebvre
Copy link
Member

#127

@willysr
Copy link
Author

willysr commented Mar 27, 2025

thanks @clefebvre

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants