dot42 is open source Xamarin alternative. You can create Android app using c#. You can grab latest stable version from official repository https://github.com/dot42/dot42. But developer Olaf Pettersen created many fixes and improvements on it own repository https://github.com/ninjasync/dot42. So I forked it, made some fixes, compiled and generated setup from Olaf repository. You can download it from my gdrive https://goo.gl/jxAHgF
Olaf ported some libraries to work with dot42: MVVM Cross, JSON .NET, OxyPlot etc. Check his repository.
If you have any question about how to compile your own version you can ask here.
Currently android 5.0 is not supported. Apk files not working.
Hi, I have already a game build in C so I can covert it in an apk file with this software? Is it possible? E.g. In one of game's folder there are file like
File ACT
File AIR
File CNS, DEF e SFF
Sent from my LG-D802 using Tapatalk 4 Beta
Related
How does the AOSP and the Android SDK relate?
If I repo the AOSP do I by default now have the SDK?
Do I have to download it separately?
Or can I/Should I compile it from the AOSP?
I ask because after following the instructions up until: source.android.com/source/building.html. I successfully compiled full-eng and ran the emulator and everything works just fine. It also seems like adb is installed which from what I understand is a part of the SDK. I can't seem to find an answer to this.
So I am going to do my best at answering my own questions and posting for the benefit of anyone else who may be confused; if any of the statements I make are wrong feel free to correct me. This is just from my experience. There seems to be little information regarding how the two relate excepting the build/core/build-system.html, and sdk/docs/howto_build_SDK.txt included with AOSP and airtower.wordpress.com/2010/07/25/building-the-android-sdk/ and of course, trial and error.
NB: jindroid.com/2009/06/08/howto-build-sdk-from-android-source-code/ points to documentation that has since moved to the above location it seems. At least it wasn't there for me as of the most recent repo sync against master.
rpowell8 said:
How does the AOSP and the Android SDK relate?
Click to expand...
Click to collapse
The android SDK is a subset of the ADT (Android Developer Toolkit). The SDK as you download it today is basically just a few binarys for getting the actual content SDK.
I think the best way to describe the SDK is that it is divided into to parts tools, and libraries. The tools are for managing the sdk (tools/android) and misc tools to build apk's, align them, emulate an api etc, and then there are the tools in platform-tools which allow you to perform operations on your device (adb fastboot etc). The "libraries" are a set of API's , system images (file for running an android virtual device (emulator)), and documentation for each release of Android. These seem to reside under platform/
You can either download the above components from the command line, or from eclipse. Eclipse is actually included in the ADT as well with the plugin for android apps preloaded. If you don't have the plugin, you can get it vie Help/Install New Software. This launches what seems to be a front end for the android SDK Manager which allows you to graphically choose which platforms you want to support and emulate.
Now, how does the SDK (the tools and libraries) relate to the AOSP as you repo init/sync from the master repository? It seems you can't build apps from the code downloaded from the AOSP git repo (I'm not sure about this but doesn't seem like it). Instead, what you do, is you use the AOSP to build the SDK (NB: when you use the SDK Manager as mentioned above, you are getting prebuild SDKs, if you want to build the SDK yourself you use the AOSP code) as described in the above mentioned howto. Once the build for the Android SDK is complete it is located in out/host/linux-x86/sdk or similar directory. You can actually point the eclipse plugin to this directory as the location for the SDK...but I recommend using the .zip file that is in that directory and putting it somewhere other than the out directory. Reason being if you decide to do a lunch full-eng after you did the lunch sdk-eng, and then proceed to make, it will force a make cleaninstall and that will basically do a rm -rf on the out directory, deleting all of your SDK and any other platforms you downloaded through the sdk manager.
After you've built the sdk, you now have the necessary tools and API's to build for the platform you repo'd. A word of warning is that it seems if you repo the master branch, it is labeled as "AOSP" for the version indicating to Eclipse that the minimum platform required is the one you just built and so if you want to run it on your device you'll need the full platform loaded onto it or it will show you are running a version earlier than AOSP (also called 'Preview'). Example, as of this writing the version of AOSP is 4.2.1 and the API level is 17 (An API level is just a set of functions/datastructures available for a particular release of Android OS, so for Level 17 it corresponds to 4.2, You can use a higher API than your target (accept in the case of AOSP Preview) and still make sure you are compatible, but you can't use a lower API and expect to have functions/datastructures that were only implemented in later versions of Android). If you have downloaded the Android SDK for API level 17 it will be 4.2, not 4.2.1. You will not be able to run your app that you built using the API level 17 "Preview" based on 4.2.1...on your 4.2 emulator (or device for that matter). You will need to use the emulator based on the AOSP Preview build.
So in short the AOSP contains the sources to build the SDK, but you can also get prebuilt SDK's if you don't want to go through and build each API level.
rpowell8 said:
If I repo the AOSP do I by default now have the SDK?
Click to expand...
Click to collapse
No, you have the components to /build/ the SDK
rpowell8 said:
Do I have to download it separately?
Click to expand...
Click to collapse
No, you can either build it from the AOSP, or you can download it separately.
rpowell8 said:
Or can I/Should I compile it from the AOSP?
Click to expand...
Click to collapse
Probably should if you're building against the latest android development, but I don't see the need if you are building apps for already released API levels.
Preamble: I am a Java Android developer. I know the standard Android development flow.
I want to start developing for AOSP-CM. I follow the guide for import the whole Java source code in Eclipse, using the .classpath file provided with the source code. So I have a Java Project with all the source code, and I can browse and edit everything.
The next step is try to setup a single Android Project, for example the Phone Application, in order to use the ADT plugin feature like GUI graphical editor.
I want to edit Phone sources, build within Eclipse and above all use Eclipse Debugger.
It is possible? Where I can find a guide or tutorial ?
Sorry but I don't believe that nobody has addressed this problem.
How a CyanongenMod developer develop and build a single application? (please...don't reply with "vim" , "nano" or similar....not in the 21th century )
Hi,
for my own usage, I would like to integrate an app to CyanogenMod, which should be compiled with CM.
How do I do that?
Thanks,
Yannik
Any idea?
Are you building cm yourself? If so then the easy way is to place your project on github and then add the project to a manifest file in the .repo/manifests/local_manifest/ folder of your cm source, repo sync well the draw your project source code and it will be built with cm.
Or you can do it the right way and add your source into the /packages/apps folder of your source but you need to make sure everything is included correctly. Check out the link below for more info:
http://wiki.cyanogenmod.org/w/Doc:_adding_your_own_app
Adding an app to the actual cm source would be pretty hard it would have to be something pretty special that would add some real value, don't know how you could do that. Check out the cm wiki.
Sent from my PACman GT-i9100 using Xparent ICS Tapatalk 2
But by doing so.. can there be any problems with the working of the rom?? or will it work fine?
As long as your app works and compiles ok there should be no issues. I have modified a number of the stock apps from cm10.1 and added my own apps to the Rom I build from the source. I go the easy way and keep my project on github and add the details in the local_manifest folder.
Sent from my PACman GT-i9100 using Xparent ICS Tapatalk 2
Thanks for your help. I integrated everything like described in my device*.mk, but the source code is not going to compiled with CyanogenMod, dont now what to do.
Does your source code have an android.mk makefile? Check where you imported the source such as packages/apps/myproject/android.mk?
If not you will need to make one, look at an existing apps android.mk to see the details you need and just make sure you edit the following:
LOCAL_PACKAGE_NAME := PackageName
Where PackageName matches what you put into your device.mk file, then it should be included in the build and appear in your output zip.
Sent from my PACman GT-I9100 using xda premium
Got it! The Android.mk was missing on the build machine because I created the file on my mac and forgot to sync the files.
I'm currently in the process of creating a custom version of AOSP that will edit the functionality of the Host-Card Emulation feature of Android, allowing me to manually set the AID produced when my device goes into emulation mode.
I've downloaded the Android source, and have located the files I think governs HCE functionality.
From the NFC System Service, I've located the following files:
"CardEmulationManager.java" and "HostEmulationManager.java" located in "/aosp/packages/apps/Nfc/src/com/android/nfc/cardemulation/"
And from the Android core framework, for the NFC API I have found:
"CardEmulation.java" located at "/frameworks/base/core/java/android/nfc/cardemulation/CardEmulation.java"
From here, i'm unsure how to get started in editing the code. I'm unsure of the interactions between the files, and how they are called at run (I.e. which functions in the file I should be looking at, how would I go about adding my own code/modifying existing code in the file)
Is there any documentation online about how these files work/are ran? Or how would I go about finding out on my own (Through debugger tools etc.)
I'm currently using Eclipse for Ubuntu, and will be developing for a Nexus 7
Hey Guys,
I'm working on a global audio tuning system for Android similar to Viper4Android and JamesDSP, but allowing the User to program and create their own audio filters on the fly. In order to do so I need to link against libLLVM.so which is one of the Android Platform Libraries which doesn't seem to be exposed via the NDK (https://android.googlesource.com/platform/external/llvm/).
My assumption is that I will need to build that library from AOSP Source independent of my project and then link against my locally built copy. Once compilation of my project is complete I don't need to distribute my locally built libLLVM.so file since I can leverage the one existing on the actual device.
I just wanted to see if anyone has any experience doing this, or if I'm going off the deep end.
Thanks!