Mirrors/overte-AleziaKurdis
3
0
Fork 0
mirror of https://github.com/AleziaKurdis/overte.git synced 2025-04-08 02:14:41 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
overte-AleziaKurdis/console
History
Stephen Birarda 89386e9dca use CONSOLE_EXEC_NAME shortcut for name
2016-01-19 16:04:43 -08:00
..
resources Update notification icon 2016-01-19 14:55:40 -08:00
src Remove test notification code 2016-01-19 15:06:03 -08:00
.gitignore use shell application to avoid fixup on Electron 2016-01-15 15:41:34 -08:00
CMakeLists.txt use CONSOLE_EXEC_NAME shortcut for name 2016-01-19 16:04:43 -08:00
package.json Update console dependencies 2016-01-19 14:41:57 -08:00
packager.js add various root files to console package ignore 2016-01-18 14:35:36 -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.