Eclipse Community Forums: C / C++ IDE (CDT) » Managed Build System Extensibility use instruction

Home » Language IDEs » C / C++ IDE (CDT) » Managed Build System Extensibility use instruction

Managed Build System Extensibility use instruction [message #190269]

Fri, 27 April 2007 23:06

Eclipse User

Originally posted by: mukerji.nita.gmail.com

I have Eclipse 3.2 with CDT 3.1 installed. In C perspective, upon clicking
build action menu item, I want a program, written by me and kept in
workspace, to
execute with the C file that is open in the C/C++ editor as the input.My
Program produces two output files.

Reading the method described in Chapter 6 of "Managed Build System
Extensibility Document"(Help Content -CDT plug-in Developer Guide),I think
what I want is feasible.Whatever gcc uses to compile (ie error
parsers,dependency calculators)
all remain the same. Only instead of gcc, the tool command has to be my
program name.What new Java Classes need I provide? Is there some more
reading material available to clear my understanding of Managed Build
System Extensibility?

Re: Managed Build System Extensibility use instruction [message #190287 is a reply to message #190269]

Sat, 28 April 2007 05:29

Eclipse User

Originally posted by: dmsubs.NOSPAM.consertum.com

There may not be any need for Java - you can do everything in XML. Suggest you
look at the standard tools definitions in:

org.eclipse.cdt.managedbuilder.gnu.ui\plugin.xml

(You will find this in the CDT source release).

HTH

--
Derek

Nita wrote:
> I have Eclipse 3.2 with CDT 3.1 installed. In C perspective, upon
> clicking build action menu item, I want a program, written by me and
> kept in workspace, to
> execute with the C file that is open in the C/C++ editor as the input.My
> Program produces two output files.
>
> Reading the method described in Chapter 6 of "Managed Build System
> Extensibility Document"(Help Content -CDT plug-in Developer Guide),I
> think what I want is feasible.Whatever gcc uses to compile (ie error
> parsers,dependency calculators)
> all remain the same. Only instead of gcc, the tool command has to be my
> program name.What new Java Classes need I provide? Is there some more
> reading material available to clear my understanding of Managed Build
> System Extensibility?
>
>

Re: Managed Build System Extensibility use instruction [message #190294 is a reply to message #190287]

Sat, 28 April 2007 09:03

Eclipse User

Originally posted by: mukerji.nita.gmail.com

Thank you.
Would it be possible to take off gcc from build operation? I need to write
a plugin.xml which makes build behaves as follows:
all: test
clean: -rm main.o test
test: test.esp
./precomp test

I have written what I thought was doing the above.But trying to test it I
see
cdtbuild has GNU c/c++ compiler /assembler at work.

(my operating system is linux)

Re: Managed Build System Extensibility use instruction [message #190311 is a reply to message #190294]

Sun, 29 April 2007 04:08

Eclipse User

Originally posted by: dmsubs.NOSPAM.consertum.com

GCC will only be called if you have C souce files in your project. However, you
can define a project type that has no rules for C source files.

--
Derek

Nita wrote:
> Thank you.
> Would it be possible to take off gcc from build operation? I need to
> write a plugin.xml which makes build behaves as follows:
> all: test
> clean: -rm main.o test
> test: test.esp
> ./precomp test
>
> I have written what I thought was doing the above.But trying to test it
> I see
> cdtbuild has GNU c/c++ compiler /assembler at work.
>
>
> (my operating system is linux)
>

Re: Managed Build System Extensibility use instruction [message #190327 is a reply to message #190311]

Sun, 29 April 2007 07:12

Eclipse User

Originally posted by: mukerji.nita.gmail.com

Thanks

Re: Managed Build System Extensibility use instruction [message #190408 is a reply to message #190311]

Tue, 01 May 2007 06:46

Eclipse User

Originally posted by: mukerji.nita.gmail.com

Please help me to find an example explaining how to define a project type.

I am trying to do the following:
In C/C++ perspective I enter a program, this is input file to my program
code( which takes in this input file and produces two output file). This
gets done very well when I do it with a makefile and a Standard Make C
Project.

Now I want the above incorporated in a plug-in so that when I click on
build,
my program code runs using the above mentioned input file.

The Standard Make C Project uses "specsFile" for scannerInfoProvider.Does
my plug-in need something to do if that? Guide me to some example codes
dealing with this sort of thing.

Re: Managed Build System Extensibility use instruction [message #190422 is a reply to message #190408]

Tue, 01 May 2007 06:54

Eclipse User

Originally posted by: dmsubs.NOSPAM.consertum.com

You should read the MBS extensibility document together with the plugin.xml that
I pointed you at. That provides all the information and examples that you need
(that is what I used).

Good luck,
--
Derek

Nita wrote:
> Please help me to find an example explaining how to define a project type.
>
> I am trying to do the following:
> In C/C++ perspective I enter a program, this is input file to my program
> code( which takes in this input file and produces two output file). This
> gets done very well when I do it with a makefile and a Standard Make C
> Project.
>
> Now I want the above incorporated in a plug-in so that when I click on
> build,
> my program code runs using the above mentioned input file.
>
> The Standard Make C Project uses "specsFile" for
> scannerInfoProvider.Does my plug-in need something to do if that? Guide
> me to some example codes dealing with this sort of thing.

Previous Topic:	Embedded debugging with CDT4.0 & BDM/JTAG
Next Topic:	Adding new files to project.

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 16 23:21:34 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter