Multi-CPU framework-supporting application software development and operation service system

Abstract

The invention discloses a multi-CPU framework-supporting application software development and operation service system. The system is divided into an operation system state, an operation state, a development state, an application state and a distribution state from bottom to top; and the system mainly comprises three parts: a multi-framework application software development and operation core framework runtime, a multi-framework application software development and operation core framework development tool and a multi-framework application software operation sandbox. The system disclosed in the invention has the advantages of standardizing the industrial standard of application software development and operation and enabling the application software packages to satisfy the application authority control requirement on the basis of the standard.

Description

technical field [0001] The invention relates to a service system, in particular to an application software development and operation service system supporting multi-CPU architecture, which belongs to the field of service systems. Background technique [0002] There are some major flaws in the current Linux desktop system, including the following four points: [0003] First, the development is severely fragmented: this is reflected in the fact that there are too many development libraries on Linux, but there is a lack of a unified development solution (similar to the Microsoft .NET framework). A direct result is that it is difficult for developers to choose the best development Language, development library and development environment. For example, for C / C++, the mainstream user interface (UI) program development includes Gtk, Qt, and WxWidget. At the same time, Gtk itself has Gtk2 and Gtk3 series, and Qt has Qt4 and Qt5. Linux application software developers often need a se...

AI Technical Summary

Problems solved by technology

This scenario solves the package risk problem to a certain extent, because package maintainers tend to choose trustworthy and functionally reliable applications, but it is also inevitable to expose some problems: upstream application developers completely rely on downstream publishers to package For the developed application, the downstream publisher decides the specific scheduling, declaration, packaging, support and other rules, and the developer often hopes for a higher release speed; the actual test of the application itself becomes very difficult, because the end user may often use many Different package versions, and hope that these versions can run under different system releases. The application is tested under a certain version of a certain release, and it is impossible to determine that the application can be used under any combination of other releases and other versions. Normal operation; to test the operation of an application under a certain version of a certain distribution, developers often need to install the environment of this version of the distribution, and compile and run the application, which will be a cumbersome task