Pull upstream into personal repo #3
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pkgbuild is used as of Mac OS X Lion.
The latter is what CMake (3.16+) itself uses; we should start using CMake's own unity build capabilities if available.
These are not intended to be invoked by the user directly, so .exe wrappers do not need to be generated. maya2egg will find the _bin equivalent by looking for it next to the executable itself.
It doesn't seem like this setting is actually needed (because mayapath does the necessary set-up), but while it's set, we might as well set it to something more sensible.
This is needed when compiling without -undefined dynamic_lookup
…ing to fullscreen on MacOS 10.15+ Fixes #794
Also disable coverage testing for Python 2.7 and 3.5, since they are respectively EOL and do not use deterministic dictionary ordering.
This is necessary because install_name_tool invalidates the signature, which causes the whole app to fail validation and refuse to open.
This prevents a common error of trying to load non-Panda3D assets without specifying $MAIN_DIR. We aren't currently making any guarantees about the cwd (which may in fact be / when launching from Finder), so I think this is safe.
The latter in particular will be called instead of __init__, so must construct the object.
* Support converting BitMask types to int * BitArray constructor accepts a Python long of arbitrary size * DoubleBitMask (and QuadBitMask, by extension) supports Python long in constructor * Support for pickling (except DoubleBitMask) * All of them now properly define __bool__() * More unit tests Fixes #886
Rather than going through the TypedWritable/bam route, this encodes InternalNames in a more compact and efficient manner.
This is not actually used by anything, but we might as well ensure that it's set to something sensible
I'm mostly trying to make sure we have over-coverage for a couple of places that are being hit intermittently by our current unit tests, generating noisy codecov reports. If we make sure these places are hit always, we hopefully won't have codecov misreport lost/gained coverage for unrelated changes.
Values above 10 MiB are displayed in MiB and values above 4 GiB are displayed in GiB. Closes #881
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.