I am trying to compile some source code but when i run the command
make -f android-9-armv7.mk
I get the following error
android-9-armv7.mk:1: * missing separator. Stop.
This is the contents of the file above:
And I have set the IMAGINE_PATH variable as well, cant seem to figure it out.
link ../imagine/make/shortcut/common-builds/android-9-armv7.mk
Compiling instructions
http://code.google.com/p/emu-ex-plus-alpha/wiki/Compiling
Imagine is locaed at C:/Imagine
I don't know where you've taken the sources, but all the android-9-armv7.mk files from different projects on that git has following content:
../imagine/make/shortcut/common-builds/android-9-armv7.mk
...there is no link keyword, which probably is why you get this error.
Also, please be informed that you're building this on Windows machine while documentation clearly states that it's supported only on Linux and Mac OS X.
Related
We are trying to bringup a new MIPI display that we are using for our smart glasses solution. To do this we have roughly followed the guide provided by Qualcomm: https://developer.qualcomm.com/download/db410c/dsi-display-porting-guide-linux-android.pdf
The method of porting a new display required that we modify the Android bootloader (Little Kernel) with the new configuration for the display we are using. This allows us to select the new display using the command:
$ fastboot oem select-display-panel <display-name>
The problem is that to add this new configuration to LK we need to rebuild the image (emmc_appsboot.mbn). This has been unsuccessful so far.
We found a file within the LK directory that is called AndroidBoot.mk. A comment in this file says “#Android makefile to build lk bootloader as a part of Android Build”
According to that comment, it seems that LK should be built as a part of Android build, however we cannot seem to do so. Is this thinking correct?
As per the LK github build instructions, we've also tried running
$ make msm8909
from the LK directory but we are getting the following error:
unrecognised option '-mcpu=cortex-a8'
I suspect this may be due to missing part of the toolchain as I've had to manually add arm-eabi-gcc to the path variable.
Can anyone provide any information on what command we need to use or what process needs to be followed in order to generate a new LK bootloader file with the updated config?
The problem was due to an incorrect PATH variable set. I fixed the issue by adding the correct path: ".../prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/" to the .bashrc file and re-logging in.
I want to build an ocr app in android.For that i am using tessaract library.I am following this turorial ocr tutoial it says follow below steps
Download the NDK & extract to C:\ drive-Done
Set NDK Path & Android SDK path to PATH variable in Enviorment Variable.-Done
Download tessaract library and extract it to C:-Done
open command line & go inside tessract folder ibn downloaded library.-
Write ndk-build-Not Done
When i write ndk-build it says the system can't find the specified path.
Please tell me how to resolve this issue.I have already spent lot of hard time on this.
Thanks in advance.
If you re-read the link you posted, you may notice this line from the author:
Attention: if you fail at any of the above steps, you are not ready for this shit yet. Better grab an introduction to android development course, read a book, then come back to this tutorial. You’ll just waste time and nerves and you’ll bitch about it in the comments that this crash, this doesn’t work. (PS. no, I will not send you the source code on your email, stop spamming k thx.)
You should seriously consider his advice - working with the Android NDK only gets more difficult from here.
You're probably getting that error message because cmd couldn't find the ndk-build program, which is located inside the root of android-ndk-r10e. Possible causes:
You made an error when editing your PATH variable - make sure each file path is separated by a semicolon and that you provided the full path to your NDK install.
Your PATH is too long - the max length is 260 characters. See this page for more info. tl;dr: prefix \?\ to your PATH to get around this length limit.
You had cmd open when you set the variables - try restarting the cmd
program or even restarting your machine.
Need your guidance, I am writing one app in android with the help of native code which will communicate with CAN (Controller Area Network) port ; for that in my C code i used linux/can.h header file. and i am following "http://mobilepearls.com/labs/ndk-builder-in-eclipse/" this link to build my app. but one i set all thing i got bellow msg in eclipse console box
Compile thumb : can_port <= cansend.c
jni/cansend.c:14:23: fatal error: linux/can.h: No such file or directory
compilation terminated.
make: *** [obj/local/armeabi/objs/can_port/cansend.o] Error 1
One more thing, i am working on windows environment. But i don't think this may be cause.
It is correct that it is not a Windows/Linux problem. The simple problem is that compiler is unable to find the file can.h. Now, for your info, when the compiler starts compiling, it searches for its header files in the folder
C:\(path to NDK folder)\platforms\(android-version)\(arch)\usr\include\linux
Now, if there isn't a can.h there, the compiler will flag an error. So the best way is
Either copy can.h to the above path (not tested)
Modify your Makefile to path to the correct directory where this header file is kept
Hope this helps!
I trying to compile CM10 with AOSCompiler(using ubuntu). And i got 2 questions:
1.It's Saying me that it's can't find my device:
elichai#elichai-MT6840:~/.aoscompiler/build$ . build/envsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
elichai#elichai-MT6840:~/.aoscompiler/build$ lunch cm_maguro-userdebug
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/maguro/cm.mk]]: "device/samsung/tuna/device.mk" does not exist. Stop.
Device maguro not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_maguro
CyanogenMod/android_device_samsung_maguro already exists
Syncing repository to retrieve project.
Fetching projects: 100% (1/1), done.
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/maguro/cm.mk]]: "device/samsung/tuna/device.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_maguro'
** Do you have the right repo manifest?
I tried to do just 'lunch' and choose my device from the list and it's gave me the same error.
I tried to use 'breakfast' and it's gave me the same error too.
2.The AOSCOmpiler Saying that:
Adb isn't running
Need adb to setup vendor files.
Is this something you are going to do yourself?
Please try again.
Even i added to the file '/etc/bash.bashrc this line:
export PATH=${PATH}:/home/elichai/Downloads/SDK/tools:/home/elichai/Downloads/SDK/platform-tools
(this is my SDK location) and now i can use 'adb' without going to the SDK folder. but it's still not working(the AOSCompiler).
Sorry, I know it's getting old, but, to to the export PATH=${PATH}:/home/elichai/Downloads/SDK/tools:/home/elichai/Downloads/SDK/platform-tools you should remove {}s
export PATH=$PATH:/home/elichai/Downloads/SDK/tools:/home/elichai/Downloads/SDK/platform-tools
That's what I did. I'm on Ubuntu 10.04
Also, you could add the paths to your .bashrc, assuming you are using bach as you shell.
I'm sure someone will correct me if I'm wrong.
build/core/base_rules.mk:166: *** system/core/allwinner_a10_core/adb:
MODULE.HOST.EXECUTABLES.adb already defined by system/core/adb. Stop.
I can understand that there is a conflict between the ICS source code's adb and the adb provided by the actual board is leading to the conflict.
I want to know where and what file i have to change to resolve this conflict,i.e, tell the compiler which adb to use. (more generically which library to use, as i know this is a generic problem)
I wish the compilation process was explained better by google's reference documents!