| Removing the generated Header file (*.h) using own compiler tool & clean target [message #169708] |
Wed, 17 May 2006 02:35 |
Eclipse User |
|
|
|
Summary
Requirement:
Writing an eclipse plug-in by using the CDT buildDefinitions extension
point. The plug-in should build an executable file for our platform.
Progress so far:
1. Started by referring to Managed Build System Extensibility Document
provided for extending the CDT extension point
org.eclipse.cdt.managedbuilder.core.buildDefinitions.
2. We have been able to write a plug-in to generate an executable without
regard to our platform specific header dependencies.
Problem:
There are two types of cores in our chip a Digital Signal Engine (DSE) and
a Processing Engine (PE). We have two compilers for these two type of
cores a DSE compiler and a PE compiler. The DSE compiler compiles a code
written in a language designed for DSE while the PE code is written in C.
The PE is the controller and the DSE is a worker. The executable file
generated for the platform contains the object code for both the PE and
the DSE. Typically the PE is started first and the PE code launches the
DSE code on selected DSE(s).
The steps to generate the executable file are:
1. Compile the DSE code into a object file dse_code.o
2. Compile the PE code into an object file pe_code.o
3. Link dse_code.o, pe_code.o and libraries to generate the executable
file.
In Step 1, the DSE compiler generates dse_code.o file and also generates a
header file dsevar_dse_code.h that contains register allocation
information. This information is needed in the PE code and thus,
dsevar_dse_code.h is #included in the PE code.
The main problem lies here. The dsevar_dse_code.h gets generated as
required but we have problems when the user does a Clean on the project.
In our plug-in we have the DSE compiler tool. We have one CDT input type
and one output type for this tool, which corresponds to the source file
and the object file respectively. In order to be able to remove the
generated dsevar_dse_code.h file, we have tried adding another output type
to the DSE compiler tool. We are also able to get the CLA_H variable
listed in the rm command for clean but we are not able to assign CLA_H: =
dsevar_dse_code.h. Hence, the header file does not get removed currently.
Any help in this regard would be greatly appreciated.
|
|
|
Powered by
FUDForum. Page generated in 0.02079 seconds
Home