Specific images of an OS are built using only the driver bindings that are necessary to link the OS to the particular hardware of a client device. A device tree of the client device is analyzed to identify the hardware components. Databases of different hardware source code for various hardware drivers are maintained and used to craft the driver bindings and instances for the hardware of the client device. The device tree is also analyzed to identify compatibility strings of the various hardware on the client device. The hardware source code is searched for these compatibility strings to see if a driver exists in the databases of hardware source code. Specific driver bindings and driver instances with the actual variable names and configuration parameters of the identified hardware drivers are then generated and included in an image of the OS that may be installed on the client device.

A method for executing program components on a control unit includes receiving a first program unit and a second program unit; producing a first proxy definition and a second proxy definition, wherein a proxy definition stipulates access to at least one function and/or a memory area of a program unit, wherein the first proxy definition is associated with the first program unit and the second proxy definition is associated with the second program unit; compiling the first program unit and the second program unit to produce a first program component, a second program component, a first proxy component and a second proxy component; and executing the first program component and the second program component on a control unit, wherein the first program component calls and/or uses at least one function of the second program component by using the first proxy component and the second proxy component.

A method for executing program components on a control unit includes receiving a first program unit and a second program unit; producing a first proxy definition and a second proxy definition, wherein a proxy definition stipulates access to at least one function and/or a memory area of a program unit, wherein the first proxy definition is associated with the first program unit and the second proxy definition is associated with the second program unit; compiling the first program unit and the second program unit to produce a first program component, a second program component, a first proxy component and a second proxy component; and executing the first program component and the second program component on a control unit, wherein the first program component calls and/or uses at least one function of the second program component by using the first proxy component and the second proxy component.

Systems and methods for developing one or more applications associated with a browser-based user interface within a multi-developer computing platform employ one or more processors that receive a request to build one or more applications configured to run in a browser-based user interface on a client; determine whether the one or more applications are associated with a core library and one or more runtime libraries; and in response to determining that the one or more applications are associated with the core library and the one or more runtime libraries: determine one or more version numbers associated with the one or more runtime libraries; and in response to the determined one or more version numbers being within a predetermined range associated with the core library, dynamically link the one or more runtime libraries and the one or more applications.

Systems and methods for developing one or more applications associated with a browser-based user interface within a multi-developer computing platform employ one or more processors that receive a request to build one or more applications configured to run in a browser-based user interface on a client; determine whether the one or more applications are associated with a core library and one or more runtime libraries; and in response to determining that the one or more applications are associated with the core library and the one or more runtime libraries: determine one or more version numbers associated with the one or more runtime libraries; and in response to the determined one or more version numbers being within a predetermined range associated with the core library, dynamically link the one or more runtime libraries and the one or more applications.

Specific images of an OS are built using only the driver bindings that are necessary to link the OS to the particular hardware of a client device. A device tree of the client device is analyzed to identify the hardware components. Databases of different hardware source code for various hardware drivers are maintained and used to craft the driver bindings and instances for the hardware of the client device. The device tree is also analyzed to identify compatibility strings of the various hardware on the client device. The hardware source code is searched for these compatibility strings to see if a driver exists in the databases of hardware source code. Specific driver bindings and driver instances with the actual variable names and configuration parameters of the identified hardware drivers are then generated and included in an image of the OS that may be installed on the client device.

Specific images of an OS are built using only the driver bindings that are necessary to link the OS to the particular hardware of a client device. A device tree of the client device is analyzed to identify the hardware components. Databases of different hardware source code for various hardware drivers are maintained and used to craft the driver bindings and instances for the hardware of the client device. The device tree is also analyzed to identify compatibility strings of the various hardware on the client device. The hardware source code is searched for these compatibility strings to see if a driver exists in the databases of hardware source code. Specific driver bindings and driver instances with the actual variable names and configuration parameters of the identified hardware drivers are then generated and included in an image of the OS that may be installed on the client device.

Systems, methods, devices and non-transitory, computer-readable storage mediums are disclosed for automated mobile app integration. In an embodiment, a method comprises: receiving, by a server computer from a development system, a first application binary executable for an application; receiving, by the server computer, a dataset specifying mobile services to be added to the application, the dataset selected by a user of the development system; dynamically and automatically generating a software adapter for adapting one or more plugin software components to the first app binary executable according to the dataset; generating, by the server computer and without access to source code for the first application binary executable, a second application binary executable for the application, the generating including merging the first application binary executable with binary code for the adaptor and the plugin software components; and transmitting, by the server computer to the development system, the second application binary executable.

Systems, methods, devices and non-transitory, computer-readable storage mediums are disclosed for automated mobile app integration. In an embodiment, a method comprises: receiving, by a server computer from a development system, a first application binary executable for an application; receiving, by the server computer, a dataset specifying mobile services to be added to the application, the dataset selected by a user of the development system; dynamically and automatically generating a software adapter for adapting one or more plugin software components to the first app binary executable according to the dataset; generating, by the server computer and without access to source code for the first application binary executable, a second application binary executable for the application, the generating including merging the first application binary executable with binary code for the adaptor and the plugin software components; and transmitting, by the server computer to the development system, the second application binary executable.

The invention relates to an executable file acquisition method and operation method of a heterogeneous computing system and a related product. According to the executable file obtaining method of the heterogeneous computing system, through the CPU program and the artificial intelligence processor program, the electronic device allows a user to compile a corresponding program according to needs to achieve needed functions, and the application range of a machine learning library is expanded.