JPH0981394A - Compiling method managing device - Google Patents

Abstract

(57) Abstract: The present invention relates to a compiling method management device for managing a compiling method, and an object thereof is to make it possible to specify a compiling method easily and surely without requiring specialized knowledge. To do. SOLUTION: An information file for registering a compilation method in advance and a management file creation for creating a management file by selecting one to be used for a group from a list of this information file and incorporating one or more specifications of an execution program Means and a makefile creating means for creating a makefile necessary for controlling compilation based on the created management file, and a make compiler corresponding to one of the specification compiler, language compiler, assembler, and linker according to this makefile. And an execution unit configured to control an object and generate an executable program in an executable format.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a compiling method management device for managing a compiling method when compiling specifications and generating an executable program in an executable format.

[0002]

2. Description of the Related Art Conventionally, an operator inputs all the processing required to compile a source program and describes it in a makefile, and the source file (specification) is specified using this makefile. The compiler, assembler, and linker were used to generate an executable program in an executable format.

[0003]

As described above, in the conventional method, when a plurality of compiling methods are used, it is necessary for the operator to describe as many make files as the number of compilations, which is extremely difficult to describe. There was a problem.

Further, in a method in which all the compiling methods are described in the makefile in advance and the control flow of the compilation is divided by specifying the conditional expressions at the time of compilation, it is necessary to specify the conditional expressions, and often the conditional expressions are used. There was a problem that it could not be separated unless it was wrong or it was not an expert who was familiar with the knowledge of conditional expressions.

The present invention solves these problems.
The compile method is registered in advance in the information file, the one corresponding to the group is selected from the information file list, the specification file is created to create the management file, and the make file is automatically generated and compiled based on this management file. ,
The purpose is to make it possible to compile by specifying the compile method easily and surely without specialized knowledge.

[0006]

[Means for Solving the Problems] Means for solving the problems will be described with reference to FIG. In FIG. 1, the management file creating means 2 creates a management file 6 by selecting one to be used for a group from a list of information files and taking in one or more specifications of an execution program.

The makefile creating means 3 creates a makefile 7 necessary for controlling compilation based on the management file 6. The execution unit 4 controls an appropriate one of a specification compiler, a language compiler, an assembler, and a linker according to the makefile 7 to generate an executable program 8 in an executable format.

The information file 5 is a file in which a compilation method is registered. The management file 6 is for registering and managing a compilation method, specifications, etc. for each group.

The makefile 7 stores information necessary for controlling compilation. Next, the operation will be described.

The management file creating means 2 uses the information file 5
Select the one to be used for the group from the list, and create the management file 6 by incorporating one or more specifications of the execution program, and compile control based on the management file 6 created by the makefile creating means 3. The makefile 7 necessary for execution is created, and the execution means 4 controls an appropriate one of the specification compiler, the language compiler, the assembler, and the linker according to the makefile 7 to generate the executable program 8 in the executable format. I am trying to do it.

At this time, in response to the corresponding management file 6 being selected from the list of management files 6 created for each group by the make file creating means 3, the make file 7 is selected from the selected management files 6. Automatically generated,
The execution means 4 controls an appropriate one of a specification compiler, a language compiler, an assembler, and a linker according to the makefile 7 to generate an executable program 8 in an executable format.

Therefore, the compile method is set to the information file 5
Registered in advance, select the information corresponding to the group from the information file list, create the specifications, and register the management file 6, and based on this management file 6, makefile 7
By automatically generating and compiling, it is possible to easily and surely specify the compiling method and compile without specialized knowledge.

[0013]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, an embodiment and operation of the present invention will be described in detail sequentially with reference to FIGS.

FIG. 1 shows a system configuration diagram of the present invention.
In FIG. 1, a processing device 1 performs various processes according to a program, and here, a management file creating means 2, a make file creating means 3, and an executing means 4 are provided.
It is composed of etc.

The management file creating means 2 responds to the selection of the information file 5 to be used for the group from the list of the information files 5, one of which is necessary for creating the selected information file 5 and the execution program. The management file 6 is created by incorporating a plurality of specifications and various options.

The make file creating means 3 creates the information necessary for controlling the compilation based on the group compiling method and various options stored in the management file 6 and stores it in the make file 7. .

The execution means 4 controls an appropriate one of a specification compiler, a language compiler, an assembler, and a linker according to the makefile 7 to generate an executable program 8 in an executable format.

The information file 5 is a file in which a compilation method (specification compiler, language compiler, assembler, linker type) is registered in association with, for example, a chip name of an execution program.

The management file 6 is for registering and managing the contents of the information file 5 and specifications and various options necessary for creating an execution program for each group.

The makefile 7 stores information for controlling the specification compiler, language compiler, assembler, and linker based on the compilation method, specifications, and various options for each group registered in the management file 6. It was done.

