Mirrors/overte
3
0
Fork 0
mirror of https://github.com/overte-org/overte.git synced 2025-04-17 23:26:35 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
overte/console
History
Stephen Birarda fcc0c92ff1 put console/build-package in installer folder
2016-01-04 15:13:29 -08:00
..
resources replace console tray icons 2015-12-28 16:42:48 -08:00
src rename tooltip for tray to proper name 2016-01-04 13:53:34 -08:00
.gitignore ignore the server-console binary folder for win/linux 2016-01-04 13:59:24 -08:00
CMakeLists.txt put console/build-package in installer folder 2016-01-04 15:13:29 -08:00
package.json setup packaging as a script 2016-01-04 13:53:26 -08:00
packager.js change a comment in packager.js 2016-01-04 13:54:39 -08:00
README.md add initial local process search 2015-12-03 13:49:53 -08:00

README.md

Console

The High Fidelity Desktop Console, made with Electron.

Running Locally

Make sure you have Node.js installed. Use the latest stable version.

npm install
npm start

To run, the console needs to find a build of Interface, domain-server, and assignment-client.

The command npm start tells the console to look for builds of those binaries in a build folder beside this console folder.

On platforms with separate build folders for release and debug libraries npm start will choose the debug binaries. On those platforms if you prefer to use local release builds you'll want npm run local-release.

Packaging

CMake produces a target package-console that will bundle up everything you need for the console on your platform. It ensures that there are available builds for the domain-server, assignment-client, and Interface. Then it produces an executable for the console.

Finally it copies all of the produced executables to a directory, ready for testing or packaging for deployment.