Thread overview
missing or corrupt object.d?
Feb 15, 2008
Christopher Wright
Feb 15, 2008
Ary Borenszweig
Feb 15, 2008
Christopher Wright
Feb 15, 2008
Ary Borenszweig
Feb 16, 2008
Christopher Wright
February 15, 2008
Hey,
I have Tangobos, downloaded with dmd from the Tango site, and pointed descent at that copy of dmd and the associated imports directory. Being Tango-based, it doesn't have object.d; it instead has object.di. When I open anything with this compiler selected, it complains for every class definition: "Missing or corrupt object.d".

Why is this? How can I fix it?

Thanks!
February 15, 2008
Christopher Wright escribió:
> Hey,
> I have Tangobos, downloaded with dmd from the Tango site, and pointed descent at that copy of dmd and the associated imports directory. Being Tango-based, it doesn't have object.d; it instead has object.di. When I open anything with this compiler selected, it complains for every class definition: "Missing or corrupt object.d".
> 
> Why is this? How can I fix it?
> 
> Thanks!

object.di will also do. Descent takes as "D files" files that end with ".d" or ".di". Could you check that "object.di" is located in the "(default package)" of Tangobos? That's expanding the Standard Library node, then again for the container, and again for the default package.
February 15, 2008
Ary Borenszweig wrote:
> object.di will also do. Descent takes as "D files" files that end with ".d" or ".di". Could you check that "object.di" is located in the "(default package)" of Tangobos? That's expanding the Standard Library node, then again for the container, and again for the default package.

Ah, okay. The GUI didn't have a problem with me not specifying a standard library, so I missed that step.

Thanks.
February 15, 2008
Christopher Wright escribió:
> Ary Borenszweig wrote:
>> object.di will also do. Descent takes as "D files" files that end with ".d" or ".di". Could you check that "object.di" is located in the "(default package)" of Tangobos? That's expanding the Standard Library node, then again for the container, and again for the default package.
> 
> Ah, okay. The GUI didn't have a problem with me not specifying a standard library, so I missed that step.
> 
> Thanks.

Ok, I decided to bold the "Configuring plugin" section in the wiki, and also add it as a final step in the installation of the plugin. We'll probably also change the error message to something more helpful in the next release.
February 16, 2008
Ary Borenszweig wrote:
> Ok, I decided to bold the "Configuring plugin" section in the wiki, and also add it as a final step in the installation of the plugin. We'll probably also change the error message to something more helpful in the next release.

Bah. Next release, I'll build you a better idiot :)