[GUIDE] How to build Android on Windows
- Thread starter Uldiniad
- Start date
-
- Tags
- bashonwindows lineageos windows wsl
Thanks again for the help. Tried make clobber and it's still happening. I am getting this before the error happens...
Code:
[596/986] including system/sepolicy/Android.mk ...
system/sepolicy/Android.mk:79: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version
system/sepolicy/Android.mk:89: warning: Be careful when using the SELINUX_IGNORE_NEVERALLOWS flag. It does not work in user builds and using it will not stop you from failing CTS.How do I fix this?
Last edited:
https://review.lineageos.org/#/q/project:LineageOS/android_device_oneplus_oneplus3
there are a lot of unmerged patches, I think it is a matter of patience
Stupid question time.
Have you changed your directory structure in GitHub.
You say add this line to roomservice.xml
<project name="TheMuppets/proprietary_vendor_your device brand" path="vendor/your device brand" remote="github" />
but when I look it up it looks like this in browser
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/lineage-16.0/kltekor
So mine looks like this.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_samsung" path="tree/lineage-16.0/kltekor" remote="github" />
<project name="LineageOS/android_device_samsung_kltekor" path="device/samsung/kltekor" remote="github" />
<project name="LineageOS/android_device_samsung_klte-common" path="device/samsung/klte-common" remote="github" />
<project name="LineageOS/android_device_samsung_msm8974-common" path="device/samsung/msm8974-common" remote="github" />
<project name="LineageOS/android_kernel_samsung_msm8974" path="kernel/samsung/msm8974" remote="github" />
<project name="LineageOS/android_packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
</manifest>
repo sync successful about to restart the WSL terminal run 2 commands then brunch.
Build failed 2.5 hours in - can anybody explain why (file attached)
Have you changed your directory structure in GitHub.
You say add this line to roomservice.xml
<project name="TheMuppets/proprietary_vendor_your device brand" path="vendor/your device brand" remote="github" />
but when I look it up it looks like this in browser
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/lineage-16.0/kltekor
So mine looks like this.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_samsung" path="tree/lineage-16.0/kltekor" remote="github" />
<project name="LineageOS/android_device_samsung_kltekor" path="device/samsung/kltekor" remote="github" />
<project name="LineageOS/android_device_samsung_klte-common" path="device/samsung/klte-common" remote="github" />
<project name="LineageOS/android_device_samsung_msm8974-common" path="device/samsung/msm8974-common" remote="github" />
<project name="LineageOS/android_kernel_samsung_msm8974" path="kernel/samsung/msm8974" remote="github" />
<project name="LineageOS/android_packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
</manifest>
repo sync successful about to restart the WSL terminal run 2 commands then brunch.
Build failed 2.5 hours in - can anybody explain why (file attached)
Last edited:
Code:
<project name="TheMuppets/proprietary_vendor_samsung" path="tree/lineage-16.0/kltekor" remote="github" />That line looks wrong - You cant have "tree" in the path - It should be going into a vendor folder
Hi there,
I'm trying to compile Lineage 15.1 for LG V30 (H930)
When I execute source build/envsetup.sh && repopick -t wsl-compile I get some messages:
Must I run it with the -f flag ??
Also I have this error when running breakfast h930
Any clues?
Thx in advance
I'm trying to compile Lineage 15.1 for LG V30 (H930)
When I execute source build/envsetup.sh && repopick -t wsl-compile I get some messages:
Must I run it with the -f flag ??
Also I have this error when running breakfast h930
Any clues?
Thx in advance
jep, run the command with -f option included. maybe things are sorting itself out after that. the area around line 109 in envsetup.mk checks environment variables, particular if it's windoze (or linux / mac) you're building with. maybe you need to set this variable?
Last edited:
I executed the repopick -t wsl-compile -f and I get the following messages. Is it correct? It seems not
I executed the repopick -t wsl-compile -f and I get the following messages. Is it correct? It seems not
quoting OP: "For those still insterested in building 15.1 (ignore the repopick step): https://web.archive.org/web/20180617...-15-1-t3750175 (do not report any errors if you sync this branch, I will ignore them since I do not have the means to maintain more than one branch on wsl)"
there's nothing to pick on 15.1 nor 16.0 cause my patches were merged
I recommend a clean sync and following the steps on the link, should work unless device tree is messed up
Last edited:
Im sorry for this question for sure its a wierd one, i use my laptop for builds and i use a SSD for the system and a HDD recently i got both working inside of the laptop, is there a way to make the subsystem store the things on the HDD ?
It's already been answered. Yes. Search the thread. I think it was among the first pages
HTML:
[CODE]ninja: error: '/home/jjut/los/out/target/product/albus/obj_arm/SHARED_LIBRARIES/libqsap_sdk_intermediates/export_includes', needed by '/home/jjut/los/out/target/product/albus/obj_arm/SHARED_LIBRARIES/libqsap_shim_intermediates/import_includes', missing and no known rule to make it
21:50:56 ninja failed with: exit status 1[/CODE]Hello, how can I solve this problem?
https://review.lineageos.org/#/q/albus
not sure but device bringup isn't finished. you may want to pick the open patches. but don't report errors here if they're not strictly due to wsl.
Well so far i got it and got the source synced, but when im going to sync the device specific things i get this "error: Exited sync due to fetch errors" it dont even tell me the reason.....
I doubt there was nothing printer above the error that is not relevant. would be good to post. if device specific stuff is failing I think it might be that you messed up the roomservice step
so after getting all running this is what i get.....
14:41:59 ************************************************************
14:41:59 You are building on a case-insensitive filesystem.
14:41:59 Please move your source tree to a case-sensitive filesystem.
14:41:59 ************************************************************
14:41:59 Case-insensitive filesystems not supported
14:41:59 Failed to run java: context canceled
14:41:59 ************************************************************
14:41:59 You are building on a case-insensitive filesystem.
14:41:59 Please move your source tree to a case-sensitive filesystem.
14:41:59 ************************************************************
14:41:59 Case-insensitive filesystems not supported
14:41:59 Failed to run java: context canceled
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
115Hardware Requirements
https://source.android.com/setup/build/requirements#hardware-requirements
Setting up a Windows Subsystem for Linux build environment
21Useful resources
Get started mounting a Linux disk in WSL 2
Learn how to set up a disk mount in WSL 2 and...docs.microsoft.com
https://github.com/MicrosoftDocs/WSL/issues/412#issuecomment-57592317612WSL 2.0 is OUT, build all the droids!
Hi all,
Microsoft just released the Windows 10 May 2020 update. But the bigger news is that it comes with WSL2. The TLDR of it is that Windows now has a Linux kernel bundled with it and that's game changing. And what that means for us is out of the box / seamless linux-like functionality for all teh things (goodbye Lineage hax patches for WSL1).
I have updated OP https://xdaforums.com/showpost.php?p=75579631&postcount=1 and the useful resources post https://xdaforums.com/showpost.php?p=75579631&postcount=2 with the latest information I have so far. Note that with wsl2 using mnt is a readily available option and the wsl installation location can easily be changed as well Lots more flexibility
Lastly, wanted to say thanks to all for your patience. I started this project while I was in the middle of university. I did this "for fun" with the goal of seeing if compiling Android on Windows (via WSL) would be remotely possible and if I personally would be able to pull that off. Apparently, I did. Part of this work (added with other work I did with Lineage) allowed me to get the Android job I currently have and I'm grateful for it.
I know WSL 1 was a bit of a pain to work with and that headaches and frustration came from it. The good news, is those days are over. And the future is now.
If you have questions that are not answered already in other posts, send them through. I will be randomly checking the thread. Although given that wsl2 doesn't need anywhere near as much maintenance as wsl1 I will probably be more hands off than I used to be (e.g. update the docs for newer versions of Android or Windows, etc.).
Take care,
Uldiniad11Pie (wsl flavour) is out of the oven
Hey everyone,
TL;DR
It is now possible to build lineage-16.0 on wsl! Just follow the updated guide from start to finish (syncing 16.0 on top of 15.1 is not recommended) and enjoy.
DO NOT COMPLAIN ABOUT ANY ERRORS THAT ARE NOT STRICTLY DUE TO THE BUILD ENVIRONMENT (WSL). Many devices are not ready to build yet!
Also, as always, I recommend building on the latest version of Windows. October Update was released recently: https://www.microsoft.com/en-ca/software-download/windows10
For those still insterested in building 15.1 (ignore the repopick step): https://web.archive.org/web/2018061...ng/guide-how-to-build-lineageos-15-1-t3750175 (as mentioned in my previous announcement, do not report any errors, I will ignore them, since I do not have the means to maintain more than one branch on wsl)
Full version:
It has been some time since the last update. I apologise for the crickets.
I didn't want to write a post until I was able to guarantee I could build lineage-16.0 without issues on wsl. I downloaded the sources as soon as they were released but was unable to complete a full build for my device without cherry-picking lots of patches for it and decided against it since I wanted to reduce the scope of the errors to the build environment alone. I only recently thought of building a generic image instead (which would accomplish what I wanted). Thankfully, wsl had less problems this time cause Google were cool with updating their bison and flex prebuilts (thereby now making them 64-bit) and killed off ijar (hopefully forever). So only dex2oat needed a patch this time around
The wsl-compile-lineage-16.0 patches are merged (https://review.lineageos.org/#/q/st...h:lineage-16.0+topic:wsl-compile-lineage-16.0). So no additional steps required there. Otherwise, make sure to install m4 since it spat out an error about it missing.
Thank you for your support,
Uldiniad
P.S. Feel free to ask any questions related to this and check my previous announcements to know my goals and standards for this side-project (https://xdaforums.com/showpost.php?p=77321912&postcount=261 for example)
P.P.S. I am working on making an official wiki page on the LineageOS website which will be more convenient than this thread. I might consider leaving the thread open for feedback once it is open, but I might also consider having feedback reported via official means (JIRA probably).6Want a piece of Pie?
Hey everyone, got some news to share.
As you may have heard, the Pie is now out of the oven. Given that,
1. At the moment building android on WSL is 100% experimental
2. There seems to be little to no interest from Google and Microsoft to officially support wsl as an android build environment
3. I'm working alone with limited time and knowledge of both the android build environment and the inner workings of wsl
4. I plan on supporting the latest version of lineage available
I am therefore starting research and work on lineage-16.0 and will be leaving lineage-15.1 as it currently stands.
As windows updates come, wsl will change and may bring new unforeseen errors to the oreo build environment. Since I will not be maintaing that branch anymore, it may mean that the best option to keep building 15.1 is to not update to the latest build of windows if it causes errors. Given this situation I will be paying less attention to bug reports for 15.1 as time goes by and 16.x takes its place (especially since I do not have 15.1 synced anymore and will not be able to reproduce errors).
For 16.x, it entails I will proceed to ram my head into the wsl wall until it gives up or I do.
Hoping we'll all get a piece of the Pie,
Uldiniad
New posts
-
Development [ROM][14.0_r25][OFFICIAL] Evolution X 8.3 [03/13/2024]- Latest: yellowafro
-
