Hi all.
I have run into a little problem while compiling from source. The following error is given while attempting to compile the libgps.so file:
Code:
make: *** No rule to make target `out/target/product/leo/obj/lib/librpc.so', needed by `out/target/product/leo/obj/SHARED_LIBRARIES/libgps_intermediates/LINKED/libgps.so'. Stop.
I have got all the proprietary files needed. If I remove the gps library from compilation, then it builds without any errors.
Any ideas?
MrP.
I'm trying to port firefox os(B2G) to my device (HTC Desire HD). While building it stops because of error at libgui in SurfaceTextureClient.cpp
last few lines of build log
Code:
target thumb C++: libgui <= frameworks/base/libs/gui/SurfaceTextureClient.cpp
frameworks/base/libs/gui/SurfaceTextureClient.cpp: In member function 'virtual int android::SurfaceTextureClient::setUsage(uint32_t)':
frameworks/base/libs/gui/SurfaceTextureClient.cpp:500: error: 'GRALLOC_USAGE_EXTERNAL_ONLY' was not declared in this scope
frameworks/base/libs/gui/SurfaceTextureClient.cpp:505: error: 'GRALLOC_USAGE_EXTERNAL_BLOCK' was not declared in this scope
make: *** [out/target/product/ace/obj/SHARED_LIBRARIES/libgui_intermediates/SurfaceTextureClient.o] Error 1
and the full build log is here
I think this happens because of the build system doesn't build
Code:
hardware/qcom/display/libgralloc/
before building
Code:
frameworks/base/libs/gui/
How can I tell the B2G build system to do that? Or is there any other way to get around this without breaking(like can't see anything) the build?
Here is my B2G manifest file.
I know this belongs in the developer forum but I still can't post in it
In your device blobs you are telling it to make hardware/com/display or display_legacy or the like correct? One way to at least get past this error and possibly get either further clues or have it compile would be to just add the header to this file or reference it as a dependency in your frameworks/base makefiles. These are just some ideas. Its hard without knowing where you are pulling these from (cm repo, Google, linaro, b2g, or whatever) so I can look at the code and makefiles. But normally this sort of thing will be an adjustment needed to your makefiles. Its just finding which, or if its simply a missing statement like this in your device makefiles TARGET_QCOM_DISPLAY_VARIANT := legacy
Pacman for the 3vo CDMA
hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/know.../open-devices/
feel free to fork, build, fix and push back
Br
J
Wohooo! Finally! [emoji106] [emoji2] [emoji3]
Excellent! An AOSP ROM is the only thing I can think is missing from an otherwise perfect device.
GCC here we come..
Andoroid L (5.0) code, binaries and guides are published
No working camera or modem, looks like we've still got awhile guys...
great news,thankss
nice
I'm syncing it now. I'm going to do a blind build (not changing anything just going with what's already there) because I have yet to unlock my bootloader and won't until they can figure out a way so at least the camera and noise cancellation don't get messed up when unlocking (if I go back to a sony stock rom I know it won't matter on AOSP)
graffixnyc said:
I'm syncing it now.
Click to expand...
Click to collapse
Preparing to build as well. Like you, I haven't BL unlocked and won't until the DRM issues are resolved.
jerpelea said:
Andoroid L (5.0) code, binaries and guides are published
Click to expand...
Click to collapse
Your work is really appreciated. FYI, I convinced a friend to buy a Z3C in large part due to your AOSP commitment. [emoji106]
Guessing we'll need to reverse engineer the camera and modem binaries? Is that right?
illogic6 said:
Guessing we'll need to reverse engineer the camera and modem binaries? Is that right?
Click to expand...
Click to collapse
no
Reverse Engeneering
In other words - SONY will deliver the required drivers or better all required driver will be there in a while...
I get compile error:
Code:
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c: In function 'bta_av_audio_sink_getconfig':
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: error: 'p_sink' undeclared (first use in this function)
if (bta_av_co_audio_sink_has_scmst(p_sink))
^
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: note: each undeclared identifier is reported only once for each function it appears in
make: *** [out/target/product/aries/obj/SHARED_LIBRARIES/bluetooth.default_intermediates/../btif/co/bta_av_co.o] Error 1
make: *** Waiting for unfinished jobs....
help appreciated
m0d said:
I get compile error:
Code:
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c: In function 'bta_av_audio_sink_getconfig':
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: error: 'p_sink' undeclared (first use in this function)
if (bta_av_co_audio_sink_has_scmst(p_sink))
^
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: note: each undeclared identifier is reported only once for each function it appears in
make: *** [out/target/product/aries/obj/SHARED_LIBRARIES/bluetooth.default_intermediates/../btif/co/bta_av_co.o] Error 1
make: *** Waiting for unfinished jobs....
help appreciated
Click to expand...
Click to collapse
just re sync your tree and fix is there
That inform you in: <insert the cpu thread number of your computer> ??? Please
I got a build to finish. I'll post the boot and system img for someone to try.. I'm not going to go through the trouble yet to make a flashable zip until we at least know it boots. I'll upload the images now
Posted the images: http://forum.xda-developers.com/z3-compact/development/img-aosp-5-0-boot-imgs-t2940499
So @NisseGurra flashed the build I made yesterday here is what he found to be broken:
no wifi, no network, some reboots, no usb storage, no external sd, no sound or camera
But its very snappy, looking forward to a functional aosp
Thank you for the guides,
I was able to compile AOSP for D5803 successfully.
A couple of issues,
First,
Has the Cherry-Pick for external/libnfc-nci/ that is provided in the guide been merged?
As I get the following error,
Code:
/external/libnfc-nci $ git cherry-pick 83cf98d0a5018e023eb9cc8b4e394957f9a6989f
fatal: bad object 83cf98d0a5018e023eb9cc8b4e394957f9a6989f
(Updated on blog to correspond with Shinano Issue.)
Second,
I get the following error when I try to output zipped package,
Code:
[B]No private recovery resources for TARGET_DEVICE aries
No recovery.fstab for TARGET_DEVICE aries[/B]
make: *** no rule to make target `otapackage'. stop.
Does this have anything to do with: TARGET_BOOTLOADER_BOARD_NAME := D5803
or that it is called aosp_d5803 (aosp_d5803.mk)
UPDATE: otatools seems to work, [" . build/envsetup.sh && time lunch aosp_d5803-userdebug && make otatools "].
But I can not find the output / output directory for package
Oh,
Is there supposed to be a userdata.img too?
Looking around a different sources mention it, however there is no userdata.img when I compiled it.
Thank you for your time
edited (solution): I forgot I had another thread on this same basic topic. You have to merge AOSP + Device Sources + Hardware Drives and set it up to build the sources.
https://forum.xda-developers.com/android/software/toolbox-c-struct-define-toolname-tool-s-t3568409
If I try to compile my own customize 'toolbox' binary for example, I can't find the headers anywhere in the toolchains or included headers. I can search them down from Google sources but I gave up after tools.h. I have a feeling this is NOT the way I am supposed to be doing it.
Is there a shared library on my device that I pull off to get these headers? (lib?????.so).. Where do I get headers for Android/log.h and cutils properties.h and selinux.h ??? Or are we not supposed to compile these binaries on a Ubuntu machine? (do I compile them on the device itself?)
ediit: (here's compiling it another way, obviously I can make a hack easily but working with Android is so much harder.)
arm-linux-gnueabi-gcc -static -march=armv8-a toolbox.c -o toolbox
toolbox.c:6:25: fatal error: android/log.h: No such file or directory
compilation terminated.
edit, solved i think
I think it's stand alone toolchain not defined. If that's not the answer, it's a fun answer so I'm playing with that. If I don't have the answer I will pass the question up, download sources and start trying to compile Android proper. (which is my new goal now, I want open source phone and I want to compile my own OS 100%, besides the closed sources, it's so exciting!!) ~so much for sleep
Kernel compilation error '"aarch64-linux-android-gcc" is not allowed to be used.'
I'm building the kernel with LineageOS 17.1 / Android 10 r31 however the build process errors out during kernel compilation.
Specifically with:
Code:
"aarch64-linux-android-gcc" is not allowed to be used. See https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools for more information.
make[3]: *** [/home/saltoin/android/lineageos-17.1/kernel/samsung/universal8895/scripts/Makefile.build:153: scripts/mod/devicetable-offsets.s] Error 1
Following the link says that any host tools in PATH won't be allowed to be used during compilation. However, `aarch64-linux-android-gcc` is not from my path but supplied by the build tools. Unless I'm mistaken in that assumption.
Regardless, exporting TEMPORARY_DISABLE_PATH_RESTRICTIONS=true allows aarch64-linux-android-gcc.
Unless I'm missing something, I don't believe I should be getting this error.
Thoughts?
Hello there, have you found any solution?
TEMPORARY_DISABLE_PATH_RESTRICTIONS=true doesn't work in the config file. What do you mean by export? Thanks in advance for help.
Build System Changes for Android.mk Writers
As a temporary measure, you can set TEMPORARY_DISABLE_PATH_RESTRICTIONS=true in your environment to temporarily turn off the error checks and allow any tool to be used (with logging).