overte/console
2015-12-16 09:11:24 -08:00
..
modules Merge branch 'console' of github.com:birarda/hifi into console 2015-12-15 14:07:55 -08:00
resources Update icons 2015-12-03 12:15:58 -08:00
.gitignore add commands for local debug and local release 2015-12-03 13:48:37 -08:00
CMakeLists.txt add PACKAGING_TARGET_NAME variable 2015-12-03 13:48:37 -08:00
index.html Add log opening to console 2015-12-16 09:11:24 -08:00
index.js Add log opening to console 2015-12-16 09:11:24 -08:00
jquery.js Add support for starting/stopping interface 2015-12-03 09:29:21 -08:00
main.js Add log opening to console 2015-12-16 09:11:24 -08:00
package.json add README and local binary cl options 2015-12-03 13:49:20 -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.