On Wed, 06 Feb 2008 10:24:06 +0200, dominik <aha@aha.com> wrote:

> "Ary Borenszweig" <ary@esperanto.org.ar> wrote in message news:fo63qt$8a2$1@digitalmars.com...
>> The Descent plugin for Eclipse provides an IDE for writing, launching and debugging code in D.
>
> have you considered to make a custom eclipse build with Descent, maybe a SVN
> and several other things into one?
> you can do that easily with this: http://ondemand.yoxos.com/geteclipse/start

Better yet, make one with an installation wizard that could download and install the D compiler (and maybe Tango, and maybe DDBG for Windows) for you. This way, getting a full-featured IDE up and running should be a sinch for new D users.

-- 
Best regards,
 Vladimir                          mailto:thecybershadow@gmail.com

Give it that path that contains the bin directory (just one directory above bin).

Olli Aalto escribió:
> Hi. I ran into a problem when adding a compiler. I have Tango which contains the DMD compiler and giving Descent the path the Tango's bin directory, it says "Target is not a DMD installation Root. DMD executable was not found". I put "dmd.exe" as the compiler name.
> Am I missing something, or doesn't Descent just not recognize the compiler when it's been bundled with Tango?
> 
> O.

And no, it doesn't recognize the compiler when it's been bundled with Tango. How should it do it? For now, in Windows, it recognized phobos by searching it in src/phobos. Is there a standard directory layout for dmd bundled with Tango?

Ary Borenszweig escribió:
> Give it that path that contains the bin directory (just one directory above bin).
> 
> Olli Aalto escribió:
>> Hi. I ran into a problem when adding a compiler. I have Tango which contains the DMD compiler and giving Descent the path the Tango's bin directory, it says "Target is not a DMD installation Root. DMD executable was not found". I put "dmd.exe" as the compiler name.
>> Am I missing something, or doesn't Descent just not recognize the compiler when it's been bundled with Tango?
>>
>> O.

Ary Borenszweig wrote:
> Give it that path that contains the bin directory (just one directory above bin).
> 

Thanks, that fixed it. Now everything seems to work as it should.

O.

That's actually an *excellent* idea, which I will implemenet for the next release. And probably when search is implemented, you'll be able to see where a particular version/debug identifier is used.

Extrawurst escribió:
> correct.
> 
> 
> Ary Borenszweig schrieb:
>> You mean, collecting all the version/debug identifiers in the project and in referenced include paths, and show them to you, so you can know all the switches?
>>
>> Extrawurst wrote:
>>> well it would be nice for compiling a project which includes various externaly created/edited modules which eventually use some version identifiers which u are not aware of. do you see the point ?
>>>
>>>
>>> Ary Borenszweig schrieb:
>>>> Where do you want to use it?
>>>>
>>>> If it's just seeing the available ones, they are in Windows -> Preferences, D -> Compiler. The suggestions come from there, and from the version/debug identifiers defined in the source file being edited.