Long-Term Supported Versions

    Application Development Guide

    This document describes the common tools used for application development and guides users to develop applications based on openEuler.


    This document describes the following four parts to guide users to use openEuler and develop code based on openEuler.

    • Install and use the GCC compiler in the openEuler operating system (OS), and complete the development, compilation, and execution of simple code.
    • In the openEuler OS, use the JDK built-in tool to compile and execute code.
    • Install IntelliJ IDEA in the openEuler OS for Java development.
    • Create an RPM package locally or using the Open Build Service (OBS).

    Intended Audience

    This document is intended for all users who use the openEuler OS for code development. You are expected to have the following experience or capabilities:

    • Have basic knowledge of the Linux OS.
    • Know how to use Linux command lines.

    Symbol Conventions

    The symbols that may be found in this document are defined as follows.

    Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results.
    NOTICE is used to address practices not related to personal injury.
    Supplements the important information in the main text.
    NOTE is used to address information not related to personal injury, equipment damage, and environment deterioration.

    Command Conventions

    Table 1 Command conventions




    Command keywords, which remain unchanged in the commands, are in boldface.


    Command parameters, which are replaced with actual values in the commands, are in italic.

    [ ]

    Items in square brackets are optional.

    { x | y | ... }

    Optional items are grouped in braces and separated by vertical bars. One item is selected.

    [ x | y | ... ]

    Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.

    { x | y | ... }\*

    Optional items are grouped in brackets and separated by vertical bars. A minimum of one or a maximum of all can be selected.

    [ x | y | ... ]\*

    Optional items are grouped in brackets and separated by vertical bars. One or more items are selected or no item is selected.

    Bug Catching

    Buggy Content

    Bug Description

    Submit As Issue

    It's a little complicated....

    I'd like to ask someone.


    Just a small problem.

    I can fix it online!

    Bug Type
    Specifications and Common Mistakes

    ● Misspellings or punctuation mistakes;

    ● Incorrect links, empty cells, or wrong formats;

    ● Chinese characters in English context;

    ● Minor inconsistencies between the UI and descriptions;

    ● Low writing fluency that does not affect understanding;

    ● Incorrect version numbers, including software package names and version numbers on the UI.


    ● Incorrect or missing key steps;

    ● Missing prerequisites or precautions;

    ● Ambiguous figures, tables, or texts;

    ● Unclear logic, such as missing classifications, items, and steps.


    ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

    ● Incorrect schematic or architecture diagrams;

    ● Incorrect commands or command parameters;

    ● Incorrect code;

    ● Commands inconsistent with the functions;

    ● Wrong screenshots.

    Risk Warnings

    ● Lack of risk warnings for operations that may damage the system or important data.

    Content Compliance

    ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

    ● Copyright infringement.

    How satisfied are you with this document

    Not satisfied at all
    Very satisfied
    Click to create an issue. An issue template will be automatically generated based on your feedback.
    Bug Catching
    编组 3备份