Build instructions

No build instructions for this software. It would be helpful to know how to build it from the release tarball.

This is planned. For now you can do:

yarn
yarn task build:server:binary

It should output to packages/server/cli-[platform]

Also use node >=8 and <9.

Required (Ubuntu) packages: https://github.com/codercom/code-server/blob/master/.travis.yml#L10
If you're using stock Node.js/npm on some distros, you would need to perform npm install -g npm to fetch newer npm which has npx binary with it.

be sure that the node version you have installed has an appropriate release for nexe/nexe, I had node 8.15.1, but there's only 8.15.0 in nexe, so I downgraded node to get this to build.

Dockerfile is available for those of you who want to dev for linux.

So lets just document the existence of the Dockerfile and for other platforms, people can look at the .travis.yml.

I have tried in CentOS, record in #23 (comment) , hope that help others

After I run yarn task build:server:binary everything builds successfully from what I can see but there are no binaries in packages/server/cli- there are no cli directories under packages/server

I was able to get a full build working however on running I get the following error:

Error: /lib64/libstdc++.so.6: version GLIBCXX_3.4.20' not found`.

I installed the latest library which contains that version but is on a non-standard path. I updated LD_LIBRARY_PATH but to no effect. Any suggestions?

I actually realized that I was building from master. When I built from the latest tag, it worked. Thanks!

Is there no way to build from master and get a binary?

I believe there's a yarn task to build and get a binary.

I'd reference our Dockerfile.

I was able to get a full build working however on running I get the following error:

Error: /lib64/libstdc++.so.6: version GLIBCXX_3.4.20' not found`.

I installed the latest library which contains that version but is on a non-standard path. I updated LD_LIBRARY_PATH but to no effect. Any suggestions?

I met the same problem recently, build instructions are needed for users to run this software on some old versions of OSes.

We are adding better documentation to our April to-do list. Sorry it has taken so long 🤕

A new issue was opened on this #417

Closing in favor of #417.

Add stdio sources (#17)

I believe there's a yarn task to build and get a binary.

I'd reference our Dockerfile.

hi, the Dockerfile is missing, can you share it?

We no longer have a Dockerfile that builds code-server but we have documentation for building here: https://github.com/coder/code-server/blob/main/docs/CONTRIBUTING.md#build

If you are looking for our release image though (it takes an already-built code-server as input) that can be found here: https://github.com/coder/code-server/blob/main/ci/release-image/Dockerfile

We no longer have a Dockerfile that builds code-server but we have documentation for building here: https://github.com/coder/code-server/blob/main/docs/CONTRIBUTING.md#build

I am follow the steps to do building.
When run node . in release folder. Got error Error: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /home/cddev/Downloads/code-server-4.0.1/release/node_modules/argon2/lib/binding/napi-v3/argon2.node)

My centos 7 mechine's GLIBC version is 2.17. So i attempt to upgrade GLIBC to 2.25. But fail.
Is there any other way to resolve the GLIBC_2.25 error?

What happens if you run npm_config_build_from_source=true node . in the release folder? see here

We no longer have a Dockerfile that builds code-server but we have documentation for building here: https://github.com/coder/code-server/blob/main/docs/CONTRIBUTING.md#build

I am follow the steps to do building. When run node . in release folder. Got error Error: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /home/cddev/Downloads/code-server-4.0.1/release/node_modules/argon2/lib/binding/napi-v3/argon2.node)

My centos 7 mechine's GLIBC version is 2.17. So i attempt to upgrade GLIBC to 2.25. But fail. Is there any other way to resolve the GLIBC_2.25 error?

I meet the same problem, can you tell me how do you fix it?

Navigation Menu

Repository navigation

Build instructions #17

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Build instructions #17

Description

Activity

kylecarbs commented on Mar 5, 2019

grant commented on Mar 6, 2019

muojp commented on Mar 6, 2019

bketelsen commented on Mar 6, 2019

nhooyr commented on Mar 7, 2019

nhooyr commented on Mar 8, 2019

uddmorningsun commented on Mar 9, 2019

tvarwig commented on Mar 12, 2019

activatedgeek commented on Mar 13, 2019

activatedgeek commented on Mar 13, 2019

bpmct commented on Mar 22, 2019

NGTmeaty commented on Mar 22, 2019

wongxingjun commented on Mar 27, 2019

nol166 commented on Apr 3, 2019

MichaelDesantis commented on Apr 3, 2019

code-asher commented on Apr 25, 2019

qinzehua commented on Jan 11, 2022

code-asher commented on Jan 11, 2022

code-asher commented on Jan 11, 2022

qinzehua commented on Jan 12, 2022

jsjoeio commented on Jan 12, 2022

codegzx commented on Sep 25, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions