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

[System.Drawing.Primitives] Add System.Drawing.Primitives.dll Facade #121

Merged
merged 1 commit into from
Jul 15, 2016

Conversation

jonpryor
Copy link
Member

Xamarin.Android needs to support .NET Standard 1.6, which
mentions a System.Drawing.Primitives.dll assembly which has not
previously been supported or shipped.

System.Drawing.Primitives.dll contains System.Drawing.Point and
related typees, which Xamarin.Android places into Mono.Android.dll.

Add a new System.Drawing.Primitives.dll assembly to use as a
facade assembly, which contains type forwarders to
"redirect" the types from System.Drawing.Primitives.dll to the
corresponding types within Mono.Android.dll.

@jonpryor jonpryor force-pushed the jonp-system.drawing.primitives branch 2 times, most recently from 5452886 to 78d6fc6 Compare July 15, 2016 19:40
Xamarin.Android needs to support [.NET Standard 1.6][0], which
mentions a [`System.Drawing.Primitives.dll` assembly][1] which has not
previously been supported or shipped.

`System.Drawing.Primitives.dll` contains `System.Drawing.Point` and
related typees, which Xamarin.Android places into `Mono.Android.dll`.

Add a new `System.Drawing.Primitives.dll` assembly to use as a
*facade assembly*, which contains [type forwarders][2] to
"redirect" the types from `System.Drawing.Primitives.dll` to the
corresponding types within `Mono.Android.dll`.

[0]: https://docs.microsoft.com/en-us/dotnet/articles/core/tutorials/libraries
[1]: https://github.com/dotnet/corefx/blob/master/Documentation/architecture/net-platform-standard.md#list-of-net-corefx-apis-and-their-associated-net-platform-standard-version
[2]: https://msdn.microsoft.com/en-us/library/ms404275(v=vs.110).aspx
@jonpryor jonpryor force-pushed the jonp-system.drawing.primitives branch from 78d6fc6 to 3e8e952 Compare July 15, 2016 20:33
@radical
Copy link
Member

radical commented Jul 15, 2016

LGTM!

@jonpryor jonpryor merged commit f48e555 into dotnet:master Jul 15, 2016
</ItemGroup>
<ItemGroup>
<Compile Include="$(MonoSourceFullPath)\mcs\class\Facades\System.Drawing.Primitives\AssemblyInfo.cs" />
<Compile Include="Properties\AssemblyInfo.cs" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could include $(MonoSourceFullPath)\mcs\class\Facades\System.Drawing.Primitives\TypeForwarders.cs instead of duplicating the forwarders in that file.

radical pushed a commit that referenced this pull request May 8, 2018
This is a fixup for c51469e, as well as bugfix for:
https://bugzilla.xamarin.com/show_bug.cgi?id=51337

What's happening behind bug #51337 was this:

	BINDINGSGENERATOR:  warning BG8800: Unknown parameter
	type org.osmdroid.ResourceProxy.bitmap in method GetBitmap
	in managed type OsmDroid.DefaultResourceProxyImpl.

This was, because, "bitmap" is all lowercased and was marked as obfuscated
(because, WHY NAME A CLASS ALL IN LOWERCASE!?).

Such classes should not exist, or should be marked as "obfuscated='false'".

However what bug #51337 implies is that people are not going to make
this additional markup for generator improvements.

What this generator change does is then - a hack. A hack to mark "classes
with very short names" as obfuscated, instead of "all lowercase or number".

As commented on c51469e, there isn't good way to check API element
siblings (it can check sibling names every time at all expensive
calculation). So we just count the sibling nodes and if name length is
short enough to fit within the number of classes, we mark as obfucated.

As some post-first-commit thought, the name check is done only for
very short names i.e. only those within 3 letters.

Also, the new proguard in Gradle task seems to obfuscates the names as
"zzXXXXX" . They should be marked as obfuscated too.
jonpryor added a commit to jonpryor/xamarin-android that referenced this pull request Jun 4, 2021
Fixes: dotnet#5432
Fixes: dotnet#5992

Changes: dotnet/android-tools@683f375...90d7621

  * dotnet/android-tools@90d7621: [BaseTasks] add ABI detection for RIDs (dotnet#121)
  * dotnet/android-tools@79e3b97: [JdkInfo] handle invalid XML from /usr/libexec/java_home (dotnet#120)
  * dotnet/android-tools@81519fe: Add SECURITY.md (dotnet#119)
jonpryor added a commit to jonpryor/xamarin-android that referenced this pull request Jun 4, 2021
Fixes: dotnet#5432
Fixes: dotnet#5992

Changes: dotnet/android-tools@683f375...90d7621

  * dotnet/android-tools@90d7621: [BaseTasks] add ABI detection for RIDs (dotnet#121)
  * dotnet/android-tools@79e3b97: [JdkInfo] handle invalid XML from /usr/libexec/java_home (dotnet#120)
  * dotnet/android-tools@81519fe: Add SECURITY.md (dotnet#119)
jonpryor pushed a commit that referenced this pull request Jun 10, 2021
Changes: xamarin/monodroid@76c04cd...1f2ce15

  * xamarin/monodroid@1f2ce1562: [tools/msbuild] only run _GetPrimaryCpuAbi for Fast Dev (#1208)
  * xamarin/monodroid@691310ede: Bump android-sdk-installer to use Mono.Unix (#1207)
  * xamarin/monodroid@48843fcb2: [tools/msbuild] <GetPrimaryCpuAbi/> selects backup RIDs for .NET 6 (#1205)
  * xamarin/monodroid@4af48f54b: [tools/fastdev] Add error checking when writing data to disk. (#1204)
  * xamarin/monodroid@65b7b2dd4: [tools/fastdev] Rework Unix timestamp calculation code in xamarin.find. (#1202)
  * xamarin/monodroid@401f170e9: [build] fix `dotnet tool install` command (#1203)
  * xamarin/monodroid@a879b250b: Bump to 032d840, xamarin/androidtools@355d015 (#1199)
  * xamarin/monodroid@9f9ee378c: [tools/msbuild] Missing translations for XA0135 (#1198)

Changes: dotnet/android-tools@683f375...49936d6

  * dotnet/android-tools@49936d6: Merge pull request #124 from xamarin/update-libzipsharp
  * dotnet/android-tools@ef78dfc: Bump LibZipSharp to 2.0.0-alpha6
  * dotnet/android-tools@e3d708c: [BaseTasks] fix `\`-delimited paths on macOS (#122)
  * dotnet/android-tools@bdcf899: Reference the new Mono.Unix nuget (#123)
  * dotnet/android-tools@90d7621: [BaseTasks] add ABI detection for RIDs (#121)
  * dotnet/android-tools@79e3b97: [JdkInfo] handle invalid XML from /usr/libexec/java_home (#120)
  * dotnet/android-tools@81519fe: Add SECURITY.md (#119)


Xamarin.Android uses the Mono's Mono.Posix assembly on Unix machines
to perform tasks not possible with BCL classes, provided by the
[`Mono.Posix.NETStandard` NuGet][0].  The `Mono.Posix` source has been
extracted into the [mono/mono.posix repo][1], which is used to build
the new [`Mono.Unix` NuGet package][2].

Update the xamarin/xamarin-android repo -- and various dependencies --
to use the `Mono.Unix` package instead of `Mono.Posix.NETStandard`.
This includes the [`Xamarin.LibZipSharp` NuGet][3], as of
dotnet/android-libzipsharp@cf5e33c6.

`Mono.Unix` no longer uses the older `libMonoPosixHelper` dynamic
library, replaced by a new `libMono.Unix` native library.
Unfortunately, this change broke a number of tests since the
`Mono.Unix.dll` assembly was no longer able to find its companion
native shared library.  While the `Mono.Posix.NETStandard` NuGet
package provides the `libMonoPosixHelper` native library, in practice
the *actual* `libMonoPosixHelper` that was used was the "system"
library included with the system mono.

`Mono.Unix`'s new native helper library, however, must be taken from
the NuGet and both the Mono and dotnet runtimes must be told where to
load the library from once a P/Invoke into `Mono.Unix` is encountered
in managed code.  The native library is copied from the NuGet to the
referencing application's output directory and it should be loaded from
there.  This proved to be easy for the "legacy" Mono: a simple
[`dllmap` configuration][4] and everything works as it should.

With `dotnet` however, dllmap doesn't work.  `dotnet` has instead a
number of mechanisms to configure where the native libraries can be
found (5 I think).  Unfortunately, the mechanisms either require that
a main executable of the application calls the APIs on entry (e.g. in
the `Main()` method) or that a JSON configuration file is provided for
the application, telling the runtime where the native libraries reside.
In case of `Xamarin.Android.Build.Tasks` there is no main executable we
can configure, since it works in the MSBuild context, providing tasks
and utilities to build Xamarin.Android apps.  In this instance, `dotnet`
could be persuaded to find the libraries by calling one of the 5 APIs.
The problem with this approach, however, is that this action would have
to be performed at **every** possible entry point to the
`Xamarin.Android.Build.Tasks` assembly, since any of them could be used
as the first one.  While certainly possible, it would be both fragile
and an unnecessary maintenance burden.  Instead, a simpler (albeit a
bit kludgy) solution was chosen: the `src/Xamarin.Android.Build.Tasks`
build process now takes care of generating a fat (multi-architecture)
binary for macOS hosts (including `x86-64` and `arm64` architectures)
using the `lipo` utility, then it copies the resulting binary to the
same directory where `Xamarin.Android.Build.Tasks.dll` and
`Mono.Unix.dll` live.  The Linux shared library is also copied to the
same location.  The `dotnet` runtime is able to find and load shared
libraries that are in the same directory as the assembly that needs
them and everything works as expected.

[0]: https://www.nuget.org/packages/Mono.Posix.NETStandard/5.20.1-preview
[1]: https://github.com/mono/mono.posix
[2]: https://www.nuget.org/packages/Mono.Unix/
[3]: https://www.nuget.org/packages/Xamarin.LibZipSharp
[4]: https://www.mono-project.com/docs/advanced/pinvoke/dllmap/
@github-actions github-actions bot locked and limited conversation to collaborators Feb 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants