-
Notifications
You must be signed in to change notification settings - Fork 95
Embeddinator runs without errors, still no aar file #767
Comments
Could you run Remove the |
I ran the command you mentioned with the following result:
I didn't get what you mean with this:
|
@MarcKammermann I find the old issus : jamesmontemagno/embeddinator-hellosharedui#3 And the msbuild output is without any error but still no arr file. This is a confusing question |
Same problem |
Same here… Is this project still actively being maintainted? 👀 |
I doubt it. You just have to check the commits and see that its so long since they made a fix and not to count the documentation is as old as 3 years at least (referencing VS2017) not to count the 100+ issues without resolving. |
Downgrading NDK to v14 helped in overcoming this. The project isn't updated for the latest NDKs |
@lindexi Unhandled Exception: System.ComponentModel.Win32Exception: The system cannot fin d the file specified at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startIn fo) at System.Diagnostics.Process.Start() at Embeddinator.Helpers.Invoke(String program, String arguments, Dictionary |
@Harishez I do not know which file not found. |
@lindexi It doesn't point to any file. I get this after the following in log Compiling binding code...Full Log: Generating Java stubs...
|
did you change anything else? I am facing the same issue and downgrading to NDK v14 alone does not resolve it. |
Steps to Reproduce
I created a test project like its described here
https://docs.microsoft.com/en-us/xamarin/tools/dotnet-embedding/get-started/java/android
I installed Embeddinator as nuget
I tried all methods of building an aar file like its described here
https://docs.microsoft.com/en-us/xamarin/tools/dotnet-embedding/get-started/install/install
I get no positive result in any of these possibilities
Expected Behavior
Should generate aar file inside output folder
Actual Behavior
generates a bunch of files but no aar
Environment
Win10 64bit, VS19 (16.4.6)
Logs
WHEN USING COMMAND LINE WITHOUT -c
Embeddinator-4000.exe -gen=Java --platform=Android -out=Foo bin\Debug\hello-from-csharp.dll -v
This runs without errors, but there is still no aar file generated in the output folder
WHEN USING COMMAND LINE WITH -c
Embeddinator-4000.exe -gen=Java --platform=Android -out=Foo bin\Debug\hello-from-csharp.dll -v -c
WHEN USING MSBUILD TARGETS
WHEN USING POST-BUILD STEPS
The text was updated successfully, but these errors were encountered: