On October 2, 2018, Microsoft announced that the availability of the Windows 10 October 2018 Update. This post will cover what you can expect to see in WSL for the October 2018 Update, Windows 10 version 1809, and from recent Windows Insiders builds. You can find additional information on our detailed release notes.
Mind you, as you can see in the previous news item, 1809 was pulled and hasn’t been rereleased yet. I’m not entirely sure why this blog post detailing these changes is still up without acknowledging that.
I tried a dozen times on various releases and none of them have been able to complete an Android build.
Have you successfully built Android in native Linux? Have you compared identical versions of the same distro on WSL versus native Linux?
I ask, because large, complicated builds like that are extremely dependent on the build environment.
For example, I just built successfully Minix on Debian under WSL, but it failed when I did it in Ubuntu (or was it OpenSuse?)
Also, I’ve built Linux From Scratch multiple times on native Linux, and that routinely fails on one distro or another, just because it’s such a complicated build.
Even that one, you build the build environment twice to completely isolate it from the host system, and even then it can fail in unpredictable ways.
That’s not a bug, it’s a feature!
I switched over from Cygwin and an Ubuntu 18 VM to using WSL for development. As a Linux environment, it seems quite solid, although I’m not trying to run Linux services or anything like that.
I’m using ConsoleZ https://github.com/cbucher/console as my console.
The only disappointing thing about WSL is how Windows apps “can’t” manipulate files in the WSL filesystem. That said, I’m using the Windows version of SublimeText as my editor there, with only a few problems so far:
* Sometimes edited files get mode 0000, which is irritating. At least it doesn’t blow away the owner/group, so it’s easy enough to fix.
* If you create a new file, it’s invisible to WSL. Need to create it from the command-line, then edit it in SublimeText.
* There’s no approved method for converting from a WSL filesystem path to a Windows path, so I can’t tell SublimeText to open a file. There’s a WSL utility for converting UNIX paths (like /mnt/c/Users) to Windows paths (like c:/Users or c:\Users) but it doesn’t fill in the really long path to the WSL filesystem.