-
Notifications
You must be signed in to change notification settings - Fork 7
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
app-editors/vscode-1.44.2 version bump request #50
Comments
That version requires a dev-util/electron bump as well, and that ain't as simple, unfortunately. |
ok thanks |
Now 1.44.2, which uses Electron 7.1.11 |
my overlay has ebuild for electron 7/8 (and electron-9 on my local disk). Also I write a ebuild to compile vscode using official way ( I don't known why this happened, but using local electron installation to compile native modules will lead to error like above( The relevant code of my ebuild is at https://github.com/12101111/overlay/blob/master/app-editors/vscode/vscode-1.44.2.ebuild#L109 The commented out part( |
I will change the title of this issue sorry for the inconveniences. |
There's a downside to this build. Various features get hidden behind flags, like the ability to use the Remote extensions. |
Most functions of vscode is custom by See also: microsoft/vscode#60 (comment) However, using product.json from Microsoft's visual studio code directly has a license problem:
See also: microsoft/vscode#60 (comment) So people can edit And there is an Open VSX Registry which is a replacement of microsoft's extensions gallery |
That seems like the most reasonable option and I see you've already implemented it. Other than that, I'd like to see about getting Maybe we can have a USE flag like |
|
I get strange slot output from eix from your Electron ebuild(s):
|
Also you need to update the Manifest because it mentions your electron-9 ebuild that doesn't exist in your repo yet. |
I got extremely close with the v8 snapshot build but it failed (
|
@12101111 I'm pretty sure |
This is fixed now.
|
Got to here:
|
fixed: 12101111/overlay@31c29af |
Got to here (
|
fixed: 12101111/overlay@6f2369e |
Got to here:
|
fixed in 12101111/overlay@e710f26 |
It built and installed VS Code, but it doesn't work correctly, mostly in loading an Extension page. It either shows up gray or doesn't load. It seems to be crashing according to the log (truncated):
I used the Settings Sync extension and I can't load its main configuration page with this build, which means it cannot work. Do you think it would work if Electron 7.1.11 were used? |
Electron itself crashes its browser when I click on API Demos. The window turns white. Log:
|
Also your ebuild does not install the .desktop files and the icon for those. |
one question:
There are any way to use python 3 in vscode? |
Nope. Not until Chromium switches to Python 3 for their build scripts. |
thanks for the response. |
This problem was caused by a wrong patch, but I did not find a solution. Without the patch, the code here will cause gcc compilation errors (but no problem with clang): specialization of template after instantiation , and this code was deleted in chromium79 (electron 7 use chromium 78) |
Okay I can rebuild without that patch if you push it, but also might as well update to Code 1.45.0? |
vscode don't depend on python directly, it use node-gyp which use python. |
Did you build Electron without the template-related GCC patch? What were your USE flags for Electron? I have |
Patch is updated. I tested 4 combinations of USE flags: 12101111/overlay#1 (comment) |
Okay. Maybe I will try building tonight but I sort of want to wait till you get Developer Tools within Electron to work. It's useful for bug reports. |
Electron didn't build for me.
|
@elprans Do you have any plans on updating electron and vscode? Should we wait? :) |
I have attempted to write my version of electron and vscode ebuilds based on the work of @elprans and @12101111. Anyone interested may find them in my overlay ::pf4public. They both at the moment miss keywords as they require some more work, but I could successfully compile them: |
I gave up with this overlay. But for people reaching this bug from internet, |
1.49.0 is in the tree. |
there are a new version of vscode 1.43.2
I did a simple version bump and it woks for me. (edited: obsolete comment)
I can try to do a pull request if you want.
Thanks in advance.
EDITED:
now there are another version 1.44.2
as pointed by @Tatsh
with new requirements.
The text was updated successfully, but these errors were encountered: