overte/console
2016-01-18 15:10:05 -08:00
..
resources use an ico for console tray on windows 2016-01-18 14:18:29 -08:00
src fix casing of consts in console main 2016-01-18 14:46:34 -08:00
.gitignore use shell application to avoid fixup on Electron 2016-01-15 15:41:34 -08:00
CMakeLists.txt put build-info in .app resources on OS X 2016-01-18 15:10:05 -08:00
package.json pass build-version through packager script 2016-01-18 12:03:49 -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

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.