Yocto Linux into Butterflies __linux

As the flagship of the Open source movement, Linux was once the hope of emerging software companies to transform the structure of traditional software industries. However, over the years, the brilliance of Linux appears to have been largely accomplished by others, such as Linux, the foundation of Android, which is popular all over the world. Linux itself, but still stealth. So, does Linux itself have a gene for take-off? It needs what kind of opportunity, can feather into butterfly, soaring.
　　
change, from genetics to the environment

Back in 1998, the open source movement was booming as it heralded the availability of software for free. This will be a revolution that has revolutionized the structure of the global software industry.

Over the years, this revolution has really happened, but if we don't think about the past, we will feel that everything is now taken for granted. Just look at the Android smartphone that many of us have in hand, and you know the software is free. Most importantly, the software base--android operating system is free.

Although Android is based on Linux, there seems to be more people in the world who know Android than people who know Linux. This explains that Linux is a gene for butterflies, because it has become a world-famous Android in the smartphone world and, on the other, has inspired us to be a butterfly in other, broader areas, and to play a bigger role in the evolution of the software industry as a whole.

Looking at the evolution of Linux to Android with a more research approach helps us to make Linux more potential in other, broader spaces. So how does Android mutate, making it stand out from traditional Linux?

Throughout the process, it's not hard to find that unification and consistency are important drivers of Linux's emergence as Android. In the area of smartphones and tablets, Linux is a powerful unifying force for Android. In other areas, engineers and teams working on Linux software development are still in the "Home workshop" situation. This is not because too many people are keen on the "Family workshop" style of development. The pain in them has a personal feeling. Starting with an operating system with only the kernel and simple networking features, 1.1-point weave a system that can work with a particular hardware environment and put into practice, a process that itself looks like someone legs while crawling. Since then, even shred changes in the hardware environment could lead to a complete overhaul and testing of the entire software system. Moreover, the process is endlessly cyclical until the end of the product lifecycle.

Against Android, this is a relatively unified, consistent Linux system. Developing an Android system is much easier than developing a Linux system, and there are fewer things to worry about, and much faster. As you can see, Linux needs to change like Android.

Yocto at the time

When time turns to 2010, the elite of the open source movement realized that unification and uniformity were at stake for Linux, and they gathered to start the Yocto program and start cultivating the spark of change for the open source community.

By providing a common build system and collaborative development technology, Yocto plans to launch a new starting point for Linux developers, with the emphasis on eliminating their waste in porting, duplicating, Recreating and maintaining these low value work time.

Over the past two years, with the support of Yocto, the people of the Linux community have become more and more robust from the initial crawl to the subsequent upright walk. One of the hallmarks of the Yocto program is the compatibility Requirements Specification (Yocto Project Compliance Requirements), which will drive change and progress in a comprehensive way.

So, what exactly is the Yocto plan? Is it a Linux distribution version? How should I use it for my Linux project?

The Yocto program is an open source collaboration program that provides the required standards and high-quality architectures, tools, and methodologies to reduce the complexity and portability of embedded Linux software projects. The Yocto program is not a Linux distribution provided by a company or organization, but many hardware and software companies have joined the YOCTO program to support embedded Linux developers to achieve better cross-platform compatibility and component interoperability. So how does the Yocto plan do that?

To build a scalable Linux system in an embedded environment, you must rely on a number of software and toolset. Imagine a situation where you can get kernel, userspace, and patch from the open source community and do your own work, such as file systems of a specific size, kernel configuration, and so on, and then apply the appropriate toolset to build a variety of specific applications, For example, for the IA architecture to do a system for the ARM architecture to do a set of systems.

It's very similar to cooking--with the same ingredients and tools, you can make different dishes by changing the proportions and the heat of the formula slightly. Now imagine that your culinary skills will be hard to come by without generic, easy-to-use tools such as kitchen knives, stoves, pans, and stir-fried shovels. In the embedded Linux world, if you don't have a yocto plan, that's what happens to you-there's no generic resources, from kernel, userspace to cross-architecture build, and no common toolset (Toolchain, makefiles, compilers, debuggers, etc.).

The Yocto program provides all that is missing, and does not leave users with a vendor lock-in. In this way, users have both high-quality standardized tools and can manage their own risks. For enterprise strategy, having independent technology choice is a necessary condition for success. The interoperability, portability, and reusability of Linux projects will benefit the development team.