[build] Java.Interop should use <ProjectReference/> for jnienv-gen #477
Conversation
This file contains hidden or 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
Java.Interop had a custom MSBuild target that builds
`jnienv-gen.csproj`:
<Target Name="BuildJnienvGen"
Inputs="..\..\build-tools\jnienv-gen\jnienv-gen.csproj"
Outputs="$(JNIEnvGenPath)\jnienv-gen.exe">
<MSBuild
Projects="..\..\build-tools\jnienv-gen\jnienv-gen.csproj"
/>
</Target>
The problem with this, is if any `.cs` files change in
`jnienv-gen.csproj`, then this target will not run.
Instead we should be able to use `<ProjectReference/>` with
`%(ReferenceOutputAssembly)=False`, and everything should "just work".
Added `Gendarme` `$(Configuration)`
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Java.Interop had a custom MSBuild target that builds
jnienv-gen.csproj:The problem with this, is if any
.csfiles change injnienv-gen.csproj, then this target will not run.Instead we should be able to use
<ProjectReference/>with%(ReferenceOutputAssembly)=False, and everything should "just work".