Skip to content

automatic compilation and github releases#86

Open
AcrylonitrileButadieneStyrene wants to merge 6 commits intoynoproject:masterfrom
AcrylonitrileButadieneStyrene:master
Open

automatic compilation and github releases#86
AcrylonitrileButadieneStyrene wants to merge 6 commits intoynoproject:masterfrom
AcrylonitrileButadieneStyrene:master

Conversation

@AcrylonitrileButadieneStyrene
Copy link
Copy Markdown

adds a docker file for setting up the build tools, when ran acts like a compiler (source is passed in with -v)
adds configuring the PSK through an env var (which can be passed into docker with -e)

unrelated changes:

  • removes some unused platform code in CMakeLists.txt (ynoengine only supports emscripten)
  • moved all arguments to new lines in the cmake_build.sh files for readability
  • removes some existing workflows that did not seem relevant to ynoengine

after merge setup steps:

  1. manually trigger the "Build Docker Image" workflow
  2. add a github secret named PSK, including the braces around the bytes
  3. re-trigger the action that failed due to steps (1) and/or (2) missing

Comment thread Dockerfile
Comment on lines +21 to +23
RUN autoreconf -fi
RUN bash -c "source /root/workdir/buildscripts/emscripten/emsdk-portable/emsdk_env.sh; \
emconfigure ./configure --prefix=/root/workdir/buildscripts/emscripten --disable-shared"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

liblcf could be built with cmake instead

docker run -v $(pwd):/root/workdir/ynoengine:rw -e PLAYER_PSK="${{ secrets.PSK }}" ghcr.io/${REPO,,}:master
docker run -v $(pwd):/root/workdir/ynoengine:rw -e PLAYER_PSK="${{ secrets.PSK }}" -e NO_SIMD=1 ghcr.io/${REPO,,}:master
echo "TAG=$(date +'%Y-%m-%d.%H.%M.%S')" >> $GITHUB_ENV
- uses: softprops/action-gh-release@v3
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since we most likely build local then deploy straight to server this step is probably not needed; could provide instructions to build local instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants