-
Notifications
You must be signed in to change notification settings - Fork 128
[release/5.0] Build against Cecil submodule #1477
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
Conversation
|
We discussed the ref issue and for 5.0 it should not matter - we're not changing public APIs in Cecil in the fork, so consumers can still refer the official Cecil package and compile against that. At runtime the forked Cecil will be used, but since public APIs are identical everything should work just fine. |
With this change, the nuspec of the ref assembly package will list cecil verision 0.11.2 as a dependency (instead of 5.0.0-rc*). This allows consumers of the ref package to use the publicly released cecil.
|
The ref package will now depend on a package version that matches the official cecil, as discussed with @vitek-karas. |
| as the package dependency. This way the linker ref assembly package | ||
| will depend on the publicly available package. Note that we can't set | ||
| just set Version here because Arcade will override it. --> | ||
| <PackageVersion>$(MonoCecilVersion)</PackageVersion> |
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.
It'd be better to stop the build when the versions don't match but it does not look like it's doable with current Cecil setting
* Build against Cecil submodule * Depend on official cecil version With this change, the nuspec of the ref assembly package will list cecil verision 0.11.2 as a dependency (instead of 5.0.0-rc*). This allows consumers of the ref package to use the publicly released cecil.
* Build against Cecil submodule * Depend on official cecil version With this change, the nuspec of the ref assembly package will list cecil verision 0.11.2 as a dependency (instead of 5.0.0-rc*). This allows consumers of the ref package to use the publicly released cecil.
Doing this will change a few things:
release/5.0will now have a dependency on the local cecil version (it gets a5.0.0-rc*version from our Versions.props). To consume it, the consuming project needs to include a version of Mono.Cecil compatible with this version, which in practice probably means also building against the submodule and giving it a custom version. @marek-safar I assume that this is OK since we will go back to shipping with the official package when use the ref assembly for plugins in 6. The alternative is to build the ref and lib against different versions of Cecil.