CN108376074B

CN108376074B - RancherOS ros core module transplanting method based on embedded system

Info

Publication number: CN108376074B
Application number: CN201611069177.2A
Authority: CN
Inventors: 朱小勇; 邓丽君; 郭志川; 赵然; 常乐
Original assignee: Institute of Acoustics CAS; Shanghai 3Ntv Network Technology Co Ltd
Current assignee: Institute of Acoustics CAS; Shanghai 3Ntv Network Technology Co Ltd
Priority date: 2016-11-28
Filing date: 2016-11-28
Publication date: 2020-10-23
Anticipated expiration: 2036-11-28
Also published as: CN108376074A

Abstract

The invention discloses a RancherOSros core module transplanting method based on an embedded system, which comprises the following steps: step 1) creating an interactive container based on specified parameters of a ros-built mirror image; step 2) setting system environment variables and installing a go command with the version number of 1.5; step 3), adding a compiling tool; step 4) modifying a main naming problem and adding a dependency library of the cutil. And 5) cross compiling to obtain an executable file. The method can solve the problem that the RancherOS ros core module is not matched with the embedded system; has the advantages of simple operation and strong practicability.

Description

RancherOS ros core module transplanting method based on embedded system

Technical Field

The invention relates to the field of embedded container operating systems, in particular to a RancherOS ros core module transplanting method based on an embedded system.

Background

The existing embedded system is more and more intelligent along with the development of the internet, communication and computers, and the human-computer interaction is more frequent, so that the requirements of people on the embedded system are higher and higher, and the embedded system is expected to be an environment in which multiple applications can run. However, the current embedded system is not perfect, and as the number of running applications is increased, more entrances are exposed, so that trojans, malicious software and viruses can easily invade the system; resource utilization rate: although the performance of smart devices has improved, more efficient resource management techniques are needed in the face of high-resolution video or complex graphics processing, etc.

Container virtualization technology is a great trend, and a new generation container technology represented by Docker becomes a hot spot for application security research. The Docker virtualization technology can provide a security domain and an isolated island environment for applications, effectively isolates access among the applications, and protects user private data. With the advent of Docker, many new Linux distribution versions of specialized runtime containers have emerged. The container encapsulates everything the application needs, except for the common operating system kernel, which encapsulates the runtime environment, framework and libraries, code, configuration, and related dependencies. The container greatly reduces the role of the operating system as a full-function platform. The operating system under the container now only needs to assume a very lightweight role: the vessel is activated and controlled. However, the existing container operating system is only suitable for a server side and cannot be adapted to an embedded system.

The embedded operating system based on Linux is generally different from the Linux system at the server side in that Linux is partially cut according to the characteristics and application of the embedded system.

Disclosure of Invention

The invention aims to solve the problem that a RancherOS and an embedded Linux system are not matched, embedded system configuration and RancherOS codes need to be modified, and therefore, the RancherOSros core module transplanting method based on the embedded system is provided.

In order to achieve the above object, the present invention provides a rancher os ros core module transplanting method based on an embedded system, the method comprising:

step 1) creating an interactive container based on specified parameters of a ros-built mirror image;

step 2) setting system environment variables and installing a go command with the version number of 1.5;

step 3), adding a compiling tool;

step 4) modifying a main naming problem and adding a dependency library of the cutil.

And 5) cross compiling to obtain an executable file.

In the above technical solution, the specifying parameters in step 1) includes: a parameter-i, -t, setting the container to an interactive mode; a parameter-v, mounting the shared volume according to the designated path; parameter — device, which allows the container to access the device under the specified path.

In the above technical solution, the step 2) specifically includes:

step 2-1) setting a current path BUILD-DIR;

step 2-2) setting a target architecture GOARCH of a program output by the Go compiler;

step 2-3) setting a GOOS (target operating system) operated by the compiled program;

step 2-4) setting a gcc compiled command line parameter GOGCCFLAGS when cgo is compiled;

step 2-5), setting GOPATH: a directory to be searched when the GO command is executed, wherein the directory mainly stores G O source codes and binary files;

step 2-6) setting a GOROOT installation catalog of Go language;

step 2-7) setting GOTOOLDIR: go's tool chain program under this catalog;

step 2-8) judging whether cgo is used or not;

step 2-9) installing a go command of a corresponding version number.

In the above technical solution, the compiling tool in step 3) is an arm-histvb300-linux compiler.

In the above technical solution, the step 4) specifically includes:

step 4-1) modifying the Main file of the Main folder under the folder-from-scratch folder, wherein the Main function is modified into a Main function, and the package Main is modified into a package Main;

step 4-2) modifying cgo parameter sections of the custom. go files in the util folder, adding cgo CFLAGS parameters to specify library file paths, and modifying cgo LDFLAGS parameters to specify paths of static link libraries and file names of the static link libraries;

the library files include blkid.h, libmount.h header files, libblkid.a, libmount.a, and libuiid.a static link library files.

In the above technical solution, in the compiling process of step 5), based on the command of the original core module of the rancher os for compiling ros, the parameters of GOARCH, CGO _ enable, and CC need to be added.

The invention has the advantages that:

1. the method of the invention can solve the problem that the RancherOS ros core module is not matched with the embedded system;

2. the method is simple to operate and high in practicability.

Drawings

Fig. 1 is a flowchart of a rancher os ros core module transplanting method based on an embedded system according to the present invention.

Detailed Description

The invention is described in detail below with reference to the figures and specific embodiments.

As shown in fig. 1, a rancher os ros core module transplanting method based on an embedded system sets up a system environment by independently cross-compiling the rancher os ros core module, modifies naming problems, adds a dependency library, and cross-compiles to obtain an executable file; the method specifically comprises the following steps:

the specified parameters include: a parameter-i, -t, setting the container to an interactive mode; a parameter-v, mounting the shared volume according to the designated path; parameter — device, which allows the container to access the device under the specified path.

Step 2) setting system environment variables and installing a go command with the version number of 1.5; the method specifically comprises the following steps:

step 2-1) setting a current path BUILD-DIR;

step 2-6) setting a GOROOT installation catalog of Go language;

step 2-7) setting GOTOOLDIR: go's tool chain program under this catalog;

step 2-8) judging whether cgo is used or not;

step 2-9) installing a go command of a corresponding version number.

Step 3), adding a compiling tool;

the compiling tool is an arm-histvb300-linux compiler.

and 4-2) modifying cgo parameter sections of the custom. go files in the util folder, adding cgo CFLAGS parameters to specify library file paths, and modifying cgo LDFLAGS parameters to specify paths of static link libraries and file names of the static link libraries.

And 5) cross compiling to obtain an executable file.

And on the basis of commands of an original compiling ros core module of RancherOS, GOARCH, CGO _ ENABLED and CC parameters need to be added.

One specific embodiment of the present invention is:

step 1) creating an interactive container based on specified parameters of the ros-built image, wherein the command is as follows: socket:/var/run/socket:/dev/kvm-name ═ ros-build

Step 2) setting system environment variables, wherein the setting environment variable command is as follows:

export BUILD_DIR＝$PWD

export GOARCH＝"arm"

export GOOS＝"linux"

export GOGCCFLAGS＝"-fPIC-marm-fmessage-length＝0-I/include"

export GOPATH＝/go

export GOROOT＝"/usr/local/go"

export GOTOOLDIR＝"/usr/local/go/pkg/tool/linux_amd64"

export CGO_ENABLED＝"1"

and step 3) installing a go command with the version number of 1.5.

Step 3-1), deleting the/usr/local/go folder;

step 3-2) setting GO _ VERSION environment variables, wherein the command is as follows: export GO _ VERSION ═ 1.5.1

Step 3-3) uses curl command to download go command with version number 1.5, and the command is:

curl-sSL"https://storage.googleapis.com/golang/go${GO_VERSION}.linux-amd64.t ar.gz"|tar-v-C/usr/local-xz

step 3-4), setting PATH environment variables with the following commands:

exportPATH＝$PATH:/go/bin:/usr/local/go/bin:$PATH

step 4) add arm-histvb300-linux compiler.

Step 4-1) downloading an arm-histvb300-linux compiler installation package and decompressing;

step 4-2) executing the command/cross.install and installing a go command with the version number of 1.5;

step 4-3), setting PATH environment variables with the commands of:

export PATH＝$PATH:/opt/hisi-linux/x86-arm/arm-histbv300-linux/bin

step 5) modifying the naming problem of the Main file in the Main folder under the locker-from-scratch folder, wherein the modified partial code is as follows:

and 6) adding a dependency library of the cutil.

Step 6-1) modifying the util/cutil.go file, wherein the modified partial code is as follows:

step 6-2) creating an include folder under the container/path;

step 6-3) create blkid file under/include/Path and add blkid.h under this folder

Step 6-4) creating libmount files under/include/path and adding libmount

Step 6-5) creating libs folders under the containers/paths;

step 6-6) add libblkid.a, libmount.a, libuiid.a static link libraries under the libs folder.

Step 7) cross compiling to obtain an executable file, and adding GOARCH, CGO _ ENABLED and CC parameters based on the commands of the original compiling ros core module of RancherOS, wherein the commands are as follows:

GOARCH＝arm CGO_ENABLED＝1CC＝"arm-histbv300-linux-gcc"godep go build-tags netgo-installsuffix netgo-ldflags"-X github.com/rancher/os/config.VERSION v0.4.1-dev-linkmode external-extldflags-extld＝arm-histbv300-linux-gcc"-o ros

the above description is only for the purpose of illustrating the embodiments of the present invention and should not be taken as limiting the scope of the present invention, and it should be understood by those skilled in the art that modifications and equivalents may be made without departing from the spirit and scope of the present invention and that the present invention is also covered by the scope of the present invention.

Claims

1. A RancherOS ros core module transplanting method based on an embedded system, the method comprising:

step 2) setting system environment variables and installing a GO language with a version number of 1.5;

step 3), adding a compiling tool;

Step 5), cross compiling to obtain an executable file;

the parameters specified in the step 1) comprise: a parameter-i, -t, setting the container to an interactive mode; a parameter-v, mounting the shared volume according to the designated path; parameter- -device, which allows the container to access the device under the specified path;

the step 2) specifically comprises the following steps:

step 2-1) setting a current path BUILD-DIR;

step 2-6) setting an installation catalog GOROOT of GO language;

step 2-7) setting GOTOOLDIR: the toolchain program of GO is under this catalog;

step 2-8) judging whether cgo is used or not;

step 2-9) installing GO languages with corresponding version numbers;

the step 4) specifically comprises the following steps:

step 4-2) modifying cgo parameter section of the custom. go file in the util folder, adding a path of a cgo CFLAGS parameter appointed library file, and modifying a path of a cgo LDFLAGS parameter appointed static link library and a static link library file name;

the library files include a blkid.h header file, a libmount.h header file, a libblkid.a static link library file, a libmount.a static link library file, and a libuiid.a static link library file.

2. The method for transplanting the RancherOS ros kernel module based on the embedded system of claim 1, wherein the compiling tool of step 3) is an arm-histvb300-linux compiler.

3. The method of claim 1, wherein in the compiling process of step 5), based on commands of a rancher os core module originally compiled, GOARCH, CGO _ ENABLED and CC parameters are added.