mirrors/moonlight-stram_moonlight-chrome
2
0
Fork 0
mirror of https://github.com/moonlight-stream/moonlight-chrome.git synced 2025-10-26 11:18:07 +00:00
Code Issues Packages Projects Releases Wiki Activity
GameStream client for ChromeOS
537 Commits 4 Branches 15 Tags 13 MiB
C 92.3%
JavaScript 3.7%
C++ 2.9%
HTML 0.4%
Makefile 0.4%
Other 0.3%
232e3c57f3
Go to file
Cameron Gutman 232e3c57f3 Add a CA bundle for CURL
2020-07-11 15:40:50 -07:00
.github Centralize Discord invite links 2020-01-18 10:55:11 -08:00
h264bitstream Use h264bitstream library to mixup the SPS so OS X will use hardware decoding 2016-02-21 15:57:45 -05:00
icons Update icons 2017-08-23 23:04:22 -07:00
libgamestream Add a CA bundle for CURL 2020-07-11 15:40:50 -07:00
moonlight-common-c@407d57a50a Update moonlight-common-c to fix QoS-related connection issues 2020-06-12 22:12:15 -07:00
opus@f6f8487b76 loaded image grid, need to finish including google material icons and to add functionality to the grid 2016-07-04 17:45:29 -05:00
ports Update curl to 7.44.0 (latest webports version) 2018-12-24 00:13:44 -08:00
static Add a CA bundle for CURL 2020-07-11 15:40:50 -07:00
.gitignore ignoring visual studio generated directories 2017-10-22 13:05:05 -07:00
.gitmodules Add Opus library for audio decoding 2016-02-13 22:12:38 -05:00
auddec.cpp Update to latest moonlight-common-c 2017-06-11 15:52:03 -07:00
CODE_OF_CONDUCT.md Update readme to new URL 2018-12-03 21:45:15 -08:00
common-c.mk Update common-c 2018-11-03 17:30:11 -07:00
connectionlistener.cpp Change errorCode from long to int 2020-02-24 23:44:38 -08:00
gamepad.cpp Send attached gamepads at launch to fix L4D2 2018-01-20 15:08:36 -08:00
h264bitstream.mk Use h264bitstream library to mixup the SPS so OS X will use hardware decoding 2016-02-21 15:57:45 -05:00
http.cpp Add a CA bundle for CURL 2020-07-11 15:40:50 -07:00
index.html Address broken error checking for launch requests and other minor issues 2018-06-12 21:23:24 -07:00
input.cpp Add a small touch deadzone for double clicking 2020-04-22 19:44:46 -07:00
libchelper.c Update libcurl webports and dependencies for IPv6 support 2017-09-02 22:28:44 -07:00
libgamestream.mk Pairing is working 2016-02-28 00:25:49 -05:00
LICENSE Initial commit 2016-02-12 20:28:41 -05:00
main.cpp Add direct touchscreen mouse support 2020-04-22 19:22:32 -07:00
make.bat New message handling, and new NvAPI 2016-02-25 07:58:36 -03:00
Makefile Fix compiler flags 2019-02-27 00:33:52 -08:00
manifest.json Version 0.10.3 2020-05-26 20:48:53 -07:00
moonlight.hpp Add a small touch deadzone for double clicking 2020-04-22 19:44:46 -07:00
opus.mk Add Opus library for audio decoding 2016-02-13 22:12:38 -05:00
ports.mk Fix makefile and add libraries required for building 2016-03-10 21:40:17 -08:00
profiling.cpp Improve profiling code 2016-05-09 14:25:58 -04:00
README.md Update README 2020-05-27 19:58:32 -07:00
viddec.cpp Add direct touchscreen mouse support 2020-04-22 19:22:32 -07:00

README.md

Moonlight for ChromeOS

Moonlight for ChromeOS is an open source implementation of NVIDIA's GameStream, as used by the NVIDIA Shield, but built to run on ChromeOS.

Moonlight for ChromeOS allows you to stream your full collection of games from your powerful desktop to another PC or laptop running ChromeOS.

For Windows, Mac, and Linux, we recommend running the new PC port for maximum performance.

Moonlight also has mobile versions for Android and iOS/tvOS.

Check out the Moonlight wiki for more detailed project information, setup guide, or troubleshooting steps.

Moonlight for ChromeOS

Building

  1. Install the Chrome Native Client SDK and download the current Pepper SDK
  2. Set the NACL_SDK_ROOT environment variable to your Pepper SDK folder. If you need more detailed instructions, see here
  3. Run git submodule update --init --recursive from within moonlight-chrome/
  4. Run make from within the moonlight-chrome/ repo

Testing

  1. Open the Extensions page in Chrome
  2. Check the 'Developer mode' option
  3. Click 'Load unpacked extension' and point it at your built moonlight-chrome repo
  4. Run Moonlight from the extensions page
  5. If making changes, make sure to click the Reload button on the Extensions page