The execution program 8 is an executable program after being compiled. The input device 9 is used to input various data and instructions. The display device 10 displays various data and the like.

Next, the procedure for creating the management file with the configuration of FIG. 1 will be described in detail with reference to FIG. FIG. 2A shows a management file creation flowchart.

In FIG. 2A, S1 creates an information file for each path. This is, for example, the type of specification compiler, language compiler, assembler, and linker used until the execution program is created from the specification in units of groups (paths) surrounded by dotted lines in FIG. It is determined and stored in the information file 5. This information file 5 creates and registers all combinations of specifications compilers, language compilers, assemblers, and linkers that can be used.

In step S2, a list of information files is displayed.
This displays a list of information files 5 created in advance in order to create a management file. In S3, an information file corresponding to the group is selected. This is because the list of the information files 5 created in advance is displayed on the screen and the group to be created from the list, for example, (a) in FIG.
Select one information file 5 describing the assembly method to be used for the group 1 on the left side of.

In step S4, specifications of the execution program are created. For example, in the case of the group 1 on the left side of FIG. 4A, the operator creates three specifications A, B, and C.

In step S5, a management file is created and options are registered for each specification. This registers the contents (compile method) of the information file 5 selected in S3 and the specifications (compiler options) for each specifications in addition to the specifications created in S4.

At step S6, it is determined whether or not the process is finished. If YES, the process ends. In the case of NO, for example, when the creation of the management file 6 of the group 1 in FIG.
Further, since there is a group 2, the management file 6 for the group 2 is created by repeating S1 and subsequent steps.

As described above, the compile method (specification compiler, language compiler, assembler, linker type) that can be used in advance is determined for each path and the information file 5
Register the information in the information file 5 and select the appropriate management file 6 for the group you are going to create from the list.
One of them is selected and the contents (compilation method) are taken out, a specification of the execution program is created, various options are set, and the management file 6 is created. As a result, it is possible to easily create the management file 6 for each group without requiring specialized knowledge.

FIG. 2B shows an example of the information file.
This information file 5 is for registering a specification compiler, a language compiler, an assembler, and a linker in advance in association with the chip name of the execution program as shown in the figure.

FIG. 3 shows an explanatory diagram of creating a management file according to the present invention. In FIG. 3, S11 shows a state in which the information file 5 is created and registered in advance. Here, the following items shown in the figure are registered in the information file 5.

-Language series: C language-Compiler type: C language A-Linker type: Linker A-Assembler path presence / absence: Yes and no assembler A-Option program: S12 is a list of information files 5 of S11 Pass 1 from the inside
The information file 1 or the information file 2 for the path 2 or the path 2 is selected and taken out.

In step S13, a management file is created. In this case, various designations are made for the contents of the information file used for the group selected and extracted from the list in S12, and the lower management file 6 is created.

-Group name designation-Compiler option designation-Other designations S14 creates specifications. This creates a specification of the executing program. For example, in the case of groups 1 and 2 of FIG. 4A described later, the following specifications are created.

-Group 1-Specification A-Specification B-Specification C-Group 2-Specification C-Specification D S15 shows an example of the created management file 6. The management file 6 registers the following items shown in the figure.

-Group name: Group 1-Language system used-Compiler, linker type, assembler path presence-Compiler options (group defaults) -Specification A: compile options, group defaults-Specification B : Compile option, group default-Specification C: Compile option, exception specification As described above, the information file 5 to be used for the group is selected from the list of the information files 5 registered in advance and its contents (compile method, etc.) ) Is taken out, the specifications are created, the options are set, etc., and the management file 6 can be created easily and without error.

FIG. 4 shows a group explanatory diagram of the present invention.
FIG. 4A shows a group 1 (path 1) and a group 2
The case where there are two (path 2) is shown. The groove 1 is for compiling the execution program 1 based on the specifications A, B and C, and the groove 2 is for compiling the execution program 2 based on the specifications C and D. here,
Group 1 (pass 1) and group 2 (pass 2) are set in association with chips that execute the execution programs 1 and 2. Group 1 and group 2 generate an execution program using the following specification compiler, language compiler, assembler, and linker, respectively (see FIG. 5A).

Group Specification Compiler Language Compiler Assembler Linker 1 For C language A A A 2 For C language B B B FIG. 4B shows the case of group 3 (pass 3).
The groove 3 is to be compiled into the execution program 3 based on the specifications V and W. Here, the group 3 (path 3) is set in association with the chip that executes the execution program 3. Group 3 is to generate an execution program by using the following specification compiler, language compiler, assembler, and linker shown in FIG.
(B)).

Group Specification Compiler Language Compiler Assembler Linker 3 For C Language B None B FIG. 4C shows the case of group 4 (pass 4).
The groove 4 is to be compiled into the execution program 4 based on the specifications X and Y. Here, the group 4 (path 4) is set in association with the chip that executes the execution program 4. Group 4 is for generating an execution program by using the following specification compiler, language compiler, assembler, and linker shown in FIG.
(C)).

