-
Notifications
You must be signed in to change notification settings - Fork 118
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
Use moztools instead of mozilla-build #368
Conversation
This is a nice change! Some suggestions:
|
|
This is the status quo with MozillaBuild so I think it's fine to keep this behavior for now. I think we should hold off on the download step...because we really haven't decided what to do with this dependency. For instance, maybe we could convert it into a crate and avoid having to do a manual download at all. |
Using mozilla-build was easier as you can just simply install mozilla-build using installer and open mozilla-build shell (like you would do if you wanted to develop for firefox) and run commands from there. Manually setting |
9acc49f
to
2882c4a
Compare
288ac5e
to
cece0e2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should not download moztools in build.rs
. In addition the comments above, this introduces a hidden dependency on cURL to build this crate. Let's just do the minimal change here and require that it be unzipped ahead of time and an environment variable set.
Curl is installed on every Win10+ system by default otherwise we could just depend on some rust crate for downloading. I already have separation per commits, but now I would like to test with servo first and then do changes here. |
00bf60e
to
2cbad03
Compare
Successful servo test here: https://github.com/sagudev/servo/actions/runs/5899499296 |
I think this should accept either My suggestion is |
You are right, while we are still on moztools-3.2 we can still support MozillaBuild 3.2+ |
@mrobinson any progress? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay in reviewing. This looks good to me. The one larger change I think we should have apart from the small things below is that we should update the README to explain downloading, unzipping, and setting the environment variable for moztools. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, a couple other tiny things.
ObjectOpResult { | ||
code_: ObjectOpResult_SpecialCodes::Uninitialized as usize, | ||
} | ||
ObjectOpResult { code_: ObjectOpResult_SpecialCodes::Uninitialized as usize } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Were these changes added by mistake?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I run cargo fmt
and I guess this was not formatted properly before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks!
Head branch was pushed to by a user without write access
Failures are not my fault: actions/runner-images#8125 |
This makes mozjs on windows more standalone and allows to remove presetting variables in servo.
Servo's
./mach bootstrap
can still download moztools and mozjs will use downloaded moztools if they are right version.WIP because I still need to make companion PR for servo.
Fixes #300
Supersedes #326 & #356