xamarin-macios/tests/linker-ios
Rolf Bjarne Kvinge 31df2f4316 [mtouch] Handle non-ascii characters when converting assembly to bitcode assembly. Fixes #56876. (#2141)
When converting strings to a sequence of bytes, we can't just cast chars to
ints, and write that, because non-ascii characters will resulting values
outside the byte range.

Instead explicitly convert the string to a UTF8 byte array, and process that.

https://bugzilla.xamarin.com/show_bug.cgi?id=56876
2017-06-01 17:24:39 +02:00
..
dont link Revert "[linker] Inline BinaryCompatibility.TargetsAtLeast_Desktop_V4_5[_1] (#1518)" 2017-03-14 11:51:08 +01:00
link all [tests][linkall] Make sure the compiler won't remove a field that triggers the inclusion of OpenTK-1.dll. Fixes #54466 (#1961) 2017-04-05 11:52:27 -05:00
link sdk [mtouch] Handle non-ascii characters when converting assembly to bitcode assembly. Fixes #56876. (#2141) 2017-06-01 17:24:39 +02:00
README.md [tests] Move linker tests from maccore (#69) 2016-05-20 14:07:34 -04:00

README.md

Linker Regression Tests

Most of our unit tests follow the default project configuration, which is "Don't Link" for simulator builds and "Link SDK" for device builds.

The linker tests are different as they set both simulator and device configuration to the same settings. This is the main way to test the linker on the simulator (which is the most common test configuration for our bots)

Note that the spaces in the projects directory names are by design as it ensure our tool chain can cope with them.

  • regression testing without using the linker

  • both simulator and devices are set to "Don't link"

  • regression testing using the linker on the all assemblies

  • "Link all assemblies" for both simulator/devices

  • regression testing using the linker on the SDK assemblies

  • "Link SDK assemblies only" for both simulator/devices