Group Specification Compiler Language Compiler Assembler Linker 4 For COBOL Language COBOL None X FIG. 5 shows an example of an information file of the present invention.

FIG. 5A shows an example of the information file 5 of the groups 1 and 2 in FIG. 4A. Here, the groups 1 and 2 are registered as illustrated. FIG. 5B
Shows an example of the information file 5 of the group 3 of FIG. 4B in comparison with the group 2 of FIG. 4A. here,
Group 3 is registered as shown.

FIG. 5C shows an example of the information file 5 of the group 4 of FIG. 4C in comparison with the group 3 of FIG. 4B. Here, the group 4 is registered as illustrated.

Next, the procedure for compiling the execution program 8 using the management file 6 will be described with reference to FIGS. 6 and 7. FIG. 6 shows an execution flowchart of the present invention.

In FIG. 6, S21 displays a group list. This displays the group list of the management file 6 registered for each group described above. In S22, the management file corresponding to the group is selected.

In step S23, a make file is created. This creates the information necessary for controlling the specification compiler, language compiler, assembler, and linker based on the management file 6 of the group selected in S22, and stores it in the makefile 7.

In step S24, the specifications are compiled. According to the makefile 7 created in S23, this controls the specification compiler 71 of FIG. 7 described later to compile (convert) the specification into, for example, a C language source.

In step S25, the language is compiled. this is,
For example, the C language source is compiled (converted) into an assembler source. S26 assembles. This assembles (converts) an assembler source into a program into a target language, for example.

S27 is linked. This links the programs in the plurality of target languages assembled in S26 into an executable program in an executable format. S28 completes the executable program in the executable format.

As described above, the management file of the corresponding group is selected from the list of the management files 6, the makefile 7 is automatically created from this management file 6, and the specification compiler 71 and the language compiler 72 are made according to this makefile 7. , The assembler 73 and the linker 74 can be controlled to automatically generate the executable program 8 in an executable format.

FIG. 7 shows a compilation explanatory diagram of the present invention. In FIG. 7, S31 is the management file 6 of the corresponding group from the list of management files 6 displayed on the screen.
Specify one.

In step S32, the management file 6 designated in step S31 is taken out. In S33, the make file 7 is automatically generated based on the management file 6 in S32.

In step S34, based on the makefile 7 automatically generated in step S33, the specification compiler 71, the language compiler 72, the assembler 73, and the linker 74 are controlled to compile an executable program in an executable format. .

As described above, by simply selecting the management file 6 corresponding to the group from the list of management files 6,
It is possible to automatically generate the makefile 7 and automatically compile the execution program 8 from the specifications.

[0053]

As described above, according to the present invention,
The compile method is registered in advance in the information file 5, the one corresponding to the group is selected from the information file list, the specification file is created to create the management file 6, and the make file 7 is automatically generated based on the management file 6. Since the configuration for compiling is used, it is possible to compile the executable program 8 in an executable format from a plurality of specifications by simply and surely designating the compiling method without specialized knowledge. As a result, even an operator who has no linguistic knowledge can set the compile method and compile easily and surely.

[Brief description of drawings]

FIG. 1 is a system configuration diagram of the present invention.

FIG. 2 is an explanatory diagram (No. 1) of creating a management file of the present invention.

FIG. 3 is an explanatory diagram (Part 2) of creating a management file of the present invention.

FIG. 4 is a group explanatory diagram of the present invention.

FIG. 5 is an example of an information file of the present invention.

FIG. 6 is an execution flowchart of the present invention.

FIG. 7 is an explanatory diagram of compiling according to the present invention.

[Explanation of symbols]

 1: Processor 2: Management file creation means 3: Make file creation means 4: Execution means 5: Information file 6: Management file 7: Make file 71: Specification compiler 72: Language compiler 73: Assembler 74: Linker 8: Execution Program 9: Input device 10: Display device

Claims (2)

[Claims] 1. An information file in which a compilation method is registered in advance, and a management file for selecting a file to be used for a group from a list of the information files and creating a management file by incorporating one or more specifications of an execution program. Creating means, and a makefile creating means for creating a makefile necessary for controlling compilation based on the created management file, and a makefile corresponding to one of the specification compiler, language compiler, assembler, and linker according to this makefile. A compiling method management device, comprising: an execution unit configured to control what is executed to generate an executable program in an executable format. 2. The make file creating means automatically creates a make file from the selected management file in response to selection of a corresponding management file from the list of management files created for each group. 2. The compiling method according to claim 1, wherein the execution means controls an appropriate one of a specification compiler, a language compiler, an assembler, and a linker according to the makefile to generate an executable program in an executable format. Management device.