-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Windows builds #8
Comments
As far as I know, if you have WINE and rcedit installed (to change the application icon and metadata), it should be possible to cross-compile Electron applications without requiring a full C/C++ toolchain. However, I tried running I wonder if it would be easier to use AppVeyor instead. Edit: Deployment of builds using both Travis CI and AppVeyor's built-in deployment systems seems to work fine in trust, so it's probably not an issue. |
@Calinou @wmhilton |
@stripedpajamas |
@TimothyDJewell The official Visual Studio Code Windows installers are created using Inno Setup. I remember seeing the I think providing both options (installer + ZIP archive) is the best. Installers are better-suited for beginners (as they make it easy to add VS Code to the |
Thanks @Calinou! Looks like it's currently at /build/win32/code.iss. I've never done any of this before, but I'll give it a shot. I agree that matching the VS Code options is best. |
@TimothyDJewell thanks for the work so far. Excited to see a Windows build in the near future. Duplicating whatever MS has on their download page is definitely the route to go. It looks like they do provide a Let me know if I can help at all because I'm eager to get the Windows builds working as well 👍 |
It seems Windows ci environment is now available on travis: https://docs.travis-ci.com/user/reference/windows/ |
@G-Ray yes! I was testing it out this past weekend. Unfortunately there is currently a known issue that the build won't work at all if there are secret environment variables (https://travis-ci.community/t/current-known-issues-please-read-this-before-posting-a-new-topic/264). We have a GITHUB_TOKEN environment variable, so it isn't working yet. Once they fix that, I'm excited to see if it's easier to work with than AppVeyor. |
Hey I was interested in fixing the issue for Windows builds, but I see that AppVeyor is paid and Travis still has the secrets issue... Can we try using Azure DevOps? It's free for 10 parallel builds... @stripedpajamas @TimothyDJewell |
@pavanagrawal123 AppVeyor is free for public repositories, lots of open source projects rely on it. That said, Azure Pipelines is worth trying since it features higher limits and supports all three major OSes. |
@pavanagrawal123 any help is welcome and any platform is fine if it produces working Windows builds :) |
@Calinou whoops just noticed it says "free for open source" in big letters @stripedpajamas sure, will try my hand at Azure Pipelines! |
@stripedpajamas and @Calinou I have successfully got Azure Pipelines working! 64bit builds are working on Windows :) How do y'all suggest I publish the artifact onto GH? |
I'm not sure how releases work in Azure. Most likely you will need a personal access token as an environment variable like we have in the Travis build. If you want you can go ahead and open a PR and then we can continue improving it together. |
(also THANKS for your help so far, I'm very excited for Windows builds) @pavanagrawal123 |
Alright, that's what I was thinking as well. I'll clean up a few things and submit the PR in a couple of hours! |
Opened #58. Still doesn't push to GH releases, but that shouldn't be too hard to solve. |
Any plans tfor release? |
It's open in a PR #58. If you want releases now you can check https://github.com/pavanagrawal123/vscodium |
@pavanagrawal123 Hey thanks, I will take a look at them. |
Is this fixed by #58? |
@JL2210 waiting to see if the windows builds succeed and upload. |
@pavanagrawal123 build worked for me |
Any chance of getting the 1.30 Win builds? thanks |
@gerroon yes! I am trying to figure out why it didn't auto build. Should have them later today. |
@stripedpajamas did you figure out what the issue was? |
Two things-- the build is broken and the scheduled builds don't run. Working on part 1; part 2 might not be fixable. Might need to migrate Windows builds over to AppVeyor |
@stripedpajamas we should be able to trigger with a webhook or something though right? also, what's broken on the builds? |
@stripedpajamas thanks for the follow up |
Any way I could help? I have a Debian Stretch system with a mingw-w64
toolchain installed.
…On Sat, Dec 22, 2018, 5:23 PM gerroon ***@***.*** wrote:
@stripedpajamas <https://github.com/stripedpajamas> thanks for the follow
up
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AlC1Cef-8-f86ojAJ3jj7nKRD0U7WZf-ks5u7rDmgaJpZM4WP2Tg>
.
|
I don't have the time to make a PR, but for whoever does, I wanted to suggest using dockcross. I had excellent results with it in cross-compiling clib
The text was updated successfully, but these errors were encountered: