DDT 0.4.0 released (formerly "Mmrnmhrm")

[Tom]

El 26/11/2010 08:43, Bruno Medeiros escribió:
> On 24/11/2010 21:44, Tom wrote:
>> El 17/11/2010 15:52, Bruno Medeiros escribió:
>>> I'm announcing the release of DDT (D Development Tools) version 0.4.0:
>>>
>>> http://code.google.com/a/eclipselabs.org/p/ddt/
>>>
>>> (There was previously an older inactive project also called DDT, it has
>>> been renamed to EclipseD, with the authors permission.)
>>>
>>> The DDT project is a direct continuation of the Mmrnmhrm project. It has
>>> been renamed to reflect a more serious and unified approach to the
>>> Eclipse IDE project development. (although ocasional odd references
>>> might still be present in less conspicuous places ^_^ )
>>>
>>> It has been 2 years since the last significant release, and this version
>>> has a lot of rough edges: Some newer D2 syntaxes are not yet supported
>>> (http://code.google.com/a/eclipselabs.org/p/ddt/issues/detail?id=6), and
>>> otherwise there are likely to be several parser bugs in the IDE (... you
>>> will be baked...). But it should provide for a minimally useful IDE, at
>>> least for simpler D projects.
>>>
>>> See http://code.google.com/a/eclipselabs.org/p/ddt/wiki/Features for a
>>> rough idea of what to expect.
>>> See also: http://code.google.com/a/eclipselabs.org/p/ddt/wiki/GeneralFAQ
>>>
>>> Changelog:
>>>
>>> == DDT 0.4.0 (2010-11-17) ==
>>> * Renamed project to DDT
>>> * Updated IDE to latest DLTK version (2.0).
>>> * Fixed comment indentation character (was '#' instead of '//') on
>>> toggle comment actions
>>> * Fixed defaults bug in DeeRootPreferencePage and
>>> DeeEditorPreferencePage.
>>> * Added DEEBUILDER.COMPILEREXEPATH variable to builder, changed builder
>>> response file defaults. [No longer uses rebuild as the default]
>>> * Fixed parser to be able to parse expressions as the argument of
>>> typeid.
>>> * Added a parser workaround to allow parsing D source with annotations.
>>> * Fixed several parser bugs.
>>> * Removed Content Assist Templates preference page.
>>
>> Hi,
>>
>> is there a way to build a library with DDT?
>>
>> Thanks in advance,
>> Tom;
>>
>
> Well, yes, if I understand you correctly. DDT will just call an external
> tool with the parameters you specify (it can be dmd, it can be
> anything), so you can configure it to build a library. But is this what
> you meant?
>

Yeah. I was able to build a library using -lib but didn't found a way to 
tell the other DDT project to use such library.

Also, it seems like there's only one build configuration for each 
project. Am I missing something or it's just that it isn't implemented yet?

Thanks,
Tom;