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
Are public nightly builds of ChakraCore available somewhere? #1180
Comments
@iskiselev see #85 and https://www.myget.org/feed/chakracore-preview/package/nuget/Microsoft.ChakraCore We publish ch.exe and ChakraCore.dll for both x64 and x86 in those packages. We are basically using those packages as a publication mechanism for the binaries since NuGet packages are just zip files with some metadata and standard arrangement of files inside the archive. They are intended to be nightly, but those builds are from branch release/1.2, which is in stabilization mode, and since there hasn't been much movement on that branch recently we haven't published that package for a couple of weeks. I'm working on enabling publication of those packages from multiple branches so we can have the stabilization branch as well as the WIP branch, |
@liminzhu Maybe we can add a link to the MyGet feed (https://www.myget.org/feed/chakracore-preview/package/nuget/Microsoft.ChakraCore) to the README? |
@dilijev, thank you for provided information. It is what I've looked for! |
Great! |
I've rephrased the title and tagged as Question so that this is easy to find in the future for people looking for info. |
@iskiselev Just published a new one since you're looking for latest. See https://www.myget.org/feed/chakracore-preview/package/nuget/Microsoft.ChakraCore |
It would be great, if Chakra will provide nightly builds (with ch), same as do Firefox SpiderMonkey (https://ftp.mozilla.org/pub/firefox/nightly/latest-mozilla-central/jsshell-win64.zip and others).
It will provide simple way to test big libraries with nightly builds and react early on potential Chakra, library or compatibility issues.
The text was updated successfully, but these errors were encountered: