Mirrors/overte
3
0
Fork 0
mirror of https://github.com/overte-org/overte.git synced 2025-04-13 16:24:47 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
overte/console
History
Stephen Birarda 3f3ded09df cleanup packager, add beta icons
2016-01-05 10:16:35 -08:00
..
resources cleanup packager, add beta icons 2016-01-05 10:16:35 -08:00
src show fail on Go Home if interface not present 2016-01-04 18:49:13 -08:00
.gitignore ignore the server-console binary folder for win/linux 2016-01-04 13:59:24 -08:00
CMakeLists.txt specify console folder to copy per-platform 2016-01-04 16:29:00 -08:00
package.json setup packaging as a script 2016-01-04 13:53:26 -08:00
packager.js cleanup packager, add beta icons 2016-01-05 10:16:35 -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.