mono
/
Embeddinator-4000
зеркало из https://github.com/mono/Embeddinator-4000.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
Embeddinator-4000/objcgen
История
Sebastien Pouliot 1bdeef1dd8 [objc][generator] Use metadata token lookup when building release (#91) 
* [objc][generator] Use metadata token lookup when building release

where release is non-debug.

https://github.com/mono/Embeddinator-4000/issues/82

* [tests] Run test-cli and perf-cli in release (non debug) mode
 		2017-04-11 17:21:54 +02:00
..
.gitignore [objc] Use Mono.Options. (#36) 2017-03-31 13:17:05 -05:00
ErrorHelper.cs [objc] Add support for -o (output directory) and -v (verbosity) and add some error codes (#39) 2017-04-03 09:24:36 -05:00
Make.config Auto-provision Xamarin.iOS and Xamarin.Mac. (#80) 2017-04-07 13:47:26 +02:00
Makefile [objc] Improve Makefile dependencies to only rebuild things if needed. (#76) 2017-04-07 20:05:25 +02:00
README.md [objc][README] Recommend usage of objcgen.exe instead of MonoEmbeddinator4000.exe (#92) 2017-04-11 08:33:38 +02:00
driver.cs [objc][generator] Use metadata token lookup when building release (#91) 2017-04-11 17:21:54 +02:00
error.cs [objc] Add error handling. (#33) 2017-03-31 13:12:12 -05:00
generate-version.sh [objc] Use Mono.Options. (#36) 2017-03-31 13:17:05 -05:00
generator.cs [objc] Initial support for methods (#67) 2017-04-06 08:46:24 -05:00
objcgen.csproj [objc][support] Move MonoString to NSString conversion into it's own routine (to avoid several dupes in generated code) (#94) 2017-04-11 08:35:10 +02:00
objcgenerator.cs [objc][generator] Use metadata token lookup when building release (#91) 2017-04-11 17:21:54 +02:00
packages.config [objc] Use Mono.Options. (#36) 2017-03-31 13:17:05 -05:00
system-dependencies.sh Auto-provision Xamarin.iOS and Xamarin.Mac. (#80) 2017-04-07 13:47:26 +02:00

README.md

ObjC generator

Build

Simply run make in Embeddinator-4000/objcgen.

Run

Don't use MonoEmbeddinator4000.exe.

Use mono ./bin/Debug/objcgen.exe --gen=Obj-C -o ./Output ManagedAssembly1.dll.

Generated API of questionable usability

Whenever we generate a working API that is not optimal (in ObjC) we should update the docs/BestPracticesObjC.md document to explain the situation and provide guidance to get the best ObjC API output.

Missing .NET features

Unimplemented, but planned, features should throw a NotImplementedException with the feature name. The generator will report it as a missing feature that does not require a bug report (and test case).

Unsupported .NET features

Anything that cannot be supported should be added to the docs/Limitations.md document.

The tool should issue warnings (which users can turn into errors) when it cannot generate ObjC to match any given .NET code. The warnings must be added to the docs/errors.md document.