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.
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.
While installing NVidia Android CodeWorks I have received an error at the very end of the installation process saying :
installing compile samples 4.0 failed nvidia
Return Code: 2Compile Samples failed. Please check the /home/user/NVPACK//_installer/compile.log. You can send it to TegraDeveloperPack-Users#nvidia.com if you can not resolve it.
Does anyone know how to solve this problem please
So that other people having the same problem might go on something for I have not found an optimal solution to this problem.
I have managed to solve it by simply copying my version of jdk (which is jdk1.8.0_101) to the specified Nvidia Codeworks folder and renaming to the one missing in the log (...\Nvidia\Codeworks_installer\compile.log - \Nvidia\Codeworks\jdk1.8.0_77" does not exist.) In my case it compiled successfully, however it must be noted that this is not a good solution. Messing around with the environment valuables might be a reasonable place to start otherwise.
If your log file shows:
Error: JAVA_HOME is not defined correctly.
make: *** [antbuild_Basic_debug] Error 1
We cannot execute /usr/bin/java
Makefile.Basic.mk:92: recipe for target 'antbuild_Basic_debug' failed
you can fix it by creating a soft link like this:
sudo ln -s $JAVA_HOME/bin/java /usr/bin/java
I am trying to build Cyanogenmod 12.1 with my ubuntu.
Target device is Korea G3(F400x).
I used TheMuppets's proprietary for vendor/lge/ and other things from Cyanogenmod github, and pulled needed files from Cyanogenmod 12 which is running on my phone.
But when I try to build...(using command "brunch f400k") I can see this.
make: *** `/home/newnis/android/system/out/target/product/f400k/obj/SHARED_LIBRARIES/libandroid_servers_intermediates/LINKED/libandroid_servers.so'에서 필요로 하는 타겟 `/home/newnis/android/system/out/target/product/f400k/obj/lib/libtime_genoff.so'를 만들 규칙이 없습니다. 멈춤.
This is korean message, I think this will mean:
make: *** No rule to make target `/home/newnis/android/system/out/target/product/f400k/obj/lib/libtime_genoff.so` needed by `/home/newnis/android/system/out/target/product/f400k/obj/SHARED_LIBRARIES/libandroid_servers_intermediates/LINKED/libandroid_servers.so'. Stop.
in english.
I copied libandroid_servers.so from my phone, but result was same.
Also, I tried to find the libtime_genoff.so from my phone, but I could not find that.
I googled this problem, but I could not find any working solution.
Anyone knows the solution?
I fixed it.
Something was wrong with device/lge/f400k.
It's name(f400k) wasn't matched with f400 in vendor/lge/g3-common/Android.mk
I changed directory name to f400(I edited some file's name and files in device/lge/f400, too.), and it works.
Now it looks like it's compiling well...
I'm trying to help out a friend of mine by compiling a ROM for the Samsung Galaxy Grand 2 (ms013g).
make: *** No rule to make target
'/home/quiche/cmsource/out/host/linux-x86/bin/dtbToolCM' needed by
'/home/quic/out/target/product/ms013g/dt.img '.
I keep getting this error i cannot fix, i tried the fix described here: CM12 build failed for oneplus one
and i also made sure android_device_qcom_common is in my local_manifest.xml.
Somewere else, someone suggested changing dtbToolCM to dtbTool, which i tried to no avail.
Seems like You need to add suitable kernel project to your local manifest
Downloading of android_kernel_samsung_klte project helped to me (I was building device_samsung_klte)
Please try this to add below to your Device.mk
BOARD_KERNEL_SEPARATED_DT :=true
Please see Android.mk for dtbtool.
Thank you.
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.