Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Internal Builder

Hello again,

 

Part of my earlier question was answered by org.eclipse.cdt.msw.build
(it uses org.eclipse.cdt.build.core.internal.builder as its only builder).

 

But I still have some doubts. So I’ll give it another try.

 

From reading through MBS, I gather that IManagedBuilderMakefileGenerator2, is the interface that needs to be implemented for any external build tool.

So if I wanted to support NMake, I would use GnuMakefileGenerator as a starting point, and modify it for NMake’s syntax.

 

If I wanted to avoid that effort, would the internal builder be a good option?

Does CDT’s internal builder use .project and .cproject files to completely store its internal representation (or is more info needed)?

Are these file formats reasonably stable and documented?

Thanks for any suggestions,

Stan Mitchell

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Stan Mitchell
Sent: Saturday, January 22, 2011 7:55 AM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Internal Builder

 

I’m working on a plug-in for CDT to support a custom tool-chain. (Helios, CDT 7.0)

 

The MBS document states that the internal builder will be used if the superclass attribute is set to org.eclipse.cdt.build.core.internal.builder.

Is it intended to be used in conjunction with an external build tool or can a tool chain be setup to _only_ use the internal builder?

Are there any plans to create an exportable file representation of an internal build?

 

Stan Mitchell


Back to the top