Hm.. What sources are you using ?
And which device are you compiling for ?
Tried a repo sync lately ?
Sent from my Xperia SL using xda premium
cm10 for LG NEXUS 4 (mako)
COMPILE From Source For Any Phone On Linux Distros [BUILD ENVIRONMENT TO COMPILE]
- Thread starter mithun46
- Start date
cm10 for LG NEXUS 4 (mako)
@mithun46 My phone has Unofficial CM 10.1.
Do I really need Official CM 10.1 ?
I wanna build AOKP For my Galaxy S2 Plus
Unofficial will work fine, its just harder to get all the files you need in place
Sent from my Desire HD using xda app-developers app
i had succesfully compile cm10.1 with no error, but after flash it on my phone, it didnt copy all file to system, only copy bin folder,
whats wrong?
whats wrong?
Last edited:
If there is unofficial support, you can follow this guide as well
Sent from my Xperia SL using xda premium
Hi all,
I'm porting CM10.1 to a new device, I've created device's repos and started compiling but got a problem
The detailed log is here
few last lines:
I tried to "make clobber" and start again with no effect at all
Could someone please advise me how to get rid of these?
I'm porting CM10.1 to a new device, I've created device's repos and started compiling but got a problem
The detailed log is here
few last lines:
Code:
frameworks/base/services/jni/com_android_server_location_GpsLocationProvider.cpp: In function 'void android::android_location_GpsLocationProvider_agps_data_conn_open(JNIEnv*, jobject, jstring)':
frameworks/base/services/jni/com_android_server_location_GpsLocationProvider.cpp:491:48: error: too many arguments to function
frameworks/base/services/jni/com_android_server_location_GpsLocationProvider.cpp: In function 'void android::android_location_GpsLocationProvider_agps_data_conn_closed(JNIEnv*, jobject)':
frameworks/base/services/jni/com_android_server_location_GpsLocationProvider.cpp:505:39: error: too many arguments to function
frameworks/base/services/jni/com_android_server_location_GpsLocationProvider.cpp: In function 'void android::android_location_GpsLocationProvider_agps_data_conn_failed(JNIEnv*, jobject)':
frameworks/base/services/jni/com_android_server_location_GpsLocationProvider.cpp:518:39: error: too many arguments to function
make: *** [/home/slayer_b/android/cyanogenmod/cm-10.1/out/target/product/ef47s/obj/SHARED_LIBRARIES/libandroid_servers_intermediates/com_android_server_location_GpsLocationProvider.o] Ошибка 1I tried to "make clobber" and start again with no effect at all
Could someone please advise me how to get rid of these?
Please modify your source . Make clobber will not help, if you're just passing too many arguments .. Find the call to the function, then modify as needed
Sent from my Xperia SL using xda premium
Please modify your source . Make clobber will not help, if you're just passing too many arguments .. Find the call to the function, then modify as needed
Sent from my Xperia SL using xda premium
actually I do not pass any arguments to the function
I just created a standart device tree to build CM, make lunch and otapackage. That's all. I do not think that anything from my changes could cause this.
btw this is the similar issue with AOSPA
the solution described there is to replace cpp and heareds file with the ones pulled from CM's source... But I'm already using CM's source
Last edited:
actually I do not pass any arguments to the function
I just created a standart device tree to build CM, make lunch and otapackage. That's all. I do not think that anything from my changes could cause this.
btw this is the similar issue with AOSPA
the solution described there is to replace cpp and heareds file with the ones pulled from CM's source... But I'm already using CM's source
*facepalm*
Excuse that, please
Now, while it's compiling, one makefile will call said function , passing some parameters.
If your gps module works with CyanogenMod on some other device, you must include those headers & CPP files, etc to your device's build tree.
Mostly it'll be while building the kernel that you're getting this error, so that's a good place to start looking
Sent from my Xperia SL using xda premium
*facepalm*
Excuse that, please
Now, while it's compiling, one makefile will call said function , passing some parameters.
If your gps module works with CyanogenMod on some other device, you must include those headers & CPP files, etc to your device's build tree.
Mostly it'll be while building the kernel that you're getting this error, so that's a good place to start looking
Sent from my Xperia SL using xda premium
thanks for your reply. It looks like I've found the issue with your help.
Next I would ask anyone who knows where to get libril, liblights etc? I know I can easily pull them from the similar arch device...but the question is where they were originally taken from? I have a kernel source for my device, is it useful for building CM except building kernel itself instead of using a prebuilt version
Probably originally taken from the device's source (if provided by OEM)
Or, as you said, a similar arch device..
May I know which device you're working on ?
If only kernel source is provided, you're gonna have to pull parts from your device & other devices that are similar to it
Hope your endeavors are successful
Sent from my Xperia SL using xda premium
It is Pantech Vega Racer 2. It has the same hardware as HTC One XL and AT&T SGS III
It seems my issue is still here. I've copied gps files from another device and forced to build them by including in mk file the following lines
# GPS
PRODUCT_PACKAGES += \
gps.msm8960
Android.mk file af gps project contains the following
ifeq ($(BOARD_VENDOR),pantech)
ifeq ($(TARGET_BOARD_PLATFORM),msm8960)
include $(call all-subdir-makefiles,$(LOCAL_PATH))
endif
endif
I double checked-all conditions should be true.
So, I suppose make ignores my files. That should I add to force it to use my gps project?
as far as I can see, it still uses old project, since my project is in another path
error: frameworks/base/services/jni/com_android_server_location_GpsLocationProvider.cpp:518:39: error: too many arguments to function
My proj path: /home/slayer_b/android/cyanogenmod/cm-10.1/device/pantech/ef47s/gps
# GPS
PRODUCT_PACKAGES += \
gps.msm8960
Android.mk file af gps project contains the following
ifeq ($(BOARD_VENDOR),pantech)
ifeq ($(TARGET_BOARD_PLATFORM),msm8960)
include $(call all-subdir-makefiles,$(LOCAL_PATH))
endif
endif
I double checked-all conditions should be true.
So, I suppose make ignores my files. That should I add to force it to use my gps project?
as far as I can see, it still uses old project, since my project is in another path
error: frameworks/base/services/jni/com_android_server_location_GpsLocationProvider.cpp:518:39: error: too many arguments to function
My proj path: /home/slayer_b/android/cyanogenmod/cm-10.1/device/pantech/ef47s/gps
Hmm. Did you make sure a makefile is calling your makefile before that one ? Check the order in which it builds; go to the brunch scripts, see where they point, then just keep following the chain of compiling , you'll get it easily (though , with a lot of reading)..
If you use whatsapp, PM me your number. And name
Sent from my Xperia SL using xda premium
Hmm. Did you make sure a makefile is calling your makefile before that one ? Check the order in which it builds; go to the brunch scripts, see where they point, then just keep following the chain of compiling , you'll get it easily (though , with a lot of reading)..
If you use whatsapp, PM me your number. And name
Sent from my Xperia SL using xda premium
Addidng Android.mk with the below content did the trick (since i started work from the scratch, I missed this file). Now I completely get rid of GPS failures.
Code:
LOCAL_PATH := $(call my-dir)
include $(call all-makefiles-under,$(LOCAL_PATH))After few hours of compiling (I have core 2 duo CPU with 2 Gb ram
) I got the below errors.
Code:
hardware/qcom/media-caf/mm-video/vidc/vdec/src/omx_vdec.cpp:9715:50: error: 'ION_FLAG_CACHED' was not declared in this scope
hardware/qcom/media-caf/mm-video/vidc/vdec/src/omx_vdec.cpp: In member function 'bool omx_vdec::allocate_color_convert_buf::set_color_format(OMX_COLOR_FORMATTYPE)':
hardware/qcom/media-caf/mm-video/vidc/vdec/src/omx_vdec.cpp:9920:71: warning: zero-length gnu_printf format string [-Wformat-zero-length]
hardware/qcom/media-caf/mm-video/vidc/vdec/src/omx_vdec.cpp: In member function 'OMX_ERRORTYPE omx_vdec::allocate_color_convert_buf::allocate_buffers_color_convert(OMX_HANDLETYPE, OMX_BUFFERHEADERTYPE**, OMX_U32, OMX_PTR, OMX_U32)':
hardware/qcom/media-caf/mm-video/vidc/vdec/src/omx_vdec.cpp:10068:138: warning: format '%d' expects argument of type 'int', but argument 5 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
make: *** [/home/slayer_b/android/cyanogenmod/cm-10.1/out/target/product/ef47s/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/src/omx_vdec.o] Ошибка 1
target StaticLib: libc_nomalloc (/home/slayer_b/android/cyanogenmod/cm-10.1/out/target/product/ef47s/obj/STATIC_LIBRARIES/libc_nomalloc_intermediates/libc_nomalloc.a)I'll investigate these as soon as I'll be at home
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
197
This is a guide to Compile From any CyanogenMod and CyanogenMod Source-Based source for Any Phone. This guide is for linux , Ubuntu etc.
What you’ll need
- A Phone Which runs Android
- A relatively recent computer (Linux, OS X, or Windows) w/a reasonable amount of RAM and storage. The less RAM you have, the longer the build will take. Using SSDs results in faster builds than traditional hard drives.
- A micro USB cable
- A decent Internet connection & reliable electricity
- Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with what a recovery image such as ClockworkMod is, for example. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.
So let’s begin!
Build ROM and ClockworkMod Recovery
Prepare the Build Environment
Install the SDK
If you have not previously installed adb and fastboot, install the Android SDK. "SDK" stands for Software Developer Kit, and it includes useful tools that you will can use to flash software, look at the system logs in real time, grab screenshots, and more-- all from your computer.
Install the Build Packages
Several "build packages" are needed to build From Source. You can install these using the package manager of your choice.
For 32-bit & 64-bit systems, you'll need:
For 64-bit only systems, get these:Code:git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.8-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev openjdk-6-jre openjdk-6-jdk pngcrush schedtool
For Linux Mint, you'll need:Code:g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline-gplv2-dev gcc-4.7-multilib g++-4.5-multilib
Code:libc6-dev x11proto-core-dev libx11-dev libgl1-mesa-dev mingw32 tofrodos python-markdown libxml2-utils
Create the directories
Code:mkdir -p ~/bin
Install the repo command
Enter the following to download the "repo" binary and make it executable (runnable):
Code:curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo chmod a+x ~/bin/repo
Put the ~/bin directory in your path of execution
Make sure that the ~/bin directory you just created is in your path of execution so that you can easily run the repo command even when you're not in ~/bin. Assuming you are using the BASH shell, the default in recent versions of Ubuntu, you can set it like this:
Code:export PATH=${PATH}:~/bin
Initialize the source repository
Make a Folder to Download the Sources and cd to it. For That:
Code:mkdir -p ~/SourceCode:cd Source
Enter the following to initialize the repository:
Download the source code
Code:repo sync
Get prebuilt apps
Code:cd ~/Source/vendor/cmCode:./get-prebuilts
How To Compile is there on next post105Prepare the device-specific code
After the source downloads, type:
Code:. build/envsetup.sh
Then Do This
Where ***** is the codename for your deviceCode:breakfast ******
Extract proprietary blobs
Now ensure that your Phone is connected to your computer via the USB cable and that you are in the ~/Source/device/***/***** directory (you can cd ~/Source/device/***/****** if necessary). Run as Root if on Debian using sudo. Then run the this script:
orCode:./proprietary-files.sh
Code:./extract-files.sh
You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the right place in the vendor directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution
Turn on caching to speed up build
Code:export USE_CCACHE=1
Start the build
Here ***** is the Phone CodenameCode:cd ~/Source brunch *****
If the build breaks...
If you experience this not-enough-memory-related error...
...you may want to make the following change to This File : system/build/tools/releasetools/common.pyCode:ERROR: signapk.jar failed: return code 1make: *** [out/target/product/n7100/cm_n7100-ota-eng.root.zip] Error 1
Change: java -Xmx2048m to java -Xmx1024m or java -Xmx512m
Then start the build again (with brunch).
If you see a message about things suddenly being “killed” for no reason, your (virtual) machine may have run out of memory or storage space. Assign it more resources and try again.
Install the build
Assuming the build completed without error (it will be obvious when it finishes), type:
Code:# cd $OUT
in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in /system is in a folder called system. The stuff that will become your ramdisk is in a folder called root. And your kernel is called... kernel.
But that’s all just background info. The two files we are interested in are (1) recovery.img, which contains ClockworkMod recovery, and (2) cm-[something].zip, which contains ROM.
Install ROM
Back to the $OUT directory on your computer-- you should see a file that looks something like:
Here *** is the phone codenameCode:cm-10-20120718-UNOFFICIAL-***.zip
Now you can flash the ...zip file above as usual via recovery mode. (Be sure you have backed up any previous installation before trying your new build.)
Feedbacks to this guide 18The issue with guides like these is they are specific to one version of Ubuntu. I successfully build Android on gentoo, which has about as little in common with Ubuntu as possible. Hence we prefer to go for guides which, where possible, teach the reasoning, rather than the method.
For building CM, this might be worthwhile merging into the "how to build android from source" one?
Unfortunately this guide isn't usable for most people, as it relies on the hacksung build scripts, so you can only build for certain devices...
What might be better is a guide on using roomservice via lunch, to build for any device?6What if i want to compile the PAC rom?
https://github.com/PAC-man
Downloading Ubuntu now!! Excited!!
Edit figured it out myself!!
repo init -u git://github.com/PAC-man/android.git -b jellybean
thankx anyways...
ya and you might need a minor edits to makefiles in the config ...
btw
this is a thread maintained by me
http://xdaforums.com/showthread.php?t=2059939
so feel free to post your errors that you encounter....
@op
explain what every step means rather then just copy paste....
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
32bit systems don't have the packages to build jb and above.. so it wont work with 32bit systems.. - A Phone Which runs Android
