-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Translocation fix #273
Merged
Merged
Translocation fix #273
Changes from all commits
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
fa63bee
Update gitignore for temp codesigning artefacts
firthm01 70c8ffe
Look for setup files in setup app bundle
firthm01 166983f
Don't require hyphen before "tweak" portion of version tag
firthm01 0c60a7a
Update changelog and release process
firthm01 926a08d
Update readmes and license
firthm01 7155b52
Setup app icon (MacOS)
firthm01 87af62a
Collate a list of EPS VST targets
firthm01 86da81e
Copy setup resources in to bundle as post build step
firthm01 d09c41b
Update packaging install locations
firthm01 7b1680f
Try install components to app resources during packaging
firthm01 bb24cda
Correct install paths
firthm01 dc04001
Fix setup install path on macos when packaging
firthm01 2b26eb1
Correct "Content" in paths
firthm01 bef3c71
Correct path for readmes and license on macos
firthm01 ece886d
Don't forget proj upgrade tools
firthm01 05e7396
Don't forget Templates (and general tidy)
firthm01 ce3b897
Codesigning status
firthm01 6cb5d2b
Merge branch 'translocation-fix' of github.com:ebu/ear-production-sui…
firthm01 e21b6e2
Update codesign.py paths
firthm01 6de4863
Update comment
firthm01 56a1b23
Revert "Update comment"
firthm01 bd911d5
Use common target_sources call for setup
firthm01 976ea2e
Fix tab/space mess
firthm01 f8afca7
Avoid passing up var by using CACHE INTERNAL
firthm01 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,4 +5,3 @@ add_subdirectory(hoa) | |
add_subdirectory(scene) | ||
add_subdirectory(monitoring) | ||
add_subdirectory(binaural_monitoring) | ||
|
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
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
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
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
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
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
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
Binary file not shown.
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
Binary file not shown.
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is only true when run on CI? (took me a while to track it down, but I think '.' means the root of CMAKE_INSTALL_PREFIX, which is set by build.yml)
If we were to configure and install locally with EPS_PACKAGE set, does that mean we'd get everything in the CMAKE_INSTALL_PREFIX root, (and presumably the setup app would be broken?)
Is there a reason for doing it that way, or would we be better with
# other install commands
and keeping the install prefix consistent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh wait, I just saw your comment at the top of the PR. Sorry :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it's maybe still valid as it's nice to be able to do a CI-style build locally (I don't think doing it this way negates that as the packaging file is only run if specified via a cache var). If it's hard for some reason (the post-build step suggests it probably is) then maybe keep things as they are.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Issue #275 opened to tackle local packaging at a later date