Re: [cdt-dev] Build System redo

[Jesper Eskilson <jesper.eskilson@xxxxxxx>]

On 2015-03-19 02:25, Alena Laskavaia wrote:

My 2c is that I don't think we need to get rid of internal builder. I think we should just make clear

interface between build configuration and actual build system, so its easily swappable.

And +2 for replacing xml madness with API's. XML is there for de-coupling and lazy loading.

When we start dealing with multiple inheritance in xml its clearly overboard... (and good luck debugging it)

The two most important things (I think) which needs to be addressed are (1) build model needs to be committable (the .cproject file is really not, as spontaneous changes appear in it for no good reason) and (2) builds need to be easily done offline without having to start an entire Eclipse instance. Fixing those to things should be the firstmost concern (IMHO). My number (3) is to have a build model which is portable across different platforms (Linux/Windows/etc). (Insert reference to the Spanish Inquisition here...)

Describing toolchains in XML is simply not flexible enough (at least not from my perspective, where there are lots of compiler options with very hairy semantics and interrelationships between each other), especially if you want to have any sort of completeness in covering all available tool options. We're moving towards a solution where we generate the plugin.xml file, but having a Java API to do that dynamically at runtime would make lots of things much simpler for us.

/Jesper

On Wed, Mar 18, 2015 at 11:46 AM, Doug Schaefer <dschaefer@xxxxxxx> wrote:

Just to a couple more thoughts. I¹m actually pretty happy with the build
model, the proper one, IConfiguration and friends. It¹s really things like
ICConfigurationDescription and friends that I have issues with. It¹s an
additional layer where people have lost their souls trying to figure out
:), and it¹s really that layer that causes most of our problems.

Also, the build model needs to be in the cdt.core so we can generically
get at build information from core features that need it, like the
indexer/parsers. And maybe that¹ll simplify things like the language
settings providers, like scanner discovery actually populating the build
model, and maybe replacing things like IIncludeEntry from the CModel with
include items from the build model.

Doug.

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev

--
Jesper Eskilson Development Engineer
IAR Systems AB
Box 23051, Strandbodgatan 1
SE-750 23 Uppsala, SWEDEN
E-mail: jesper.eskilson@xxxxxxx Website: www.iar.com
Twitter: www.twitter.com/iarsystems