Skip to content
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

Ensure Unity publishing works without disrupting other targets #25

Merged
merged 2 commits into from
Oct 3, 2023

Conversation

reeseschultz
Copy link
Contributor

@reeseschultz reeseschultz commented Oct 2, 2023

This pull request fixes this problem: genaray/Arch#143 (reply in thread).

(However, note that tests for Arch.Extended were already failing before the Unity publishing changes were merged.)

Now the TargetFramework for projects that otherwise didn't have it is set to net7.0 which will prevent the tests from failing (for that reason). TargetFramework, TargetFrameworks and TargetFrameworkVersion are also now forced in the UnityPublish.sh script as arguments, because it 100% reliably overwrites whereas putting them in Directory.Build.targets apparently didn't. I'm not a fan of MSBuild.

I'm additionally ensuring that any previously published assemblies are deleted before new ones are generated again just to be safe. We don't want old ones to gunk up the directory. And I removed some confusing language about codegen from the shell script. Sorry for all the hassle with this. It's a lot of trial and error wrangling this build system to comply with reason.

Edit: Sister PR: genaray/Arch#152

@genaray genaray merged commit 04ed5b7 into genaray:master Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants