CN113094033A - Engineering structure adaptation method of MCU integrated development environment - Google Patents
Engineering structure adaptation method of MCU integrated development environment Download PDFInfo
- Publication number
- CN113094033A CN113094033A CN202110628976.3A CN202110628976A CN113094033A CN 113094033 A CN113094033 A CN 113094033A CN 202110628976 A CN202110628976 A CN 202110628976A CN 113094033 A CN113094033 A CN 113094033A
- Authority
- CN
- China
- Prior art keywords
- engineering
- mode
- mapping
- directory
- file
- 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/33—Intelligent editors
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses an engineering structure adaptation method of an MCU integrated development environment, which receives an engineering structure mode switching command, wherein the engineering structure mode comprises a logic mapping mode and an entity package management mode; switching the mode of the engineering structure according to the mode switching command, and updating a mode identifier, wherein the mode identifier is stored in an engineering file and is used for distinguishing the engineering structure mode; and executing commands of adding, deleting and moving resources in the switched engineering structure mode, wherein the resources comprise a logic directory, an entity directory and a file. The invention can flexibly switch two engineering structures according to the application scene under the condition of not influencing the compiling, programming and debugging of the program, thereby facilitating the resource management and the export of the engineering package; the use habits of different users are compatible, the degree of freedom is expanded, and the use is more convenient and efficient.
Description
Technical Field
The invention relates to the field of MCU integrated development, in particular to an engineering structure adaptation method of an MCU integrated development environment.
Background
With the continuous expansion of RISC-V open source instruction architecture, chip industries at home and abroad glow with lasting vitality. In order to facilitate hardware engineers to develop chip schemes conveniently and efficiently, many chip manufacturers are focusing on developing an integrated development environment for independent development.
An Integrated Development Environment (IDE) is a developer-oriented software environment that supports basic code editing, compilation, and programming debugging. In addition, the IDE generally integrates diversified upper computer tools, so that a developer can conveniently analyze and control the IDE. The software framework can be generalized to three dimensions of storage, snoop control and interface. How to display and manage the engineering structure is a ring of the foundation in storage design.
In the mainstream C/C + + integrated development environment of the embedded field, the directory is a representation form of a logic branch. Taking the example of a Keil MDK, some common directories in the routine named source, link, debug do not really exist in the actual disk directory. The files under these logical branches are recorded in the form of links, and the actual paths can be scattered anywhere on the disk. This resource schema is described herein as a "logical mapping schema". Before a developer builds a project, files at different positions need to be sequentially added into a created logic directory, and a project script can automatically record the corresponding relation between logic and an entity. The method conforms to the development habit of most embedded engineers, but has the defect that the position of the mapped file in the cross-host file system cannot be ensured to be unchanged in the migration engineering scene. During the collaborative development process, the dispersed files in the logic mapping mode are not beneficial to the movement of engineering storage. This is clearly a pain point.
The Eclipse framework has been favored by many developers for its open source extensibility and support of multiple languages. In the development related to Java, the resource mode of the system takes the characteristics of Java into full consideration, and a mode that an engineering internal structure corresponds to a packet structure is adopted. The "package" is an entity folder in the resource manager, the internal structure is described as a tree in the engineering browser in the interface, and the resource mode is described as an "entity package management mode" in this document. Compared with the MDK form, the 'entity package management mode' encapsulates resources required by the whole project, is beneficial to centralized storage and movement, but has the following defects:
1. files irrelevant to the project are added under the corresponding local browser folder and can be reflected in the project browser. The "entity package management schema" does not conform to the industry concept that a project set contains only project-related files.
2. In the "entity package management mode", when a project or a directory is deleted from a resource tree, all subfiles corresponding to the entity directory are deleted. For users who are not used to or do not know about entity directory management, source codes are easy to delete mistakenly, and project deletion even can not be recovered. This affects the use of most users that have become accustomed to embedded mainstream IDE.
3. All engineering resources must be located within the engineering folder. And when a plurality of projects exist, the code multiplexing is not facilitated, and the degree of freedom is poor.
Disclosure of Invention
The purpose of the invention is as follows: in order to solve the problem that the engineering structure of the integrated development environment is inconvenient to manage and use in the prior art, the invention provides an engineering structure adaptation method of an MCU integrated development environment.
The technical scheme is as follows: the invention provides an engineering structure adaptation method of an MCU integrated development environment, which comprises the following steps:
receiving an engineering structure mode switching command, wherein the engineering structure mode comprises a logic mapping mode and an entity package management mode; in the logical mapping mode, the project directory does not really exist in the local system, the project files are scattered at a plurality of positions of the local system, the project files comprise mapping records, the mapping records comprise logical paths and mapping paths, the logical paths reflect the structural relationship of the project files, and the mapping paths are the actual positions of the project files in the local system; in the entity package management mode, the project directory corresponds to a project folder in the local system, and the project files correspond to files in the project folder;
step two, switching the mode of the engineering structure according to the mode switching command, when receiving a command for switching to a logical mapping mode, executing depth-first traversal by a processor under an engineering directory, filtering out configuration files and output directories which are irrelevant to mapping and do not need to be displayed in the engineering directory, recording the logical paths and mapping paths of other files, changing the path represented by the original engineering variable in engineering configuration into a relative path, wherein the relative path is a path of the engineering variable relative to the same-level directory of the engineering, and importing the path into a working space through a loading interface; when receiving a command of switching to an entity package management mode, a processor reads a mapping record in an engineering file, calculates an absolute path of the engineering file, creates a new folder in an engineering peer directory when the position of the mapped file does not exist in the engineering peer directory, and copies the mapped file into the new folder;
step three, updating a mode identifier, wherein the mode identifier is stored in an engineering file and is used for distinguishing engineering structure modes;
and step four, executing commands of adding, deleting and moving resources in the switched engineering structure mode, wherein the resources comprise a logic directory, an entity directory and files.
Further, in the first step, the engineering structure mode switching command may be triggered by an external input or triggered according to a specific condition, where the external input trigger does not limit the scene, and the specific condition is: when the project package is exported, the popup suggestion is initiated to be switched to the entity package management mode, and after the confirmation, the popup suggestion is switched to the entity package management mode, and when the project package is imported, the popup suggestion is initiated to select to keep the entity package management mode or switch to the logic mapping mode.
Furthermore, in step four, the logical mapping mode and the entity packet management mode share a set of interface, and the same command is executed on the resource with different operations in different modes.
Further, in the fourth step, the command of adding and deleting resources is executed in the entity package management mode, and the new creation and deletion operations of the local folder or file are respectively corresponded;
and executing the commands of adding and deleting resources in the logic mapping mode:
if a logical directory needs to be added in the engineering browser, the engineering file is modified, recording nodes are added in the engineering file, the recorded resource type is the logical directory, the logical path is an input name, and the mapping path is a special character string;
if an existing file needs to be added in a logical directory of the engineering browser, a mapping node is added in the engineering file, the resource type is recorded as the logical directory, the logical path is the logical directory or the file name, and the mapping path is the actual position of the file in the local system;
if the resources need to be deleted, judging the resource type, if the resource type is a logical directory, finding a mapping node with the same name, the resource type being the logical directory and the logical directory mark in the engineering file, and deleting the node; if the mapping node is the reference of the entity file, finding a mapping node with the same name, the resource type of the mapping node is a file and the mapping node is provided with a link mark in the engineering file, and deleting the node; if the file is the entity directory or the entity file, sending a prompt that the deletion of the local file is unrecoverable, and deleting the entity directory or the entity file after receiving a deletion confirmation command.
Further, in step four, the move resource command can be executed in either the logical mapping mode or the physical packet management mode,
when a resource moving command is received, reading a mode identifier, and if the mode identifier indicates that the current mode is an entity packet management mode, moving the resource by the processor; if the mode identification is represented as a logic mapping mode, modifying the logic path of the mapping record in the engineering file, and when the logic directory is moved, keeping the directory or file mapping path under the logic directory unchanged, and sequentially updating the logic path.
Further, in step three, the mode identifier is represented by a boolean value, where the boolean value is true in the case of the logical mapping mode, and the boolean value is false or cleared in the case of the physical packet management mode.
Further, the fourth step includes exporting the engineering package, where the exporting of the engineering package must be performed in the entity package management mode, and the engineering package is exported as a template package, where the template package may be used for importing and migrating the engineering package across hosts.
An MCU integrated development environment comprises a memory, a processor and a computer program which is stored in the memory and can run in the processor, wherein the processor can realize the engineering structure adaptation method of the MCU integrated development environment when executing the computer program.
The invention provides an engineering structure adaptation method of an MCU integrated development environment, which has the following advantages compared with the prior art:
1. the method does not affect the compiling, programming and debugging of the program, can flexibly switch two engineering structures according to the application scene, and the background performs corresponding command processing on the switching behavior, and is compatible with the use habits of different users, the freedom degree is expanded, and the use is more convenient and efficient.
2. Supporting efficient cross-host engineering migration, and supporting the SDK engineering of refining the multiplexing structure into a single template package. EVT package structures provided by hardware manufacturers are often libraries outside a plurality of engineering multiplexing projects, but most users only need a single project in actual use, and resources scattered in different positions are inconvenient to manage. After the mode is switched to the entity package management mode, the relative positions of files under different hosts to the project do not need to be considered. The export operation can effectively replace the way that a user manually moves the disk resources to construct the engineering package, thereby reducing the operation and time cost and improving the export efficiency. After the exported template package is provided for other users, the other users only need to import the template package and can also convert the template package into a logic mapping mode again to restore the file structure of the distributed management type. The overall development process forms a benign closed loop.
3. The coupling of the project and the local directory is reduced, the change of the index record corresponding to the increase and deletion movement of the project resources is avoided, and the actual disk file after the index is not operated. This effectively prevents the user from mistakenly deleting the files under the local disk without backup. Multiple routines on the same chip often refer to a common library, and a common library directory can be reused by using a logic mapping mode in the development process without copying each library file into a project folder.
Drawings
FIG. 1 is a flow chart of an MCU integrated development environment engineering structure adaptation method;
FIG. 2 is a flow chart of switching from the physical packet management mode to the logical mapping mode;
FIG. 3 is a flow chart of switching from the logical mapping mode to the physical packet management mode.
Detailed Description
The invention is further explained below with reference to the figures and the specific embodiments.
An MCU integrated development environment comprises a memory, a processor and a computer program which is stored in the memory and can run in the processor, wherein the processor can realize the following engineering structure adaptation method of the MCU integrated development environment when executing the computer program.
As shown in fig. 1, an engineering structure adaptation method for an MCU integrated development environment includes the following steps:
(1) receiving an engineering structure mode switching command, wherein the engineering structure mode comprises a logic mapping mode and an entity package management mode; in the logical mapping mode, the project directory does not really exist in the local system, the project files are scattered at a plurality of positions of the local system, the project files comprise mapping records, the mapping records comprise logical paths and mapping paths, the logical paths reflect the structural relationship of the project files, and the mapping paths are the actual positions of the project files in the local system; in the entity package management mode, the project directory corresponds to a project folder in the local system, and the project files correspond to files in the project folder;
the engineering structure mode switching command can be triggered by external input or according to specific conditions, the external input trigger does not limit the scene, and the specific conditions are as follows: when the project package is exported, the popup suggestion is initiated to be switched to the entity package management mode, and after the confirmation, the popup suggestion is switched to the entity package management mode, and when the project package is imported, the popup suggestion is initiated to select to keep the entity package management mode or switch to the logic mapping mode.
(2) Switching the mode of the engineering structure according to the mode switching command, and when receiving a command for switching to the logical mapping mode, as shown in fig. 2, executing depth-first traversal by the processor under the engineering directory, filtering out configuration files and output directories which are not related to mapping and do not need to be displayed in the engineering directory, recording the logical paths and mapping paths of the rest files, changing the path represented by the original engineering variables in the engineering configuration into a relative path, wherein the relative path is a path of the engineering variables relative to the engineering peer directory, and importing the path into a working space through a loading interface; when receiving a command for switching to the entity package management mode, as shown in fig. 3, the processor reads a mapping record in the engineering file, calculates an absolute path of the engineering file, creates a new folder in the engineering peer directory when the mapped file position does not exist in the engineering peer directory, and copies the mapped file into the new folder;
(3) updating a mode identifier, wherein the mode identifier is stored in the project file and is used for distinguishing project structure modes; the mode identification is represented by a Boolean value, the Boolean value is true when the mode is a logic mapping mode, and the Boolean value is false or is cleared when the mode is an entity packet management mode.
(4) And executing commands of adding, deleting and moving resources and exporting the engineering package in the switched engineering structure mode, wherein the resources comprise a logic directory, an entity directory and a file.
The logical mapping mode and the entity packet management mode share one set of interface, and the operation of executing the same command on resources in different modes is different.
Executing resource adding and deleting commands in an entity package management mode, and respectively corresponding to new creation and deletion operations of a local folder or file;
and executing the commands of adding and deleting resources in the logic mapping mode: if a logical directory needs to be added in the engineering browser, the engineering file is modified, recording nodes are added in the engineering file, the recorded resource type is the logical directory, the logical path is an input name, and the mapping path is a special character string; if an existing file needs to be added in a logical directory of the engineering browser, a mapping node is added in the engineering file, the resource type is recorded as the logical directory, the logical path is the logical directory or the file name, and the mapping path is the actual position of the file in the local system; if the resources need to be deleted, judging the resource type, if the resource type is a logical directory, finding a mapping node with the same name, the resource type being the logical directory and the logical directory mark in the engineering file, and deleting the node; if the mapping node is the reference of the entity file, finding a mapping node with the same name, the resource type of the mapping node is a file and the mapping node is provided with a link mark in the engineering file, and deleting the node; if the file is the entity directory or the entity file, sending a prompt that the deletion of the local file is unrecoverable, and deleting the entity directory or the entity file after receiving a deletion confirmation command.
The method comprises the steps that a mobile resource command can be executed in a logic mapping mode or an entity packet management mode, when the mobile resource command is received, a mode identifier is read first, and if the mode identifier indicates that the current entity packet management mode is adopted, a processor moves resources; if the mode identification is represented as a logic mapping mode, modifying the logic path of the mapping record in the engineering file, and when the logic directory is moved, keeping the directory or file mapping path under the logic directory unchanged, and sequentially updating the logic path.
The export of the engineering package must be executed in an entity package management mode, and the export generates a template package which can be used for importing engineering, or collaborative development across hosts, and the like.
The MCU integrated development environment Mouniver Studio is taken as an example, the scheme architecture comprises a command unit, an identification and mapping unit and a processing unit, the command unit is realized through an Eclipse plug-in, and the control event monitoring uses swt packets. And the identification and mapping unit is used for storing the mode identification, the identification is stored in the script, and the mapping record is stored in the project. The processing unit is used for executing commands and is realized through an Eclipse plug-in. The following further illustrates an MCU model CH32V103C6T6, EVT routine analog watch dog, as an example.
In the engineering structure, besides a source code User folder, a local public bank SRC is also introduced, and the whole EVT comprises a plurality of projects and is too large in size. And in the development process, individual projects need to be derived depending on public relations. The convenient and fast adaptation mode of the routine is as follows: the native engineering package is in an entity package management mode, the entity package management mode is switched into a logic mapping mode, engineering management is carried out through the logic mapping mode, the use habits of most Keil users are met, source codes are not easy to delete mistakenly, and resource management is facilitated; and then the logical mapping mode is switched to the entity package management mode, the template package is exported, other irrelevant files are not required, the engineering package is more convenient to export, and the working efficiency is improved. Of course, the user can also switch the engineering structure mode at any time according to the needs or the use habits, and the degree of freedom is high.
(1) A command to switch from a physical packet management mode to a logical mapping mode is received.
(2) Traversing the analog watch folder, obj being the output directory,. cproject,. project being the compiled link configuration and eclipse engineering script, respectively, these scripts stored for engineering configuration are filtered without adding mappings. User needs to add a mapping for the source code directory. And adding a mapping record in the project file to indicate that the User is a logic directory after conversion. According to the depth-first traversal algorithm, files such as ch32v10x _ conf.h, ch32v10x _ it.c under the directory are sequentially recorded after the subfiles of the User folder are continuously traversed. And no other subfolders needing to be traversed exist outside the User folder, and the depth-first traversal is finished.
Taking ch32v10x _ conf.h as an example, the format of the proposed record is as follows:
<link>
< name > User/ch32v10x _ conf.h </name >/logical Path
< type >1</type >// asset type 1 denotes a file, and 2 denotes a directory
< location > User/ch32v10x _ conf.h </location >/link location relative path representation
</link>
And expanding paths represented by all the engineering variables in the compiling link configuration, and converting the paths into relative paths by taking the engineering script file as a reference. Take the compiled include path as an example:
before conversion: value = "$ { workspace _ loc:/$ { ProjName }/Startup }" ".
After conversion: value = "("/. /)/SRC/Startup ""
This translates into emphasis, which is a guarantee that the project can be compiled properly afterwards. The actual location of the start folder in the EVT project is under the SRC, which is a public directory outside the project directory, due to the special link form. This key piece of information is recorded in the project file script before conversion.
<link>
<name>Startup</name>
<type>2</type>
<location>PARENT-1-PROJECT_LOC/SRC/Startup</location>
</link>
Analyzing and recording to obtain an actual path C: \ Users \ OWNER \ Downloads \ CH32V103EVT \ EVT \ EXAM \ SRC \ Startup, converting by taking a script C: \ Users \ OWNER \ Downloads \ CH32V103EVT \ EVT \ EXAM \ ADC \ AnalogWatchdog. Compiling a reference path list assembly in a compiled connection configuration, compiling a reference path list c. If the program presets relevant tool parameters for one-key programming and debugging, for example, programming an elf relative path outside a preset project, debugging a config file relative path outside a specified project, and also performing path updating.
(3) And updating the pattern identifier in the engineering file, setting the Boolean value to be true, and identifying the pattern before updating as a false or non-existent Boolean value (entity package management pattern).
(4) After switching to the logical mapping mode, resource management is performed in the mode, including adding, deleting and moving resources, where the resources include logical directories, entity directories and files.
(5) And (4) switching the engineering structure to a physical package management mode when the engineering package subjected to the series of modification in the step (4) needs to be provided to another host.
(6) A command to switch from a logical mapping mode to a physical packet management mode is received.
(7) After monitoring the command, the processing unit executes the related operation: the engineering file is firstly analyzed, the identification and the mapping unit are read, and the absolute path of each resource file is obtained through calculation of the engineering file and the relative path. In this example, directories StartUp (C: \ Users \ OWNER \ Downloads \ CH32V103EVT \ EVT \ EXAM \ SRC \ StartUp) and library files POP3.lib (F: \ MAIL _ POP3\ POP3.lib) are public, the processing unit creates a folder "External" under the peer directory, in which SRC and MAIL _ POP3 are created, and copies the linked resources StartUp, POP3.lib to the respective folders. And after the copying is finished, updating the actual path of the corresponding mapping in the project file and the compiling option.
(8) The pattern flag is updated, and the boolean value is cleared or false.
(9) Before the step is executed, the project package is associated with the folder of the local disk. The processing unit traverses the folder where the project is located, filters the compiling output directory, and packages the contents of the folder into a template with a specific format supported by the IDE. And after the template packet is transferred, analyzing and processing the template through the import interface, loading the project and realizing the cross-host transfer of the project packet.
Claims (8)
1. An engineering structure adaptation method of an MCU integrated development environment is characterized by comprising the following steps:
receiving an engineering structure mode switching command, wherein the engineering structure mode comprises a logic mapping mode and an entity package management mode; in the logical mapping mode, the project directory does not really exist in the local system, the project files are scattered at a plurality of positions of the local system, the project files comprise mapping records, the mapping records comprise logical paths and mapping paths, the logical paths reflect the structural relationship of the project files, and the mapping paths are the actual positions of the project files in the local system; in the entity package management mode, the project directory corresponds to a project folder in the local system, and the project files correspond to files in the project folder;
step two, switching the mode of the engineering structure according to the mode switching command, when receiving a command for switching to a logical mapping mode, executing depth-first traversal by a processor under an engineering directory, filtering out configuration files and output directories which are irrelevant to mapping and do not need to be displayed in the engineering directory, recording the logical paths and mapping paths of other files, changing the path represented by the original engineering variable in engineering configuration into a relative path, wherein the relative path is a path of the engineering variable relative to the same-level directory of the engineering, and importing the path into a working space through a loading interface; when receiving a command of switching to an entity package management mode, a processor reads a mapping record in an engineering file, calculates an absolute path of the engineering file, creates a new folder in an engineering peer directory when the position of the mapped file does not exist in the engineering peer directory, and copies the mapped file into the new folder;
step three, updating a mode identifier, wherein the mode identifier is stored in an engineering file and is used for distinguishing engineering structure modes;
and step four, executing commands of adding, deleting and moving resources in the switched engineering structure mode, wherein the resources comprise a logic directory, an entity directory and files.
2. The method for adapting an engineering structure of an MCU integrated development environment according to claim 1, wherein in step one, the engineering structure mode switching command can be triggered by an external input or triggered according to a specific condition, the external input trigger does not limit a scene, and the specific condition is: when the project package is exported, the popup suggestion is initiated to be switched to the entity package management mode, and after the confirmation, the popup suggestion is switched to the entity package management mode, and when the project package is imported, the popup suggestion is initiated to select to keep the entity package management mode or switch to the logic mapping mode.
3. The method for adapting an engineering structure of an MCU integrated development environment according to claim 1 or 2, wherein in step four, the logical mapping mode and the entity package management mode share a set of interfaces, and the operations of executing the same command on resources in different modes are different.
4. The method for adapting an engineering structure of an MCU integrated development environment according to claim 3, wherein in step four, the add/delete resource command is executed in the entity package management mode, corresponding to the new creation/deletion operation of a local folder or file, respectively;
and executing the commands of adding and deleting resources in the logic mapping mode:
if a logical directory needs to be added in the engineering browser, the engineering file is modified, recording nodes are added in the engineering file, the recorded resource type is the logical directory, the logical path is an input name, and the mapping path is a special character string;
if an existing file needs to be added in a logical directory of the engineering browser, a mapping node is added in the engineering file, the resource type is recorded as the logical directory, the logical path is the logical directory or the file name, and the mapping path is the actual position of the file in the local system;
if the resources need to be deleted, judging the resource type, if the resource type is a logical directory, finding a mapping node with the same name, the resource type being the logical directory and the logical directory mark in the engineering file, and deleting the node; if the mapping node is the reference of the entity file, finding a mapping node with the same name, the resource type of the mapping node is a file and the mapping node is provided with a link mark in the engineering file, and deleting the node; if the file is the entity directory or the entity file, sending a prompt that the deletion of the local file is unrecoverable, and deleting the entity directory or the entity file after receiving a deletion confirmation command.
5. The method of claim 3, wherein in step four, the move resource command is executed in either a logical mapping mode or a physical package management mode,
when a resource moving command is received, reading a mode identifier, and if the mode identifier indicates that the current mode is an entity packet management mode, moving the resource by the processor; if the mode identification is represented as a logic mapping mode, modifying the logic path of the mapping record in the engineering file, and when the logic directory is moved, keeping the directory or file mapping path under the logic directory unchanged, and sequentially updating the logic path.
6. An engineering structure adaptation method for an MCU integrated development environment according to claim 1 or 2, characterized in that in step three, the mode flag is represented by a Boolean value, the Boolean value is true when the mode is a logical mapping mode, and the Boolean value is false or cleared when the mode is an entity package management mode.
7. The method for adapting an engineering structure of an MCU integrated development environment according to claim 1 or 2, wherein step four further comprises exporting an engineering package, wherein the exporting of the engineering package must be performed in a physical package management mode, the engineering package is exported into a template package, and the template package can be used for importing the engineering package and migrating across hosts.
8. An MCU integrated development environment, comprising a memory, a processor and a computer program stored in the memory and executable in the processor, wherein the processor, when executing the computer program, can implement the method for adapting an engineering structure of an MCU integrated development environment according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110628976.3A CN113094033B (en) | 2021-06-07 | 2021-06-07 | Engineering structure adaptation method of MCU integrated development environment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110628976.3A CN113094033B (en) | 2021-06-07 | 2021-06-07 | Engineering structure adaptation method of MCU integrated development environment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113094033A true CN113094033A (en) | 2021-07-09 |
| CN113094033B CN113094033B (en) | 2021-08-27 |
Family
ID=76665136
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110628976.3A Active CN113094033B (en) | 2021-06-07 | 2021-06-07 | Engineering structure adaptation method of MCU integrated development environment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113094033B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101387959A (en) * | 2008-10-29 | 2009-03-18 | 东软集团股份有限公司 | Method for constructing physical engineering logical structure and apparatus |
| CN102006356A (en) * | 2010-09-27 | 2011-04-06 | 浙江大学 | Method for detecting state of cell phone pocket by using Android operating system |
| CN102063298A (en) * | 2010-12-10 | 2011-05-18 | 电子科技大学 | Automobile electronic controller-oriented runtime environment generation system and method |
| CN104321745A (en) * | 2012-02-07 | 2015-01-28 | 泰利瑞克股份公司 | Environment and method for cross-platform development of software applications |
| CN106502708A (en) * | 2016-11-15 | 2017-03-15 | 航天信息股份有限公司 | A kind of method and system for creating web project project based on Eclipse plug-in units |
| CN108196880A (en) * | 2017-12-11 | 2018-06-22 | 北京大学 | Software project knowledge mapping method for automatically constructing and system |
| US20180267779A1 (en) * | 2017-03-14 | 2018-09-20 | Cianmbella Ltd. | Method and apparatus for automatically generating and incorporating code in development environments |
| CN108647010A (en) * | 2018-04-27 | 2018-10-12 | 武汉斗鱼网络科技有限公司 | A kind of method, terminal device and the storage medium of projects initialization |
| WO2019099264A1 (en) * | 2017-11-14 | 2019-05-23 | Microsoft Technology Licensing, Llc | Assistive, language-agnostic debugging with multi-collaborator control |
| CN112905173A (en) * | 2021-05-07 | 2021-06-04 | 南京沁恒微电子股份有限公司 | Engineering multiplexing implementation method based on Eclipse and integrated development environment thereof |
-
2021
- 2021-06-07 CN CN202110628976.3A patent/CN113094033B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101387959A (en) * | 2008-10-29 | 2009-03-18 | 东软集团股份有限公司 | Method for constructing physical engineering logical structure and apparatus |
| CN102006356A (en) * | 2010-09-27 | 2011-04-06 | 浙江大学 | Method for detecting state of cell phone pocket by using Android operating system |
| CN102063298A (en) * | 2010-12-10 | 2011-05-18 | 电子科技大学 | Automobile electronic controller-oriented runtime environment generation system and method |
| CN104321745A (en) * | 2012-02-07 | 2015-01-28 | 泰利瑞克股份公司 | Environment and method for cross-platform development of software applications |
| CN106502708A (en) * | 2016-11-15 | 2017-03-15 | 航天信息股份有限公司 | A kind of method and system for creating web project project based on Eclipse plug-in units |
| US20180267779A1 (en) * | 2017-03-14 | 2018-09-20 | Cianmbella Ltd. | Method and apparatus for automatically generating and incorporating code in development environments |
| WO2019099264A1 (en) * | 2017-11-14 | 2019-05-23 | Microsoft Technology Licensing, Llc | Assistive, language-agnostic debugging with multi-collaborator control |
| CN108196880A (en) * | 2017-12-11 | 2018-06-22 | 北京大学 | Software project knowledge mapping method for automatically constructing and system |
| CN108647010A (en) * | 2018-04-27 | 2018-10-12 | 武汉斗鱼网络科技有限公司 | A kind of method, terminal device and the storage medium of projects initialization |
| CN112905173A (en) * | 2021-05-07 | 2021-06-04 | 南京沁恒微电子股份有限公司 | Engineering multiplexing implementation method based on Eclipse and integrated development environment thereof |
Non-Patent Citations (2)
| Title |
|---|
| HUANG_XW: ""Eclipse中的相对路径"", 《HTTPS://BBS.CSDN.NET/TOPICS/320080644》 * |
| 徐明路: ""在Eclipse中的Android项目里实现代码复用"", 《HTTPS://WWW.CNBLOGS.COM/SKY/2010/11/24/1886099.HTML》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113094033B (en) | 2021-08-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US5339435A (en) | Heterogenous software configuration management apparatus | |
| US5911074A (en) | Process for manipulating data models used in software engineering | |
| CN100442234C (en) | Software package constructing method and system for embedded system | |
| US5956513A (en) | System and method for automated software build control | |
| JP3738787B2 (en) | Resource management apparatus and resource management method | |
| US6117187A (en) | Automatic generation of a software installation package | |
| US5678044A (en) | System and method for improved rehosting of software systems | |
| CN109343854B (en) | Intelligent automatic compiling method and system based on zynq system | |
| US20030093420A1 (en) | Method and system for retrieving sharable information using a hierarchically dependent directory structure | |
| CN108595186B (en) | Multi-version software management method based on complete function on Feiteng platform | |
| US11579856B2 (en) | Multi-chip compatible compiling method and device | |
| US8010578B2 (en) | Method of refactoring a running database system | |
| US20080271004A1 (en) | Computer-implemented method, system, and program product for optimizing a distributed application | |
| CN101866315A (en) | Test method and system of software development tool | |
| CN115437684A (en) | File-level clipping method and system for Linux kernel source code | |
| WO2022227409A1 (en) | Embedded terminal remote software updating method | |
| CN113094033B (en) | Engineering structure adaptation method of MCU integrated development environment | |
| CN110058876B (en) | Method, device, server and storage medium for expanding compatibility of wireshark software | |
| JP3603718B2 (en) | Project content analysis method and system using makeup information analysis and information recording medium | |
| WO2008015110A2 (en) | Methods, apparatus and computer programs for modelling computer programs | |
| CN108829387B (en) | RPC function generation method based on Windows platform | |
| WO2023082365A1 (en) | Wechat mini program packaging platform and method, and device and storage medium | |
| CN115794174A (en) | Project program import updating method | |
| KR100520632B1 (en) | How to create makefile in deset environment | |
| JPH03286346A (en) | File control system |
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 |