could you supply bsd*(freebsd/netbsd/openbsd) release binary package? #2320
Labels
Milestone
Comments
nhooyr
added
enhancement
|
Hoping to have a FreeBSD binary in the next release! |
nhooyr
added a commit
that referenced
this issue
Dec 14, 2020
nhooyr
added a commit
that referenced
this issue
Dec 14, 2020
nhooyr
added a commit
that referenced
this issue
Dec 14, 2020
nhooyr
added a commit
that referenced
this issue
Dec 14, 2020
- Removed electron from lib/vscode but kept the types. - electron doesn't support FreeBSD. - Added docs on dependencies of FreeBSD when installing via npm module. - For now, we're going to be shipping a dynamically linked version of node which may cause problems but we can fix that later. Updates #1826 Updates #1880 Updates #2320 Updates #2349
|
Done in #2466 Only thing remaining here is we need a static node v12 binary to ship with the release. Seems like I'm going to have to modify the port somehow. |
|
And need to modify the install script! |
|
Modified the port and got it down to the following: diff --git a/two b/one
index 8d2ff16..8bd6e29 100644
--- a/two
+++ b/one
@@ -1,20 +1,15 @@
- libz.so.6 => /lib/libz.so.6 (0x80224e000)
- libuv.so.1 => /usr/local/lib/libuv.so.1 (0x80226a000)
- libcares.so.2 => /usr/local/lib/libcares.so.2 (0x802299000)
- libnghttp2.so.14 => /usr/local/lib/libnghttp2.so.14 (0x8022b9000)
- libcrypto.so.111 => /lib/libcrypto.so.111 (0x8022e6000)
- libssl.so.111 => /usr/lib/libssl.so.111 (0x8025d8000)
- libicui18n.so.67 => /usr/local/lib/libicui18n.so.67 (0x802670000)
- libicuuc.so.67 => /usr/local/lib/libicuuc.so.67 (0x80299c000)
- libicudata.so.67 => /usr/local/lib/libicudata.so.67 (0x802b9c000)
- libelf.so.2 => /lib/libelf.so.2 (0x802b9e000)
- libutil.so.9 => /lib/libutil.so.9 (0x802bb9000)
- libkvm.so.7 => /lib/libkvm.so.7 (0x802bd1000)
- libm.so.5 => /lib/libm.so.5 (0x802be4000)
- libexecinfo.so.1 => /usr/lib/libexecinfo.so.1 (0x802c16000)
- libc++.so.1 => /usr/lib/libc++.so.1 (0x802c1c000)
- libcxxrt.so.1 => /lib/libcxxrt.so.1 (0x802ce9000)
- libthr.so.3 => /lib/libthr.so.3 (0x802d0b000)
- libc.so.7 => /lib/libc.so.7 (0x802d38000)
- libdl.so.1 => /usr/lib/libdl.so.1 (0x80312e000
- libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x803132000))
+ libcrypto.so.111 => /lib/libcrypto.so.111 (0x802451000)
+ libssl.so.111 => /usr/lib/libssl.so.111 (0x802743000)
+ libicui18n.so.67 => /usr/local/lib/libicui18n.so.67 (0x8027db000)
+ libicuuc.so.67 => /usr/local/lib/libicuuc.so.67 (0x802b07000)
+ libicudata.so.67 => /usr/local/lib/libicudata.so.67 (0x802d07000)
+ libelf.so.2 => /lib/libelf.so.2 (0x802d09000)
+ libutil.so.9 => /lib/libutil.so.9 (0x802d24000)
+ libkvm.so.7 => /lib/libkvm.so.7 (0x802d3c000)
+ libm.so.5 => /lib/libm.so.5 (0x802d4f000)
+ libexecinfo.so.1 => /usr/lib/libexecinfo.so.1 (0x802d81000)
+ libc++.so.1 => /usr/lib/libc++.so.1 (0x802d87000)
+ libcxxrt.so.1 => /lib/libcxxrt.so.1 (0x802e54000)
+ libthr.so.3 => /lib/libthr.so.3 (0x802e76000)
+ libc.so.7 => /lib/libc.so.7 (0x802ea3000)
+ libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x803299000) |
|
Passing configure: make: rerun: |
|
Maybe it's better to publish a code-server port that depends on node12. |
I think it can put the depend libs in diffrent directories, "linux" , "freebsd", "openbsd" and so on, when compile for linux/bsd*, link to the right directory |
|
Hi there, I looked at this earlier and set up a GhostBSD VM to test code-server in; code-server itself works, but quite a few extensions do not, simply because they don't provide FreeBSD binaries. In addition, search also doesn't work because of a lack of a binary from In this state, I don't think I want to further modify VSCode to support FreeBSD (for eg., by shipping our own ripgrep); it can still likely be installed with |
|
For ripgrep all freebsd has ports and pre-built packages for ripgrep and ropgrepall, so all that's needed is to symlink it to the correct place. but currently I can't even install because its now requiring "argon2" |
Dang it! I'm the one who moved us from sha256 to argon2 for hashing passwords. I did not anticipate this happening.
From the argon2 docs. Not sure if those are available in your environment but more info here. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no activity occurs in the next 5 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As title.
The text was updated successfully, but these errors were encountered: