CN112905173A - Engineering multiplexing implementation method based on Eclipse and integrated development environment thereof - Google Patents
Engineering multiplexing implementation method based on Eclipse and integrated development environment thereof Download PDFInfo
- Publication number
- CN112905173A CN112905173A CN202110492708.3A CN202110492708A CN112905173A CN 112905173 A CN112905173 A CN 112905173A CN 202110492708 A CN202110492708 A CN 202110492708A CN 112905173 A CN112905173 A CN 112905173A
- Authority
- CN
- China
- Prior art keywords
- file
- project
- engineering
- ide
- migration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses an Eclipse-based project multiplexing implementation method and an integrated development environment thereof, and provides concepts of project files and project set files, wherein the project files and the project set files are automatically created during project creation, the project files or the project set files can be loaded by double clicking the project files or the project set files, multiplexing of project combinations defined in project set can be realized, and a function of efficient migration of the project set across hosts is realized, so that the integrated development work is more convenient, the time cost is reduced, and the development work efficiency is improved.
Description
Technical Field
The invention relates to a software program development technology, in particular to an Eclipse-based engineering multiplexing implementation method.
Background
With the continuous flourishing development of RISC-V ecology in recent years, more and more scientific and technological majors strive for the arrangement of the original companies, and the industrial application falls into the ground. RISC-V kernel embedded Integrated Development Environment (IDE), which plays an important role in the industrial ecology, has also been in the era of "all flowers.
In various existing integrated development platforms, Eclipse has the controllability of free sources; the convenience of modular architecture and plug-in development wins the favor of numerous developers. A plurality of manufacturers have launched an integrated development environment that is developed based on the Eclipse platform.
The RISC-V kernel embedded integrated development environment based on the Eclipse platform in the industry at present has the following defects:
1. when loading the target embedded engineering each time, a user needs to open an IDE interface first and then import the engineering through the interface provided by the IDE. The loading engineering operation is long in time consumption and does not accord with the operation habit that most embedded development engineers open the engineering in the IDE by double-clicking the engineering files with specific suffixes.
2. The project set and IDE interface configuration are stored in the current active working space, if the user needs to reuse part of the project in the current project set in another project, the IDE only provides an interface for copying the current complete project set, and the user needs to manually switch the new working space and delete redundant projects or re-create the working space and import the projects one by one. Flexible engineering set multiplexing service cannot be provided, and the time cost of a user is increased.
3. The work space stores the local absolute path information of the project source codes in the form of binary files, each project corresponds to one binary file, and the type of file directory is deep. When project development needs to be carried out on the engineering set on another host, a user has only two options: (1) copying source codes of all projects to a new host, and then sequentially importing the source codes to the same working space by using an IDE interface to form a new project set, wherein all user-defined interface configurations in the original IDE can be lost; (2) copying the old working space and all the engineering source codes to a new host, and respectively moving the engineering source codes to absolute paths completely matched with the engineering source codes according to the binary source code position information corresponding to each engineering so as to normally load the engineering set in the working space. Neither solution enables efficient cross-host engineering set migration operations.
Disclosure of Invention
The purpose of the invention is as follows: in order to solve the problem that the IDE based on the Eclipse platform in the prior art cannot flexibly multiplex engineering combination in a working space, the invention provides an engineering multiplexing implementation method based on the Eclipse.
Another object of the present invention is to provide an Eclipse-based IDE that can implement engineering multiplexing.
The technical scheme is as follows: a project multiplexing implementation method based on Eclipse comprises a local multiplexing method and specifically comprises the following steps:
creating an original project set in a working space, wherein the original project set comprises at least two projects, and creating an original project set file according to the project set file creating step; determining the projects in the original project set to be multiplexed, selecting the projects to be multiplexed, and creating a multiplexed project set file according to the project set file creating step; when the multiplexing project set needs to be loaded, executing the project set loading step;
the engineering set file creating step comprises: the project set file contains a project set file specific suffix name, and the default opening mode of the file containing the project set file specific suffix name is bound as a file loader; the project set file comprises absolute paths and unique identification codes of all project source code storage addresses in the project set, and the unique identification codes of different project sets are different;
the engineering set loading step comprises the following steps: double-clicking the project set file, acquiring a full path name of the project set file by the file loader, judging whether the project set file is the project set file or not through a suffix name, and reading registry information by the file loader to acquire an IDE installation position if the project set file is confirmed;
the file loader searches whether an active process with the same name as the IDE exists or not, if so, a communication file is created in a directory where the IDE executable file is located, the file loader reads the unique identification code and writes the unique identification code into the communication file, the IDE is maximized and set to a top-layer window, and a circular waiting mode is entered; the IDE monitoring task plug-in detects a communication file, when the communication file is detected, the unique identification code in the communication file is read and compared with the unique identification code of the currently active engineering set, and if the unique identification code and the unique identification code are the same, the communication file and the file loader process are actively destroyed; if the two are different, prompting to save the currently active engineering set, closing the IDE and destroying the communication file; the file loader detects the IDE process, if the IDE process is destroyed, the loop waiting mode is exited, and the step of loading the engineering set is executed; if the file loader does not find the active process with the same name as the IDE, directly executing the step of loading the engineering set;
the step of loading the engineering set comprises the following steps: creating a temporary configuration file in a directory where the IDE executable file is located, completely writing the content in the engineering set file into the temporary configuration file, then creating an IDE process, setting the directory where the engineering set file is located as an active working space, detecting the temporary configuration file by the IDE monitoring task plug-in, and reading the content of the temporary configuration file and deleting the temporary configuration file if the temporary configuration file is detected; and loading all projects in the project set through the absolute path of the project source code storage address.
Further, the engineering set file also comprises a migration identifier, wherein the migration identifier is used for indicating whether the engineering set file is in native reuse or is migrated across hosts; when the migration identifier is true, calling an IDE import engineering interface in a directory where the engineering set file is located; when the migration identifier is false, calling an IDE import engineering interface according to each engineering source code directory recorded in the temporary configuration file, and sequentially loading the engineering; the migration identifier is set to false by default when the project set file is created and set to true when the project migrates across hosts.
Further, the method for migrating the cross-host computer also comprises the following steps:
step a1, selecting the engineering combination to be migrated in the local machine, respectively inquiring the position of the engineering source code of the selected engineering through an interface provided by an IDE, and copying the directory of the engineering source code to the appointed packing path;
step a2, creating a migration project set file under a packaging path, setting a migration identifier in the migration project set file to true, and writing the position information and the unique identification code of the project source code of the selected project relative to the migration project set file into the migration project set file respectively;
step a3, calling a compression algorithm to pack all files under the packing path to generate a migration file;
step a4, copying the migration files on a new host computer with IDE, decompressing the migration files, opening the migration project set files, and loading all the migrated projects.
Further, step a2 also includes writing the IDE interface configuration file in the current workspace to the migration engineering set file.
Further, when the project in the original project set is created, the method further comprises the steps of creating a project file: creating a project file with the same name after a new project is built in the IDE, wherein the project file comprises a specific suffix name of the project file, and the default opening mode of the file containing the specific suffix name of the project file is bound as a file loader; the engineering files are stored in a root directory of the engineering source codes, and the engineering files contain chip manufacturers, series, models and description information corresponding to engineering.
Further, when a project needs to be loaded, the project is loaded by using the project file, and the method comprises the following steps:
b1, double-clicking the project file, the file loader acquiring the full path name of the project file, judging whether the project file is the project file or not through the suffix name, and if the project file is confirmed, the file loader reading the registry information to acquire the IDE installation position;
step b2, creating a temporary configuration file in the directory where the IDE executable file is located, and writing the directory where the project file is located into the temporary configuration file; the file loader searches whether an active process with the same name as the IDE exists or not, if so, the IDE is maximized and is set to a top-layer window, if not, the IDE process is established, and a preset directory is set as an active working space;
step b3, the IDE monitoring task plug-in detects the temporary configuration file, when the temporary configuration file is detected, the position information of the project file in the temporary configuration file is automatically read and then the temporary configuration file is deleted, the project source code and the project file are in the same level directory, the project source code is found through the position information of the project file, the IDE is called to be led into the project interface, and the project is loaded.
An Eclipse-based integrated development environment comprises a storage medium, a processor and a computer program which is stored on the storage medium and can be executed on the processor, wherein the processor realizes the Eclipse-based engineering multiplexing implementation method when executing the computer program.
Compared with the prior art, the engineering multiplexing implementation method based on Eclipse and the IDE thereof provided by the invention have the following advantages:
1. support fast loading of engineering/engineering sets and take into account the operating habits of most embedded engineers. While keeping the original entrance of IDE lead-in project, the concept of project file and project set file is put forward on Eclipse platform, and the project and project set can be opened quickly by directly double-clicking the two files with special suffix name.
2. And flexible and convenient engineering multiplexing service is supported. When the IDE icon or the project file is double-clicked, a certain default directory is used as the currently active working space of the IDE, and all loaded projects can be automatically added into a default project set. When closing IDE, inquiring whether user creates self-defined project set on the basis of current project set, user can freely appoint multiplex project combination, project set file name, whether current IDE interface configuration is reserved and storage directory of multiplex project set; when the project set file is double-clicked, the IDE is controlled to automatically set the directory where the file is located as an active working space, and projects outside the project set are loaded at the moment, so that the projects cannot be automatically added into the current project set. Each time the IDE is turned off, the user is asked whether to save the modifications to the current engineering set or to spool them as a new engineering set.
3. Supporting efficient cross-host engineering set migration operations. The method provides a function of 'one-key migration of the engineering set', and the engineering source codes, the engineering set files and the like can be compressed into the migration packet only by specifying the engineering combination to be migrated in the current engineering set and exporting the name of the engineering set and the migration packet after migration. After copying and decompressing, double-clicking the designated file can lead the migration engineering set to the IDE of another host, thereby simplifying the migration work of the engineering set across the hosts, leading the integrated development work to be more convenient, reducing the time cost and improving the development work efficiency.
Drawings
FIG. 1 is a process of creating project files, project set files;
FIG. 2 is a method of engineering, engineering set loading;
FIG. 3 is a method of engineering set cross-host migration;
FIG. 4 is a flow diagram of development work using the IDE in an embodiment.
Detailed Description
The invention is further explained below with reference to the figures and the specific embodiments.
An Eclipse-based integrated development environment comprises a storage medium, a processor and a computer program which is stored on the storage medium and can be executed on the processor, wherein the processor realizes the Eclipse-based engineering multiplexing implementation method when executing the computer program.
The Eclipse-based integrated development environment comprises project files and a project set file creating unit: the implementation is realized by an Eclipse plug-in mode; an engineering set migration unit: the implementation is realized by an Eclipse plug-in mode; a suffix name binding unit: the method is realized by a software installation script mode (or an executable file); a loader unit: the method is realized by an executable file + Eclipse plug-in mode.
In this embodiment, the suffix name of the engineering file is wvproj, and the suffix name of the engineering set file is wvsln, and whether the file is an engineering file, or another file can be determined according to the suffix name.
A flow diagram of development work using the IDE in an embodiment is shown in FIG. 4, which illustrates the flow of engineering native multiplexing and cross-host multiplexing. An Eclipse-based engineering multiplexing implementation method is established on an Eclipse-based IDE and is implemented, and comprises a native multiplexing method and a cross-host migration method. The local reuse only reuses partial projects in the original project, and the cross-host migration can be partial projects in the original project or the whole project set.
1. The method for multiplexing the mobile phone specifically comprises the following steps:
and (3) creating an original engineering set in a working space C:/MRS _ DATA directory, using an engineering template built in MRS, respectively creating engineering of three RISC-V kernel chips CH32V103, CH569 and CH573, selecting and storing engineering source codes in a default working space, and creating engineering files of CH32V103.wvproj, CH569.wvproj and CH573.wvproj in the three engineering source code directories at the moment. When a main form button is closed, an original project set file is created according to the project set file creating step in the step C:/MRS _ DATA; determining the project in the original project set needing to be multiplexed, selecting the project needing to be multiplexed, creating a multiplexed project set file according to the project set file creating step, for example, if we need to multiplex CH569 and CH573 projects, selecting the two projects, creating a multiplexed project set file Test1.wvsln, storing the multiplexed project set file Test1.wvsln in a multiplexed directory D:/Folder1, and also storing the metadata Folder of the current IDE configuration file in a D:/Folder1 directory; when a multiplexing project set needs to be loaded, executing a project set loading step to load CH569 and CH573 projects;
as shown in fig. 1, the engineering set file creating step includes: the project set file contains a project set file specific suffix name wvsln, and the default opening mode of the wvsln is bound as a specified file loader under an installation path; the project set file comprises absolute paths and unique identification codes of all project source code storage addresses in the project set, and the unique identification codes of different project sets are different;
as shown in fig. 2, the engineering set loading step includes: double-clicking the project set file, acquiring a full path name of the project set file by the file loader, judging whether the project set file is the project set file or not through a suffix name, and reading registry information by the file loader to acquire an IDE installation position if the project set file is confirmed;
the file loader searches whether an active process with the same name as the IDE exists or not, if so, a communication file is created in a directory where the IDE executable file is located, the file loader reads the unique identification code and writes the unique identification code into the communication file, the IDE is maximized and set to a top-layer window, and a circular waiting mode is entered; the IDE monitoring task plug-in detects a communication file, when the communication file is detected, the unique identification code in the communication file is read and compared with the unique identification code of the currently active engineering set, and if the unique identification code and the unique identification code are the same, the communication file and the file loader process are actively destroyed; if the two are different, prompting to save the currently active engineering set, closing the IDE and destroying the communication file; the file loader detects the IDE process, if the IDE process is destroyed, the loop waiting mode is exited, and the step of loading the engineering set is executed; if the file loader does not find the active process with the same name as the IDE, directly executing the step of loading the engineering set;
the step of loading the engineering set comprises the following steps: creating a temporary configuration file in a directory where the IDE executable file is located, completely writing the content in the engineering set file into the temporary configuration file, then creating an IDE process, setting the directory where the engineering set file is located as an active working space, detecting the temporary configuration file by the IDE monitoring task plug-in, and reading the content of the temporary configuration file and deleting the temporary configuration file if the temporary configuration file is detected; and loading all projects in the project set through the absolute path of the project source code storage address.
2. For the cross-host migration method, a migration identifier needs to be added to the engineering set file. The migration identifier is used for representing whether the engineering set files are multiplexed on the local machine or migrated across the host machine; when the migration identifier is true, calling an IDE import engineering interface in a directory where the engineering set file is located; when the migration identifier is false, calling an IDE import engineering interface according to each engineering source code directory recorded in the temporary configuration file, and sequentially loading the engineering; the migration identifier is set to false by default when the project set file is created and set to true when the project migrates across hosts.
As shown in fig. 3, the cross-host migration method specifically includes the following steps:
(a1) selecting a project combination needing to be migrated in the local computer, if the project needing to be migrated is a project CH32V103 and a project CH569 in the embodiment, respectively inquiring the positions of project source codes of the selected project through an interface provided by an IDE (integrated drive electronics) and copying a directory where the project source codes are located to a specified packing path E:/Folder2, wherein the directory where the project source codes are located is copied, namely all files under the directory are copied to the specified packing path;
(a2) creating a migration engineering set file Test2.wvsln under a packaging path, setting a migration identifier in the migration engineering set file, respectively writing the position information and the unique identifier of the engineering source code of the selected engineering relative to the migration engineering set file into the migration engineering set file, and optionally writing the IDE interface configuration file in the current working space into the migration engineering set file together according to the requirement;
(a3) calling a compression algorithm to pack all files under the packing path to generate a migration file Test2. zip;
(a4) copying the migration file on a new host with IDE, decompressing the migration file, double-clicking the migration project set file Test2.wvsln, and loading the migrated CH32V103 and CH569 projects.
In order to load a project conveniently, project files can be automatically created during project creation, as shown in fig. 1, that is, after a project is newly created in an IDE, project files with the same name are created, the project files include a specific suffix name of the project files, and a default opening mode of the file containing the specific suffix name of the project files is bound as a file loader; the engineering files are stored in a root directory of the engineering source codes, and the engineering files contain chip manufacturers, series, models and description information corresponding to engineering. When the project file is double-clicked, the project can be loaded, as shown in fig. 2, specifically including the following steps:
(b1) double-clicking the project file, acquiring a full path name of the project file by the file loader, judging whether the project file is the project file or not through a suffix name, and reading registry information by the file loader to acquire an IDE installation position if the project file is confirmed;
(b2) creating a temporary configuration file in a directory where the IDE executable file is located, and writing the directory where the project file is located into the temporary configuration file; the file loader searches whether an active process with the same name as the IDE exists or not, if so, the IDE is maximized and is set to a top-layer window, if not, the IDE process is established, and a preset directory is set as an active working space;
(b3) the IDE monitoring task plug-in detects the temporary configuration file, when the temporary configuration file is detected, the position information of the engineering file in the temporary configuration file is automatically read, the temporary configuration file is deleted, the engineering source code and the engineering file are in the same level directory, the engineering source code is found through the position information of the engineering file, the IDE is called to be led into an engineering interface, and the engineering is loaded.
Claims (7)
1. A project multiplexing implementation method based on Eclipse is characterized by comprising a local multiplexing method, and specifically comprising the following steps:
creating an original project set in a working space, wherein the original project set comprises at least two projects, and creating an original project set file according to the project set file creating step; determining the projects in the original project set to be multiplexed, selecting the projects to be multiplexed, and creating a multiplexed project set file according to the project set file creating step; when the multiplexing project set needs to be loaded, executing the project set loading step;
the engineering set file creating step comprises: the project set file contains a project set file specific suffix name, and the default opening mode of the file containing the project set file specific suffix name is bound as a file loader; the project set file comprises absolute paths and unique identification codes of all project source code storage addresses in the project set, and the unique identification codes of different project sets are different;
the engineering set loading step comprises the following steps: double-clicking the project set file, acquiring a full path name of the project set file by the file loader, judging whether the project set file is the project set file or not through a suffix name, and reading registry information by the file loader to acquire an IDE installation position if the project set file is confirmed;
the file loader searches whether an active process with the same name as the IDE exists or not, if so, a communication file is created in a directory where the IDE executable file is located, the file loader reads the unique identification code and writes the unique identification code into the communication file, the IDE is maximized and set to a top-layer window, and a circular waiting mode is entered; the IDE monitoring task plug-in detects a communication file, when the communication file is detected, the unique identification code in the communication file is read and compared with the unique identification code of the currently active engineering set, and if the unique identification code and the unique identification code are the same, the communication file and the file loader process are actively destroyed; if the two are different, prompting to save the currently active engineering set, closing the IDE and destroying the communication file; the file loader detects the IDE process, if the IDE process is destroyed, the loop waiting mode is exited, and the step of loading the engineering set is executed; if the file loader does not find the active process with the same name as the IDE, directly executing the step of loading the engineering set;
the step of loading the engineering set comprises the following steps: creating a temporary configuration file in a directory where the IDE executable file is located, completely writing the content in the engineering set file into the temporary configuration file, then creating an IDE process, setting the directory where the engineering set file is located as an active working space, detecting the temporary configuration file by the IDE monitoring task plug-in, and reading the content of the temporary configuration file and deleting the temporary configuration file if the temporary configuration file is detected; and loading all projects in the project set through the absolute path of the project source code storage address.
2. The Eclipse-based project multiplexing implementation method of claim 1, wherein the project set files further comprise a migration flag, the migration flag being used to indicate whether the project set files are multiplexed locally or migrated across hosts; when the migration identifier is true, calling an IDE import engineering interface in a directory where the engineering set file is located; when the migration identifier is false, calling an IDE import engineering interface according to each engineering source code directory recorded in the temporary configuration file, and sequentially loading the engineering; the migration identifier is set to false by default when the project set file is created and set to true when the project migrates across hosts.
3. The Eclipse-based engineering multiplexing implementation method of claim 2, further comprising a cross-host migration method, specifically comprising the steps of:
step a1, selecting the engineering combination to be migrated in the local machine, respectively inquiring the position of the engineering source code of the selected engineering through an interface provided by an IDE, and copying the directory of the engineering source code to the appointed packing path;
step a2, creating a migration project set file under a packaging path, setting a migration identifier in the migration project set file to true, and writing the position information and the unique identification code of the project source code of the selected project relative to the migration project set file into the migration project set file respectively;
step a3, calling a compression algorithm to pack all files under the packing path to generate a migration file;
step a4, copying the migration files on a new host computer with IDE, decompressing the migration files, opening the migration project set files, and loading all the migrated projects.
4. The Eclipse-based engineering multiplexing implementation method of claim 3, wherein the step a2 further comprises writing the IDE interface configuration file in the current workspace to the migration engineering set file.
5. The Eclipse-based project multiplexing implementation method of any one of claims 1 to 4, wherein when creating the project in the original project set, the method further comprises a project file creating step of: creating a project file with the same name after a new project is built in the IDE, wherein the project file comprises a specific suffix name of the project file, and the default opening mode of the file containing the specific suffix name of the project file is bound as a file loader; the engineering files are stored in a root directory of the engineering source codes, and the engineering files contain chip manufacturers, series, models and description information corresponding to engineering.
6. The Eclipse-based engineering multiplexing implementation method of claim 5, wherein when a certain project needs to be loaded, the project is loaded by using project files, comprising the following steps:
b1, double-clicking the project file, the file loader acquiring the full path name of the project file, judging whether the project file is the project file or not through the suffix name, and if the project file is confirmed, the file loader reading the registry information to acquire the IDE installation position;
step b2, creating a temporary configuration file in the directory where the IDE executable file is located, and writing the directory where the project file is located into the temporary configuration file; the file loader searches whether an active process with the same name as the IDE exists or not, if so, the IDE is maximized and is set to a top-layer window, if not, the IDE process is established, and a preset directory is set as an active working space;
step b3, the IDE monitoring task plug-in detects the temporary configuration file, when the temporary configuration file is detected, the position information of the project file in the temporary configuration file is automatically read and then the temporary configuration file is deleted, the project source code and the project file are in the same level directory, the project source code is found through the position information of the project file, the IDE is called to be led into the project interface, and the project is loaded.
7. An Eclipse-based integrated development environment, comprising a storage medium, a processor and a computer program stored on the storage medium and executable on the processor, wherein the processor implements the Eclipse-based engineering multiplexing implementation method according to any one of claims 1-6 when executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110492708.3A CN112905173B (en) | 2021-05-07 | 2021-05-07 | Engineering multiplexing implementation method based on Eclipse and integrated development environment thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110492708.3A CN112905173B (en) | 2021-05-07 | 2021-05-07 | Engineering multiplexing implementation method based on Eclipse and integrated development environment thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112905173A true CN112905173A (en) | 2021-06-04 |
| CN112905173B CN112905173B (en) | 2021-08-06 |
Family
ID=76109014
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110492708.3A Active CN112905173B (en) | 2021-05-07 | 2021-05-07 | Engineering multiplexing implementation method based on Eclipse and integrated development environment thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112905173B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113094033A (en) * | 2021-06-07 | 2021-07-09 | 南京沁恒微电子股份有限公司 | Engineering structure adaptation method of MCU integrated development environment |
| CN115033266A (en) * | 2022-08-12 | 2022-09-09 | 深圳华龙讯达信息技术股份有限公司 | IDE development system based on Loongson instruction set |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101763258A (en) * | 2009-12-31 | 2010-06-30 | 深圳联友科技有限公司 | Software multiplexing method and system |
| CN102193793A (en) * | 2010-03-02 | 2011-09-21 | 腾讯科技（深圳）有限公司 | Method and device for realizing software reusability |
| CN110083749A (en) * | 2019-04-11 | 2019-08-02 | 艾伯资讯（深圳）有限公司 | The retrieval quickly developed for software, multiplexing, environmental structure system and method |
| CN110647326A (en) * | 2019-09-20 | 2020-01-03 | 中国银行股份有限公司 | NuGet program package-based software multiplexing method, device and system |
-
2021
- 2021-05-07 CN CN202110492708.3A patent/CN112905173B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101763258A (en) * | 2009-12-31 | 2010-06-30 | 深圳联友科技有限公司 | Software multiplexing method and system |
| CN102193793A (en) * | 2010-03-02 | 2011-09-21 | 腾讯科技（深圳）有限公司 | Method and device for realizing software reusability |
| CN110083749A (en) * | 2019-04-11 | 2019-08-02 | 艾伯资讯（深圳）有限公司 | The retrieval quickly developed for software, multiplexing, environmental structure system and method |
| CN110647326A (en) * | 2019-09-20 | 2020-01-03 | 中国银行股份有限公司 | NuGet program package-based software multiplexing method, device and system |
Non-Patent Citations (1)
| Title |
|---|
| 狼人: "在Eclipse中的Android项目里实现代码复用", 《HTTPS://WWW.CNBLOGS.COM/WAW/ARCHIVE/2011/08/28/2156653.HTML》 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113094033A (en) * | 2021-06-07 | 2021-07-09 | 南京沁恒微电子股份有限公司 | Engineering structure adaptation method of MCU integrated development environment |
| CN113094033B (en) * | 2021-06-07 | 2021-08-27 | 南京沁恒微电子股份有限公司 | Engineering structure adaptation method of MCU integrated development environment |
| CN115033266A (en) * | 2022-08-12 | 2022-09-09 | 深圳华龙讯达信息技术股份有限公司 | IDE development system based on Loongson instruction set |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112905173B (en) | 2021-08-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112905173B (en) | Engineering multiplexing implementation method based on Eclipse and integrated development environment thereof | |
| CN109491695B (en) | Incremental updating method for integrated android application | |
| CN109783117B (en) | Mirror image file making and starting method of diskless system | |
| US5623661A (en) | System for and method of providing delta-versioning of the contents of PCTE file objects | |
| CN1329836C (en) | Method for locating program abnormity | |
| CN103077043B (en) | A kind of method of quick Start-up and operating performance Linux | |
| WO2018045733A1 (en) | Method for loading android system so files, and electronic device | |
| JPH0836488A (en) | Method and device for checking run-time error using dynamic patching | |
| CN105988843A (en) | Firmware upgrade method and firmware upgrade device for mobile terminal | |
| JP4086791B2 (en) | Compiler program, dynamic compiler program, reproduction compiler program, reproduction compiler, compilation method, and recording medium | |
| CN104731622A (en) | Application program loading method and device and mobile terminal | |
| CN103324505A (en) | Method for deploying GPU (graphic processor unit) development environments in cluster system and could computing system | |
| US20120185682A1 (en) | Method and system for post-build modification of firmware binaries to support different hardware configurations | |
| CN101620542A (en) | Compatible updating method of ultrasonic imaging equipment software data | |
| CN101330695A (en) | Mobile terminal as well as system upgrade method and device thereof | |
| WO2023169164A1 (en) | Method and apparatus for restoring application program, and computer device and storage medium | |
| CN113656040A (en) | Program component debugging and updating method and corresponding device, equipment and medium | |
| CN100365572C (en) | Software packaging method | |
| FR2799285A1 (en) | Memory arrangement for portable data carrier e.g. chip card, updates information following deactivation process in such way, that referenced memory areas cover joined memory area | |
| CN113094033B (en) | Engineering structure adaptation method of MCU integrated development environment | |
| US20100036891A1 (en) | Apparatus and method for collecting logging information, and computer-readable recording medium in which a logging information collecting program is stored | |
| CN112579545B (en) | Linux file system mounting method and storage medium | |
| KR100652616B1 (en) | Booting time shortening method for mobile communication terminal | |
| JP2005251045A (en) | Information processor, housing position management method, and program | |
| KR20000003162A (en) | Effective operation method of flash memory |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |