Mod edit: Thread closed as duplicate of
Building devices flame and coral for pixeldust
I'm having a problem building the device flame and I keep running into this issue on pixeldust does anyone know how to solve this error? and this problem on coral, I have a feeling it's using python3 rather than python2 but idk how I should...
forum.xda-developers.com
I'm having a problem building the device flame and I keep running into this issue on pixeldust
does anyone know how to solve this error?
bootable/recovery/Android.mk: error: "librecovery_ui_ext (SHARED_LIBRARIES android-arm64) missing librecovery_ui_pixel (STATIC_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build
Related
Because it seems to be a often requested topic I wanted to give back my experince with compiling the in topic mentioned source code and how really value it is for anything.
I started this because I got the code for review for a intrested customer but my experince with arm and gcc is rather low. So i started reading up on the cross compiler and came accros serveral dificults with the build enviorment.
First the code seemed to be aimed to a rather old version of gcc, newer cross compiler toolchains won't compile it.
So I obtained a 2004 linux (redhat 8) which fitted best in the time mentioned in the headers source was last edited. On this system I was able to build the cross-arm toolchain like mentioned in the readmes without any problem.
With the builded toolchain I was also able to compile celp_fxp and with the make file. i mentioned that in the makefile there is a (intentionally) added error. After the last source file there was fxlp.c added which is not a file present in the tree. After removing this the .o files builded fine.
I imported the .o files produced back to windows Embended Visual C++, opened the project and started a compile like further explainedin the readme docs. Sadly I now face this error:
acb_parm.o : fatal error LNK1190: invalid fixup found, type 0x0010
It is possible this error occures from a wrong compiled gmp libary for which no build isntructions were given. If anybody has any value information on this I would greatly appriciate this. As I said earlier I had really no experince with gcc form cross arm before i started here. I always left out linux compiler of my embended world.
I am working on this now since a few days, maybe someone else got experince in this he/she wants to share. Thansk for reading.
Is there somebody success to compile the XDAndroid on the new fedora 13?
when i make it, ld DSO linking error occur
Sup XDA, there is one question about porting the sailfish OS. I am guided by the official documentation, according to the latest guide on HADK - https://sailfishos.org/wp-content/u...OS-HardwareAdaptationDevelopmentKit-2.0.1.pdf
I encountered a problem with the point 7.2.1. When performing the rpm/dxd/helpers/build_packages.sh. there is installation and assembly of packages, but it breaks off when creating a middlevare, namely, the libhybris. Here is the complete log of the assembly - https://paste.debian.net/plain/997702
As I understood from the logs myself to build the libhybris, I need to use the compiler with C++11 support, but in the scratchbox2 the old version of the gcc-4.6.3 version is used, which does not understand the standart C++11. I tried to change the CFLAGS from "--std=gnu++11" to "--std=gnu++0x" , but the libhybris does not compile with the flag of the old standards.
What do you propose to do? How to update the compiler in a scratchbox2 target?
P.S. wrote it via google translate, dont be offended pls
memewarrior said:
Sup XDA, there is one question about porting the sailfish OS. I am guided by the official documentation, according to the latest guide on HADK - https://sailfishos.org/wp-content/u...OS-HardwareAdaptationDevelopmentKit-2.0.1.pdf
I encountered a problem with the point 7.2.1. When performing the rpm/dxd/helpers/build_packages.sh. there is installation and assembly of packages, but it breaks off when creating a middlevare, namely, the libhybris. Here is the complete log of the assembly - https://paste.debian.net/plain/997702
As I understood from the logs myself to build the libhybris, I need to use the compiler with C++11 support, but in the scratchbox2 the old version of the gcc-4.6.3 version is used, which does not understand the standart C++11. I tried to change the CFLAGS from "--std=gnu++11" to "--std=gnu++0x" , but the libhybris does not compile with the flag of the old standards.
What do you propose to do? How to update the compiler in a scratchbox2 target?
P.S. wrote it via google translate, dont be offended pls
Click to expand...
Click to collapse
Heyyo, the guide has a messed up sb2 section.
I can't load your Pastebin link but please check my thread here to see how I resolved the bad sb2 guide
https://together.jolla.com/question/172682/unknown-tag-systemd_requires/
Also, just in case you get stuck on 8.5 of that guide here's how I fixed that too
https://together.jolla.com/question...cregister-for-85-building-the-image-with-mic/
Hi, first of all, sorry if this is an stupid question, or if I'm underestimating the difficulty of porting this kinds of software, or if I'm saying something wrong.
I really like GNU/Linux mobile distros like Sailfish OS, Lune OS, Ubuntu Touch and Plasma Mobile, they use Halium for base for using our hardware, Is someone already trying to port Halium for our device or is there already an existing port? That would open a new world of OSs for our device.
If anyone hasn't ported Halium yet I could give it a try; However, I have 0 experience porting stuff, so I can promise nothing, I'm good using Linux and reading documentation and guides though, but I don't know if that will be enough.
Again, sorry if I'm underestimating the difficult of porting, if I'm saying something wrong and if I can't make myself understood.
Edit: I'm not actually working on the project because I haven't the phone. I did a progress when I had it, anyone interested in the project can PM if get stuck or need help or guide. Thanks for everything, great community.
Hi,
I am a beginner in the field of kernel customization and I want to learn this.
I have a OnePlus 6T device which I have successfully rooted. I want to customize the kernel of this device.
For this I have already cloned the kernel source code from https://github.com/OnePlusOSS/androi...lus_sdm845.git
But I didn't find a good documentation for kernel customization.
I found a little info that I need a tool-chain for building the kernel source code but I don't have enough knowledge of this that
- what is the correct tool-chain for my downloaded version of kernel.
- Is android ndk include that toolchain?
- If no where can I found the tool-chain?
Please guide me to learn about this.
Any good web-link or comment can be helpful.
Best Regards,
Vatish
Vats12 said:
- what is the correct tool-chain for my downloaded version of kernel.
- Is android ndk include that toolchain?
- If no where can I found the tool-chain?
Please guide me to learn about this.
Any good web-link or comment can be helpful.
Best Regards,
Vatish
Click to expand...
Click to collapse
-I think that is more user choice...
-No, NDK has nothing to do with toolchain.
-Look for Linaro. That is a pretty popular one.
I was going to follow this tutorial by @nathanchance to brush myself back up (its been a while).
[REFERENCE] How to compile an Android kernel
I think this man knows more than most
Scott said:
-I think that is more user choice...
-No, NDK has nothing to do with toolchain.
-Look for Linaro. That is a pretty popular one.
I was going to follow this tutorial by @nathanchance to brush myself back up (its been a while).
[REFERENCE] How to compile an Android kernel
I think this man knows more than most
Click to expand...
Click to collapse
Thanks for the great link. I have read but when I went to google tool-chains link(https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/) then I was confused:
- Which branch I should clone for my device
OR
- Is it fine to continue with other step by choosing the master branch from google tool-chains?
Please provide me a little information on the tool-chain selection for the kernel.
Best Regards.
Vats12 said:
Thanks for the great link. I have read but when I went to google tool-chains link(https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/) then I was confused:
- Which branch I should clone for my device
OR
- Is it fine to continue with other step by choosing the master branch from google tool-chains?
Please provide me a little information on the tool-chain selection for the kernel.
Best Regards.
Click to expand...
Click to collapse
I am not in a position to give advise. I'm too rusty. It would be best to post the building questions in that linked thread.
Scott said:
I am not in a position to give advise. I'm too rusty. It would be best to post the building questions in that linked thread.
Click to expand...
Click to collapse
I understood that any tool-chain will work. The only thing we need to take care is the exports that we will use when compiling the kernel source.
e.g. for my arm64 bit device I have used linaro toolchain - the latest version.
and used export ARCH=arm64 && export SUBARCH=arm64 when compiling the source code.
I am able to compile it successfully but now I have to find the information about how to flash it on the device.
Following are the last lines of compilation:
```
CC drivers/media/platform/msm/broadcast/tspp.mod.o
CC drivers/media/platform/msm/dvb/adapter/mpq-adapter.mod.o
CC drivers/media/platform/msm/dvb/demux/mpq-dmx-hw-plugin.mod.o
GZIP arch/arm64/boot/Image.gz
CC drivers/soc/qcom/llcc_perfmon.mod.o
CC drivers/video/backlight/lcd.mod.o
CC net/bridge/br_netfilter.mod.o
LD [M] drivers/char/rdbg.ko
LD [M] drivers/media/platform/msm/broadcast/tspp.ko
LD [M] drivers/media/platform/msm/dvb/adapter/mpq-adapter.ko
LD [M] drivers/media/platform/msm/dvb/demux/mpq-dmx-hw-plugin.ko
LD [M] drivers/soc/qcom/llcc_perfmon.ko
LD [M] drivers/video/backlight/lcd.ko
LD [M] net/bridge/br_netfilter.ko
CAT arch/arm64/boot/Image.gz-dtb
make[1]: Leaving directory '/home/.../KernelCustomization/android_kernel_oneplus_sdm845/Out'
```