Basically don't abuse OSG as badly. We need to let it know we've bound a shader program so it doesn't assume the FFP is still used, but it doesn't have a built-in way to apply the uniforms when doing so, so we need to do it manually.
This is a combination of 3 commits.
This is the 1st commit message:
Use the correct path
This will be the last non-deranged commit message on this branch.
This is the commit message #2:
🤨🤨🤨🤨
This is the commit message #3:
🙈🙉🙊
pick e140f1aa3a Use the correct path
squash 28744e367c 🤨🤨🤨🤨
squash b57bde40a2 🙈🙉🙊
We have to get it from Amazon directly and run an install script as
aws-cli v2 (which is what we use on Windows) is only shipped as a snap,
and snaps don't work on Docker, which the GitLab runners use.
This is a combination of 4 commits.
This is the 1st commit message:
Install aws-cli
Get it from snap because apt only has 1.x versions.
Pass --classic so it can actually see files.
This is the commit message #2:
But snapd isn't installed by default even though it's Ubuntu's recommended way to install everything
This is the commit message #3:
Mysterious snap-fixing incantation
I guess the service isn't running my default until the next reboot?
This is the commit message #4:
Snap doesn't work in Docker, apt doesn't have awscli v2+, let's just install random binaries wherever they want to put themselves
pick 5f0dfbf768 Install aws-cli
squash 1ed2a711fc But snapd isn't installed by default even though it's Ubuntu's recommended way to install everything
squash 230c917993 Mysterious snap-fixing incantation
squash 75142ff3c2 Snap doesn't work in Docker, apt doesn't have awscli v2+, let's just install random binaries wherever they want to put themselves
You can only use variables to specify the dependency job if you also
specify the project and ref. I couldn't find a built-in variable that
evaluated to the current ref or particularly clear documentation of what
ref even meant in this context (GitLab uses it for a few different
things in CI as far as I can tell).
This is a combination of 2 commits.
This is the 1st commit message:
Project permits variables in job names?
This is the commit message #2:
Using a variable is getting too hard, just copy and paste some stuff
pick cf1c4dfa73 Project permits variables in job names?
squash e5e888ac77 Using a variable is getting too hard, just copy and paste some stuff
Originally this had a double closing '' which wasn't noticed until
several commits later when it was fixed well enough to actually reach
that line. That change has been time-travelled and squashed after a big
argument.
This is a combination of 2 commits.
This is the 1st commit message:
Compress symbols in separate job
Typo
pick 9c27586080 Compress symbols in separate job
squash b072d7e33f Typo
