Computers and cars are a lot of similarities, consumers do not need to understand the underlying complex, just turn on and use it on the line & mdash; & mdash; Android, Windows, OS X, and Linux, also true. Of course, after developed, they still after years of sharpening, will become more mature. But Google is developing a mysterious called & ldquo; Fuchsia & rdquo; new system, it is not such a thing.
Android Authority foreign media a few days ago wrote an introduction Fuchsia article, which contains a linkCompiler GuideLink, interested users can go there and see how to build a bootable system.
The easiest way to create Fuchsia, is to use the 64-bit Intel-based platforms Ubuntu Linux machine (of course, support compile on OS X and Debian and other Linux distributions).
If you are not familiar with Linux, touching the command line skills are relatively limited, so the job may not be very suitable. Fuchsia currently consists of two major components & mdash; & mdash; Magenta cores and toolset, libraries, and other programs.
Magenta is a small kernel (LK), so Fuchsia is also a function of the relatively limited small systems. Its mainly for embedded devices and bootloaders, supports the connection of numerous peripheral drivers, there is a & ldquo; & rdquo ;. user mode
To build Fuchsia, you need to pay attention to two aspects. The first is to build tools and libraries required to run in user space, including a man named & ldquo; mxsh & rdquo; small shell program; second is to build LK / Magenta.
After get some of these, you can start Magenta on a file system, and then use the executable user space Fuchsia.
Want to run Fuchsia, the easiest way is to use the popular open source machine emulator & ldquo; qemu & rdquo ;. In fact, Fuchsia in the source tree already contains a copy of qemu.
When you start Fuchsia, you can see a lot of kernel-level debugging information, to tell you the system start all the details related to the & mdash; & mdash; the first words & ldquo; welcome to lk / MP & rdquo ;, then the comfort of each subsystems (such as thread / timer).
Then followed by CPU detection, scheduled task, the device manager, and network component parts. After the boot is complete, you can see a man named mxsh simple shell program.
mxsh comes with some instructions, including cd (access directory), cp (copy), echo (print variable or string), ls (display the file directory) and rm (remove files or directories).
If you type a non-shell command comes, then it will attempt to run / boot / bin / path under the program of the same name. This path includes many different executable files, mostly for testing and further development of Fuchsia.
To & ldquo; thread-depth-test & rdquo; for example, it is used to test the ability to create ready-Fuchsia. There are also some simple executable files, such as fortune and cowsay.
To test the Fuchsia Dart, just follow & ldquo / boot / apps under the path; hello_fuchsia.dart & rdquo; & mdash; & mdash; Enter & ldquo; dart /boot/apps/hello_fuchsia.dart” can. (Only displayed on the console Hello, Fuchsia!)
See & ldquo;! Hello, Fuchsia & rdquo ;, means Fuchsia has been able to run complex interpretive environment and run scripts, such as process management, thread management, memory management, file I / O and so on. (This is certainly a lot of people think of Linux pre v1.0 release time)
Fuchsia OS will allow Dart play an important role, because the current version does not contain the C compiler and other high-level languages (such as Java).
Given Google has invested a lot on the Dart, which may mean that the company is to build a device running Fuchsia and will be programmed by Dart.
Of course, we do not know Fuchsia those only a few KB of memory for embedded devices. This may be a virtual reality devices, home automation products, or have access to a huge infrastructure of AI smart devices.
The idea that, Fuchsia might be a desire to compete with Windows or OS X desktop operating system, but in small series seems to be absurd, after all, it has Android and Chrome OS first.