-
Notifications
You must be signed in to change notification settings - Fork 58
[build] remove XAIntegrationDebug and XAIntegrationRelease #368
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
[build] remove XAIntegrationDebug and XAIntegrationRelease #368
Conversation
In PR: dotnet#360 I will likely add a new `$(Configuration)` to be used in xamarin-android, so we can build `Java.Interop` as a non-PCL. The existence of `XAIntegrationDebug` and `XAIntegrationRelease` are confusing, since they are no longer used. See: dotnet@54a2aff dotnet/android#1231 This removes `XAIntegrationDebug` and `XAIntegrationRelease` from all solutions, project files, and `Makefile`. I also let VS 2017 update the SLN file, as it was an old VS 2010 format...
I'm having to backport this, to fix: dotnet/android#2157 And then the SLN file had a conflict, so opening this PR. The build failure in #2157 is mentioning
|
@@ -116,7 +94,7 @@ | |||
<Compile Include="Java.Interop\JniAddNativeMethodRegistrationAttribute.cs" /> | |||
<Compile Include="Java.Interop\JniNativeMethodRegistrationArguments.cs" /> | |||
</ItemGroup> | |||
<ItemGroup Condition=" !$(Configuration.StartsWith('XAIntegration')) "> | |||
<ItemGroup> |
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 we can just merge these 2 item groups.
@@ -12,7 +12,7 @@ NATIVE_EXT = .so | |||
DLLMAP_OS_NAME = linux | |||
endif | |||
|
|||
XA_CONFIGURATION = XAIntegrationDebug | |||
XA_CONFIGURATION = Debug |
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.
Do we need to keep this around?
I guess we should remove more stuff like xa-fxcop
rule, xa-all
rule, XA_INTEGRATION_OUTPUTS
variable, ...
Mainly looking to backport this to get this one green: dotnet/android#2157 @jonpryor can I address @radekdoulik's review comments on master in another PR? |
@jonathanpeppers asked:
Yes, those can be in a separate PR. |
Context: dotnet#368 Addressing the comments in dotnet#368, this removes more unused build targets, etc.
Context: dotnet#368 Addressing the comments in dotnet#368, this removes more unused build targets, etc.
Context: dotnet#368 Addressing the comments in dotnet#368, this removes more unused build targets, etc.
In PR: #360
I will likely add a new
$(Configuration)
to be used inxamarin-android, so we can build
Java.Interop
as a non-PCL.The existence of
XAIntegrationDebug
andXAIntegrationRelease
areconfusing, since they are no longer used.
See:
54a2aff
dotnet/android#1231
This removes
XAIntegrationDebug
andXAIntegrationRelease
from allsolutions, project files, and
Makefile
.I also let VS 2017 update the SLN file, as it was an old VS 2010
format...