Skip to content
This repository has been archived by the owner on Oct 25, 2021. It is now read-only.

Poor tooling, generally bad experience #705

Open
iamheavymetal opened this issue Sep 7, 2018 · 2 comments
Open

Poor tooling, generally bad experience #705

iamheavymetal opened this issue Sep 7, 2018 · 2 comments

Comments

@iamheavymetal
Copy link

Just passing through though I feel it would be unfortunate if I didn't leave some feedback..

  1. 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

  2. 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...."

  3. 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

  4. Windows 7 powershell is unable to run the build script.

  5. No exception handling in the tool. it just crashes with a stack trace

@galilov
Copy link

galilov commented Oct 22, 2018

faced the same issue :(

@korovan-software
Copy link

Any workaround for 3td case?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants