Just passing through though I feel it would be unfortunate if I didn't leave some feedback..
reliance on obsolete ways to locate appropriate android sdk/ndk. I had to resort to putting a registry entry in HKLM/Novell/Mono for Android just to get Embeddinator to recognize that there was an ndk installed as it couldn't find the NDK specified in visual studio or android sdk manager.
Suggestion: allow command line or environmental variables to specify sdk/ndk locations
If the c# DLL has a namespace with the word "Interface" in it, like "a.b.Interface.Generic", the generated code will transform "Interface" to lower case "interface" and will fail complication. e.g. "a.b.interface...."
java compiler failed with "filename or extension too long" error if too many files are generated from the DLL and hits the 32kb command line limit. Suggestion: put the filename in a file and use the @filename parameter for java compiler
Windows 7 powershell is unable to run the build script.
No exception handling in the tool. it just crashes with a stack trace
Just passing through though I feel it would be unfortunate if I didn't leave some feedback..
reliance on obsolete ways to locate appropriate android sdk/ndk. I had to resort to putting a registry entry in HKLM/Novell/Mono for Android just to get Embeddinator to recognize that there was an ndk installed as it couldn't find the NDK specified in visual studio or android sdk manager. Suggestion: allow command line or environmental variables to specify sdk/ndk locations
If the c# DLL has a namespace with the word "Interface" in it, like "a.b.Interface.Generic", the generated code will transform "Interface" to lower case "interface" and will fail complication. e.g. "a.b.interface...."
java compiler failed with "filename or extension too long" error if too many files are generated from the DLL and hits the 32kb command line limit. Suggestion: put the filename in a file and use the @filename parameter for java compiler
Windows 7 powershell is unable to run the build script.
No exception handling in the tool. it just crashes with a stack trace