xamarin
/
xamarin-macios
зеркало из
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
xamarin-macios/tests/test-libraries/Makefile

221 строка
9.2 KiB
Makefile
Исходник Обычный вид История

Make logic not depend on the checkout directory being named 'xamarin-macios'. (#129)
2016-06-06 13:18:52 +03:00
TOP=../..
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
include $(TOP)/Make.config
# without this many compiler warnings about unused functions and variables
# in system headers show up.
export CCACHE_CPP2=1
[tests] Generate some trampoline and registrar tests. Generate trampoline and registrar tests that tests if a return type requires objc_msgSend or objc_msgSend_stret. Now it's much easier to test new return types (a single line of code), which avoids a _lot_ of copy-pasting, and makes sure all the different variations are tested properly. These new tests found several bugs, which are fixed in subsequent commits.
2016-10-07 13:48:01 +03:00
GENERATED_FILES = \
libtest.structs.h \
libtest.decompile.m \
libtest.properties.h \
../bindings-test/ApiDefinition.generated.cs \
../bindings-test/StructsAndEnums.generated.cs \
[monotouch-test] Move generated files out of the "all test files" wildcard. (#2958) monotouch-test has a wildcard to automatically include new test files, but this should not include generated files, because: * The generated files are generated when needed, which means we can't rely on the wildcard to trigger their generation, because the wildcard won't find them before they exist, and as such msbuild won't detect that they're needed. * This means the generated files must be listed separately, but in that case they shouldn't be found by the wildcard too, because that leads to: /Library/Frameworks/Mono.framework/Versions/5.4.0/lib/mono/msbuild/15.0/bin/Roslyn/Microsoft.CSharp.Core.targets(84,5): error MSB3105: The item "ObjCRuntime/TrampolineTest.generated.cs" was specified more than once in the "Sources" parameter. Duplicate items are not supported by the "Sources" parameter. So move the generated files to a different directory, so that the wildcard doesn't find them.
2017-11-06 19:16:32 +03:00
RegistrarTest.generated.cs \
TrampolineTest.generated.cs \
[tests] Generate some trampoline and registrar tests. Generate trampoline and registrar tests that tests if a return type requires objc_msgSend or objc_msgSend_stret. Now it's much easier to test new return types (a single line of code), which avoids a _lot_ of copy-pasting, and makes sure all the different variations are tested properly. These new tests found several bugs, which are fixed in subsequent commits.
2016-10-07 13:48:01 +03:00
GENERATED_FILES_PATTERN = \
libtest.structs%h \
libtest.decompile%m \
libtest.properties%h \
../bindings-test/ApiDefinition.generated%cs \
../bindings-test/StructsAndEnums.generated%cs \
[monotouch-test] Move generated files out of the "all test files" wildcard. (#2958) monotouch-test has a wildcard to automatically include new test files, but this should not include generated files, because: * The generated files are generated when needed, which means we can't rely on the wildcard to trigger their generation, because the wildcard won't find them before they exist, and as such msbuild won't detect that they're needed. * This means the generated files must be listed separately, but in that case they shouldn't be found by the wildcard too, because that leads to: /Library/Frameworks/Mono.framework/Versions/5.4.0/lib/mono/msbuild/15.0/bin/Roslyn/Microsoft.CSharp.Core.targets(84,5): error MSB3105: The item "ObjCRuntime/TrampolineTest.generated.cs" was specified more than once in the "Sources" parameter. Duplicate items are not supported by the "Sources" parameter. So move the generated files to a different directory, so that the wildcard doesn't find them.
2017-11-06 19:16:32 +03:00
RegistrarTest.generated%cs \
TrampolineTest.generated%cs \
[tests] Generate some trampoline and registrar tests. Generate trampoline and registrar tests that tests if a return type requires objc_msgSend or objc_msgSend_stret. Now it's much easier to test new return types (a single line of code), which avoids a _lot_ of copy-pasting, and makes sure all the different variations are tested properly. These new tests found several bugs, which are fixed in subsequent commits.
2016-10-07 13:48:01 +03:00
testgenerator.exe: testgenerator.cs Makefile
$(Q) mcs -out:$@ $<
$(GENERATED_FILES_PATTERN): testgenerator.exe
$(Q) mono --debug $<
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
libtest-object.m libtest-ar.m:
$(Q) ln -fhs libtest.m $@
define Template
$(2)_TARGETS = \
.libs/$(1)/XTest.framework/XTest \
.libs/$(1)/XTest.framework/Info.plist \
.libs/$(1)/XStaticObjectTest.framework/XStaticObjectTest \
.libs/$(1)/XStaticArTest.framework/XStaticArTest \
.libs/$(1)/libtest.dylib \
[tests] Add test for bug #43689.
2017-01-26 15:38:39 +03:00
.libs/$(1)/libtest2.a \
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
.libs/$(1)/libtest.a \
.libs/$(1)/libtest-object.a \
.libs/$(1)/libtest-ar.a \
$$(foreach arch,$(3),.libs/$(1)/libtest.$$(arch).a) \
$$(foreach arch,$(3),.libs/$(1)/libtest-object.$$(arch).a) \
$$(foreach arch,$(3),.libs/$(1)/libtest-ar.$$(arch).a) \
.libs/$(1)/XTest.framework \
[tests] Generate some trampoline and registrar tests. Generate trampoline and registrar tests that tests if a return type requires objc_msgSend or objc_msgSend_stret. Now it's much easier to test new return types (a single line of code), which avoids a _lot_ of copy-pasting, and makes sure all the different variations are tested properly. These new tests found several bugs, which are fixed in subsequent commits.
2016-10-07 13:48:01 +03:00
all-local:: $$($(2)_TARGETS) $(GENERATED_FILES)
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
clean-$(1):
rm -Rf .libs/$(1)
CLEAN_TARGETS += clean-$(1)
Optimize calls to BlockLiteral.SetupBlock to inject the block signature. (#3391) * [linker] Optimize calls to BlockLiteral.SetupBlock to inject the block signature. Optimize calls to BlockLiteral.SetupBlock[Unsafe] to calculate the block signature at build time, and inject it into the call site. This makes block invocations 10-15x faster (I've added tests that asserts at least an 8x increase). It's also required in order to be able to remove the dynamic registrar code in the future (since calculating the block signature at runtime requires the dynamic registrar). * [mtouch/mmp] Add support for reporting errors/warnings that point to the code line causing the error/warning. Add support for reporting errors/warnings that point to the code line causing the error/warning by adding ErrorHelper overloads that take the exact instruction to report (previously we defaulted to the first line/instruction in a method). * [tests] Add support for asserting filename/linenumber in warning messages. * Make all methods that manually create BlockLiterals optimizable. * [tests] Create a BaseOptimizeGeneratedCodeTest test that's included in both XI's and XM's link all test. * [tests] Add link all test (for both XI and XM) to test the BlockLiteral.SetupBlock optimization. * [tests] Add mtouch/mmp tests for the BlockLiteral.SetupBlock optimization. * [tests][linker] Make the base test class abstract, so tests in the base class aren't executed twice. * [tests][linker] Don't execute linkall-only tests in linksdk. The optimization tests only apply when the test assembly is linked, and that only happens in linkall, so exclude those tests in linksdk. * [tests][mmptest] Update test according to mmp changes. Fixes these test failures: 1) Failed : Xamarin.MMP.Tests.MMPTests.MM0132("inline-runtime-arch") The warning 'MM0132: Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' was not found in the output: Message #1 did not match: actual: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' Message #2 did not match: actual: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'inline-runtime-arch'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' 2) Failed : Xamarin.MMP.Tests.MMPTests.MM0132("foo") The warning 'MM0132: Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' was not found in the output: Message #1 did not match: actual: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' Message #2 did not match: actual: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size, blockliteral-setupblock.' expected: 'Unknown optimization: 'foo'. Valid optimizations are: remove-uithread-checks, dead-code-elimination, inline-isdirectbinding, inline-intptr-size.' * [tests][linker] Fix typo. Fixes this test failure: 1) SetupBlock_CustomDelegate (Linker.Shared.BaseOptimizeGeneratedCodeTest.SetupBlock_CustomDelegate) Counter Expected: 1 But was: 2 * [registrar] Minor adjustment to error message to match previous (and better) behavior. Fixes this test failure: 1) Failed : Xamarin.Registrar.GenericType_WithInvalidParameterTypes The error 'MT4136: The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<U>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' was not found in the output: Message #1 did not match: actual: 'The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<Foundation.NSObject>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' expected: 'The registrar cannot marshal the parameter type 'System.Collections.Generic.List`1<U>' of the parameter 'arg' in the method 'Open`1.Bar(System.Collections.Generic.List`1<U>)'' * [docs] mmp shows MM errors/warnings. * [docs] Improve according to reviews. * [tests] Fix merge failure causing test duplication.
2018-02-06 09:08:15 +03:00
EXTRA_DEPENDENCIES = libtest.h $(GENERATED_FILES) rename.h
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
.libs/$(1)/libtest-object.%.o: export EXTRA_DEFINES=-DPREFIX=1
.libs/$(1)/libtest-ar.%.o: export EXTRA_DEFINES=-DPREFIX=2
.libs/$(1)/libtest%.a: .libs/$(1)/libtest%.o libtest-object.m libtest-ar.m
$(Q) rm -f $$@
[test-libraries] Don't include all the dependencies in the ar archives we create. (#9167) We only want the *.o files in the *.a archives, not the source files (*.m files).
2020-07-23 16:37:39 +03:00
$$(call Q_2,AR [$(1)]) $(XCODE_DEVELOPER_ROOT)/Toolchains/XcodeDefault.xctoolchain/usr/bin/ar cru $$@ $$<
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
[mtouch] Make sure native symbols from third-party libraries are preserved in dylibs. Fixes #51548. The native linker treats object files (.o) and static libraries (.a files, which are archives of .o files) differently. The native linker will always include object files into the executable: $ echo "void xxx () {}" > foo.m $ clang -c foo.m -o foo.o -arch x86_64 $ ld foo.o -dylib -o foo.dylib -macosx_version_min 10.12 -arch x86_64 $ nm foo.dylib 0000000000000fe0 T _xxx However, if the object file is inside a static library: $ echo "void xxx () {}" > foo.m $ clang -c foo.m -o foo.o -arch x86_64 $ ar cru foo.a foo.o $ ld foo.a -dylib -o foo.dylib -macosx_version_min 10.12 -arch x86_64 $ nm foo.dylib <no output> This means that our testing library (libtest.a) which is a fat library of _object files_, do not show the problems reported in bug #51548. So: a) I've fixed the creation of libtest.a to be a fat library of _static libraries_. This causes the `FastDev_LinkWithTest` test to fail exactly like in bug #51548. b) I've made mtouch pass `-u <native symbol>` to the native linker, for every native symbol referenced in a managed assembly, when creating a dylib. Amazingly this seems to work fine even with symbols to Objective-C classes (`_OBJC_CLASS_$_<class name>`). c) This also required adding support for collecting the Objective-C names of all managed types registered with Objective-C to the linker. The information is already available in the static registrar, but that would require us to make sure the static registrar is executed before compiling dylibs, which means those two tasks won't be able to run in parallel (also there's no guarantee we'll even run the static registrar). https://bugzilla.xamarin.com/show_bug.cgi?id=51548
2017-01-18 12:25:58 +03:00
.libs/$(1)/libtest.a: $$(foreach arch,$(3),.libs/$(1)/libtest.$$(arch).a)
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
$(Q) rm -f $$@
$$(call Q_2,LIPO [$(1)]) $(XCODE_DEVELOPER_ROOT)/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo $$^ -create -output $$@
[tests] Add test for bug #43689.
2017-01-26 15:38:39 +03:00
.libs/$(1)/libtest2.a: $$(foreach arch,$(3),.libs/$(1)/libtest2.$$(arch).a)
$(Q) rm -f $$@
$$(call Q_2,LIPO [$(1)]) $(XCODE_DEVELOPER_ROOT)/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo $$^ -create -output $$@
[mtouch] Make sure native symbols from third-party libraries are preserved in dylibs. Fixes #51548. The native linker treats object files (.o) and static libraries (.a files, which are archives of .o files) differently. The native linker will always include object files into the executable: $ echo "void xxx () {}" > foo.m $ clang -c foo.m -o foo.o -arch x86_64 $ ld foo.o -dylib -o foo.dylib -macosx_version_min 10.12 -arch x86_64 $ nm foo.dylib 0000000000000fe0 T _xxx However, if the object file is inside a static library: $ echo "void xxx () {}" > foo.m $ clang -c foo.m -o foo.o -arch x86_64 $ ar cru foo.a foo.o $ ld foo.a -dylib -o foo.dylib -macosx_version_min 10.12 -arch x86_64 $ nm foo.dylib <no output> This means that our testing library (libtest.a) which is a fat library of _object files_, do not show the problems reported in bug #51548. So: a) I've fixed the creation of libtest.a to be a fat library of _static libraries_. This causes the `FastDev_LinkWithTest` test to fail exactly like in bug #51548. b) I've made mtouch pass `-u <native symbol>` to the native linker, for every native symbol referenced in a managed assembly, when creating a dylib. Amazingly this seems to work fine even with symbols to Objective-C classes (`_OBJC_CLASS_$_<class name>`). c) This also required adding support for collecting the Objective-C names of all managed types registered with Objective-C to the linker. The information is already available in the static registrar, but that would require us to make sure the static registrar is executed before compiling dylibs, which means those two tasks won't be able to run in parallel (also there's no guarantee we'll even run the static registrar). https://bugzilla.xamarin.com/show_bug.cgi?id=51548
2017-01-18 12:25:58 +03:00
.libs/$(1)/libtest-object.a: $$(foreach arch,$(3),.libs/$(1)/libtest-object.$$(arch).a)
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
$(Q) rm -f $$@
$$(call Q_2,LIPO [$(1)]) $(XCODE_DEVELOPER_ROOT)/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo $$^ -create -output $$@
[mtouch] Make sure native symbols from third-party libraries are preserved in dylibs. Fixes #51548. The native linker treats object files (.o) and static libraries (.a files, which are archives of .o files) differently. The native linker will always include object files into the executable: $ echo "void xxx () {}" > foo.m $ clang -c foo.m -o foo.o -arch x86_64 $ ld foo.o -dylib -o foo.dylib -macosx_version_min 10.12 -arch x86_64 $ nm foo.dylib 0000000000000fe0 T _xxx However, if the object file is inside a static library: $ echo "void xxx () {}" > foo.m $ clang -c foo.m -o foo.o -arch x86_64 $ ar cru foo.a foo.o $ ld foo.a -dylib -o foo.dylib -macosx_version_min 10.12 -arch x86_64 $ nm foo.dylib <no output> This means that our testing library (libtest.a) which is a fat library of _object files_, do not show the problems reported in bug #51548. So: a) I've fixed the creation of libtest.a to be a fat library of _static libraries_. This causes the `FastDev_LinkWithTest` test to fail exactly like in bug #51548. b) I've made mtouch pass `-u <native symbol>` to the native linker, for every native symbol referenced in a managed assembly, when creating a dylib. Amazingly this seems to work fine even with symbols to Objective-C classes (`_OBJC_CLASS_$_<class name>`). c) This also required adding support for collecting the Objective-C names of all managed types registered with Objective-C to the linker. The information is already available in the static registrar, but that would require us to make sure the static registrar is executed before compiling dylibs, which means those two tasks won't be able to run in parallel (also there's no guarantee we'll even run the static registrar). https://bugzilla.xamarin.com/show_bug.cgi?id=51548
2017-01-18 12:25:58 +03:00
.libs/$(1)/libtest-ar.a: $$(foreach arch,$(3),.libs/$(1)/libtest-ar.$$(arch).a)
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
$(Q) rm -f $$@
$$(call Q_2,LIPO [$(1)]) $(XCODE_DEVELOPER_ROOT)/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo $$^ -create -output $$@
COMMON_DYLIB_ARGS=-g -dynamiclib -gdwarf-2 -fms-extensions libframework.m -o $$@ -Wall -framework Foundation -lz
Make makefiles compatible with make 4.3. (#8573) In make 4.3 the pattern `.libs/watchos/%.arm64_32.dylib` in mk/rules.mk takes precedence over the pattern `.libs/watchos/libtest.%.dylib` in tests/test-libraries/Makefile when the pattern replacements are 'libtest' and 'arm64_32' respectively, because the former is shorter. This seems to be a bug (in make 3.81) that has been fixed, because that's the documented behavior. Rewrite the logic to not use a pattern target in test/test-libraries/Makefile.
2020-05-12 17:38:05 +03:00
.libs/$(1)/libtest.x86.dylib: ARCH=i386
$$(foreach arch,$(3),.libs/$(1)/libtest.$$(arch).dylib): libframework.m | .libs/$(1)
$$(call Q_2,CC, [$(1)]) $$(XCODE_CC) $$(COMMON_DYLIB_ARGS) -arch $$(if $$(ARCH),i386,$$(subst libtest.,,$$(basename $$(notdir $$@)))) $(5) -isysroot $(XCODE_DEVELOPER_ROOT)/Platforms/$(4).platform/Developer/SDKs/$(4)$$($(6)_SDK_VERSION).sdk
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
$$(Q) $(XCODE_DEVELOPER_ROOT)/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool -id @rpath/XTest.framework/XTest $$@
[runtime] Split the build differently: build libraries for simulator and device separately. (#7143) This has a couple of advantages: * It makes it easier to add a catalyst version of these libraries (because it becomes cumbersome to build for catalyst when the build rules assumes we're building for both simulator and device). * It makes it easier to create an xcframework of our libraries, because the contents in an xcframework is split like this.
2019-10-03 17:38:44 +03:00
.libs/$(1)/libtest.dylib: $$(foreach arch,$(3),.libs/$(1)/libtest.$$(arch).dylib)
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
$$(call Q_2,LIPO [$(1)]) $(XCODE_DEVELOPER_ROOT)/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo $$^ -create -output $$@
# XTest is a framework where the binary code is a (fat) dynamic library
.libs/$(1)/XTest.framework/XTest: .libs/$(1)/libtest.dylib | .libs/$(1)/XTest.framework
Clone files if possible whenever it makes sense. (#5049) Cloning is faster when supported, and it also saves disk space.
2018-10-29 18:09:30 +03:00
$$(Q) $(CP) $$^ $$@
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
.libs/$(1)/XTest.framework/Info.plist: XTest-Info.plist | .libs/$(1)/XTest.framework
Clone files if possible whenever it makes sense. (#5049) Cloning is faster when supported, and it also saves disk space.
2018-10-29 18:09:30 +03:00
$$(Q) $(CP) $$^ $$@
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
# XStaticObjectTest is a framework where the binary code is a (fat) object file
.libs/$(1)/XStaticObjectTest.framework/XStaticObjectTest: $$(foreach arch,$(3),.libs/$(1)/libtest-object.$$(arch).o) | .libs/$(1)/XStaticObjectTest.framework
$(Q) rm -f $$@
$$(call Q_2,LIPO [$(1)]) $(XCODE_DEVELOPER_ROOT)/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo $$^ -create -output $$@
# XStaticArTest is a framework where the binary code is a (fat) ar archive (of object files)
.libs/$(1)/XStaticArTest.framework/XStaticArTest: $$(foreach arch,$(3),.libs/$(1)/libtest-ar.$$(arch).a) | .libs/$(1)/XStaticArTest.framework
$(Q) rm -f $$@
$$(call Q_2,LIPO [$(1)]) $(XCODE_DEVELOPER_ROOT)/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo $$^ -create -output $$@
.libs/$(1)/XTest.framework .libs/$(1)/XStaticObjectTest.framework .libs/$(1)/XStaticArTest.framework:
$$(Q) mkdir -p $$@
endef
[runtime] Split the build differently: build libraries for simulator and device separately. (#7143) This has a couple of advantages: * It makes it easier to add a catalyst version of these libraries (because it becomes cumbersome to build for catalyst when the build rules assumes we're building for both simulator and device). * It makes it easier to create an xcframework of our libraries, because the contents in an xcframework is split like this.
2019-10-03 17:38:44 +03:00
# 1: platform infix
# 2: platform variable
# 3: architectures
# 4: platform name
# 5: min version
# 6: os
$(eval $(call Template,iphonesimulator,IOSSIMULATOR,x86 x86_64,iPhoneSimulator,-mios-simulator-version-min=8.0,IOS))
$(eval $(call Template,iphoneos,IPHONEOS,armv7 armv7s arm64,iPhoneOS,-miphoneos-version-min=8.0,IOS))
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
ifdef INCLUDE_TVOS
[runtime] Split the build differently: build libraries for simulator and device separately. (#7143) This has a couple of advantages: * It makes it easier to add a catalyst version of these libraries (because it becomes cumbersome to build for catalyst when the build rules assumes we're building for both simulator and device). * It makes it easier to create an xcframework of our libraries, because the contents in an xcframework is split like this.
2019-10-03 17:38:44 +03:00
$(eval $(call Template,tvsimulator,TVSIMULATOR,x86_64,AppleTVSimulator,-mtvos-simulator-version-min=9.0,TVOS))
$(eval $(call Template,tvos,TVOS,arm64,AppleTVOS,-mtvos-version-min=9.0 -fembed-bitcode,TVOS))
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
endif
ifdef INCLUDE_WATCH
[main][watchOS] Add x86_64 simulator support (#10059) * [watchOS] Add x86_64 simulator support * Build runtime/registrar x86_64 slices * Produce a 64 bit version of Xamarin.WatchOS.dll * Allow building x86_64 for watch simulators in mtouch * Let xharness know about x86_64 * [tests] Add x86_64 arch to test-libraries * Make dotnet package aware of x64 * [ObjCRuntime] Fix computing if we're calling a stret function or not in a 64-bit watchOS simulator. * [xharness] Re-enable some watchOS tests. Co-authored-by: Rolf Bjarne Kvinge <rolf@xamarin.com>
2020-11-20 17:27:46 +03:00
$(eval $(call Template,watchsimulator,WATCHSIMULATOR,x86 x86_64,WatchSimulator,-mwatchos-simulator-version-min=2.0,WATCHOS))
[runtime] Split the build differently: build libraries for simulator and device separately. (#7143) This has a couple of advantages: * It makes it easier to add a catalyst version of these libraries (because it becomes cumbersome to build for catalyst when the build rules assumes we're building for both simulator and device). * It makes it easier to create an xcframework of our libraries, because the contents in an xcframework is split like this.
2019-10-03 17:38:44 +03:00
$(eval $(call Template,watchos,WATCHOS,armv7k arm64_32,WatchOS,-mwatchos-version-min=2.0 -fembed-bitcode,WATCHOS))
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
endif
[tests] Build the native test library for macOS and create a binding project for it. (#3373) * [tests] Build the native test library for macOS and create a binding project for it. Also add the new binding project to the xammac and link all XM test projects, which allows us to stop excluding tests that require the native library and the corresponding bindings. * [tests] Include more tests in xammac_tests. * [tests] Correctly ignore the ObjC exception tests in release mode.
2018-02-02 13:14:44 +03:00
ifdef INCLUDE_MAC
[runtime] Split the build differently: build libraries for simulator and device separately. (#7143) This has a couple of advantages: * It makes it easier to add a catalyst version of these libraries (because it becomes cumbersome to build for catalyst when the build rules assumes we're building for both simulator and device). * It makes it easier to create an xcframework of our libraries, because the contents in an xcframework is split like this.
2019-10-03 17:38:44 +03:00
$(eval $(call Template,macos,MACOS,x86_64,MacOSX,-mmacosx-version-min=$(MIN_OSX_VERSION_FOR_MAC),MACOS,x86_64))
[tests] Build the native test library for macOS and create a binding project for it. (#3373) * [tests] Build the native test library for macOS and create a binding project for it. Also add the new binding project to the xammac and link all XM test projects, which allows us to stop excluding tests that require the native library and the corresponding bindings. * [tests] Include more tests in xammac_tests. * [tests] Correctly ignore the ObjC exception tests in release mode.
2018-02-02 13:14:44 +03:00
endif
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
[runtime] Split the build differently: build libraries for simulator and device separately. (#7143) This has a couple of advantages: * It makes it easier to add a catalyst version of these libraries (because it becomes cumbersome to build for catalyst when the build rules assumes we're building for both simulator and device). * It makes it easier to create an xcframework of our libraries, because the contents in an xcframework is split like this.
2019-10-03 17:38:44 +03:00
.libs/ios-fat .libs/tvos-fat .libs/watchos-fat:
$(Q) mkdir -p $@
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
[runtime] Split the build differently: build libraries for simulator and device separately. (#7143) This has a couple of advantages: * It makes it easier to add a catalyst version of these libraries (because it becomes cumbersome to build for catalyst when the build rules assumes we're building for both simulator and device). * It makes it easier to create an xcframework of our libraries, because the contents in an xcframework is split like this.
2019-10-03 17:38:44 +03:00
define LibTemplate
.libs/$(4)/libtest.$(1).a: $(2) $(3) | .libs/$(4)
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
@rm -f $$@
$$(Q_LIPO) $(XCODE_DEVELOPER_ROOT)/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo $$^ -create -output $$@
$(5)_TARGETS += .libs/$(4)/libtest.$(1).a
[runtime] Split the build differently: build libraries for simulator and device separately. (#7143) This has a couple of advantages: * It makes it easier to add a catalyst version of these libraries (because it becomes cumbersome to build for catalyst when the build rules assumes we're building for both simulator and device). * It makes it easier to create an xcframework of our libraries, because the contents in an xcframework is split like this.
2019-10-03 17:38:44 +03:00
all-local:: $$($(5)_TARGETS)
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
endef
[runtime] Split the build differently: build libraries for simulator and device separately. (#7143) This has a couple of advantages: * It makes it easier to add a catalyst version of these libraries (because it becomes cumbersome to build for catalyst when the build rules assumes we're building for both simulator and device). * It makes it easier to create an xcframework of our libraries, because the contents in an xcframework is split like this.
2019-10-03 17:38:44 +03:00
$(eval $(call LibTemplate,armv7+7s,.libs/iphoneos/libtest.armv7.o,.libs/iphoneos/libtest.armv7s.o,ios-fat,IOS))
$(eval $(call LibTemplate,armv7+x86,.libs/iphoneos/libtest.armv7.o,.libs/iphonesimulator/libtest.x86.o,ios-fat,IOS))
$(eval $(call LibTemplate,armv7s+x86,.libs/iphoneos/libtest.armv7s.o,.libs/iphonesimulator/libtest.x86.o,ios-fat,IOS))
$(eval $(call LibTemplate,arm64+x86_64,.libs/tvos/libtest.arm64.o,.libs/tvsimulator/libtest.x86_64.o,tvos-fat,TVOS))
$(eval $(call LibTemplate,armv7k+x86,.libs/watchos/libtest.armv7k.o,.libs/watchsimulator/libtest.x86.o,watchos-fat,WATCHOS))
define FatFrameworkTemplate
.libs/$(1)/XStaticObjectTest.framework/XStaticObjectTest: .libs/$(2)/XStaticObjectTest.framework/XStaticObjectTest .libs/$(3)/XStaticObjectTest.framework/XStaticObjectTest | .libs/$(1)
$(Q) mkdir -p $$(dir $$@)
$(Q) lipo -create -output $$@ $$^
.libs/$(1)/XStaticArTest.framework/XStaticArTest: .libs/$(2)/XStaticArTest.framework/XStaticArTest .libs/$(3)/XStaticArTest.framework/XStaticArTest | .libs/$(1)
$(Q) mkdir -p $$(dir $$@)
$(Q) lipo -create -output $$@ $$^
.libs/$(1)/XTest.framework/XTest: .libs/$(2)/XTest.framework/XTest .libs/$(3)/XTest.framework/XTest | .libs/$(1)
$(Q) mkdir -p $$(dir $$@)
$(Q) lipo -create -output $$@ $$^
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
[runtime] Split the build differently: build libraries for simulator and device separately. (#7143) This has a couple of advantages: * It makes it easier to add a catalyst version of these libraries (because it becomes cumbersome to build for catalyst when the build rules assumes we're building for both simulator and device). * It makes it easier to create an xcframework of our libraries, because the contents in an xcframework is split like this.
2019-10-03 17:38:44 +03:00
.libs/$(1)/XTest.framework/Info.plist: .libs/$(2)/XTest.framework/Info.plist .libs/$(3)/XTest.framework/Info.plist
$(Q) mkdir -p $$(dir $$@)
@# Check if the Info.plists are identical
$(Q) diff $$^
@# Copy one of them
$(Q) $(CP) $$< $$@
.libs/$(1)/libtest.a: .libs/$(2)/libtest.a .libs/$(3)/libtest.a | .libs/$(1)
$(Q) lipo -create -output $$@ $$^
.libs/$(1)/libtest2.a: .libs/$(2)/libtest2.a .libs/$(3)/libtest2.a | .libs/$(1)
$(Q) lipo -create -output $$@ $$^
$(3)_TARGETS += \
.libs/$(1)/XTest.framework/XTest .libs/$(1)/XTest.framework/Info.plist \
.libs/$(1)/XStaticObjectTest.framework/XStaticObjectTest \
.libs/$(1)/XStaticArTest.framework/XStaticArTest \
.libs/$(1)/libtest.a \
.libs/$(1)/libtest2.a \
all-local:: $$($(3)_TARGETS)
endef
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
[runtime] Split the build differently: build libraries for simulator and device separately. (#7143) This has a couple of advantages: * It makes it easier to add a catalyst version of these libraries (because it becomes cumbersome to build for catalyst when the build rules assumes we're building for both simulator and device). * It makes it easier to create an xcframework of our libraries, because the contents in an xcframework is split like this.
2019-10-03 17:38:44 +03:00
$(eval $(call FatFrameworkTemplate,ios-fat,iphoneos,iphonesimulator))
$(eval $(call FatFrameworkTemplate,tvos-fat,tvos,tvsimulator))
$(eval $(call FatFrameworkTemplate,watchos-fat,watchos,watchsimulator))
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
[tests] Build the native test library for macOS and create a binding project for it. (#3373) * [tests] Build the native test library for macOS and create a binding project for it. Also add the new binding project to the xammac and link all XM test projects, which allows us to stop excluding tests that require the native library and the corresponding bindings. * [tests] Include more tests in xammac_tests. * [tests] Correctly ignore the ObjC exception tests in release mode.
2018-02-02 13:14:44 +03:00
# Xamarin.Mac
MAC_CLANG = DEVELOPER_DIR=$(XCODE_DEVELOPER_ROOT) $(MAC_CC)
MAC_OBJC_CFLAGS=-ObjC++ -std=c++0x -fno-exceptions
MAC_CFLAGS = -mmacosx-version-min=$(MIN_OSX_SDK_VERSION) -Wall -DMONOMAC -g
MAC_LDFLAGS = -mmacosx-version-min=$(MIN_OSX_SDK_VERSION) -framework AppKit
.libs/macos/libtest.%.o: libtest.m $(EXTRA_DEPENDENCIES) | .libs/macos
$(call Q_2,OBJC, [mac]) $(MAC_CLANG) -arch $* -c $(MAC_OBJC_CFLAGS) $(MAC_CFLAGS) -o $@ $<
.libs/macos/libtest-object.%.o: libtest.m $(EXTRA_DEPENDENCIES) | .libs/macos
$(call Q_2,OBJC, [mac]) $(MAC_CLANG) -arch $* -c $(MAC_OBJC_CFLAGS) $(MAC_CFLAGS) -o $@ $< -DPREFIX=1
.libs/macos/libtest-ar.%.o: libtest.m $(EXTRA_DEPENDENCIES) | .libs/macos
$(call Q_2,OBJC, [mac]) $(MAC_CLANG) -arch $* -c $(MAC_OBJC_CFLAGS) $(MAC_CFLAGS) -o $@ $< -DPREFIX=2
.libs/macos/libtest2.%.o: libtest2.m $(EXTRA_DEPENDENCIES) | .libs/macos
$(call Q_2,OBJC, [mac]) $(MAC_CLANG) -arch $* -c $(MAC_OBJC_CFLAGS) $(MAC_CFLAGS) -o $@ $<
.libs/macos:
$(Q) mkdir -p $@
[tests] Add test-libraries.
2016-04-26 15:00:35 +03:00
clean-local:: $(CLEAN_TARGETS)
include $(TOP)/mk/rules.mk
Make makefiles compatible with make 4.3. (#8573) In make 4.3 the pattern `.libs/watchos/%.arm64_32.dylib` in mk/rules.mk takes precedence over the pattern `.libs/watchos/libtest.%.dylib` in tests/test-libraries/Makefile when the pattern replacements are 'libtest' and 'arm64_32' respectively, because the former is shorter. This seems to be a bug (in make 3.81) that has been fixed, because that's the documented behavior. Rewrite the logic to not use a pattern target in test/test-libraries/Makefile.
2020-05-12 17:38:05 +03:00
.SECONDARY: