Hi,
I've just installed the D compiler following requisites and instructions.

However, when I try to compile a simple "Hello" program, the compiler gives me the following error :

Error : error reding file 'object.d'

What happens?

Thanks a lot.

Alessandro Picetti

Italy

Try the flag:
    -I\dm\src\phobos

"Alessandro" <Alessandro_member@pathlink.com> wrote in message news:ad7tks$2gq3$1@digitaldaemon.com...
> Hi,
> I've just installed the D compiler following requisites and instructions.
>
> However, when I try to compile a simple "Hello" program, the compiler
gives me
> the following error :
>
> Error : error reding file 'object.d'
>
> What happens?
>
> Thanks a lot.
>
> Alessandro Picetti
>
> Italy

"Walter" <walter@digitalmars.com> escribió en el mensaje news:ad8cjp$31eo$2@digitaldaemon.com...
> Try the flag:
>     -I\dm\src\phobos
>

It seems to be very common. Why don't you make the compiler to automatically look for that path? Then the -I flag would only modify the default.

"Carlos" <carlos8294@msn.com> wrote in message news:ad99c8$10d0$1@digitaldaemon.com...
>
> "Walter" <walter@digitalmars.com> escribió en el mensaje news:ad8cjp$31eo$2@digitaldaemon.com...
> > Try the flag:
> >     -I\dm\src\phobos
> It seems to be very common. Why don't you make the compiler to
automatically
> look for that path? Then the -I flag would only modify the default.

Good question. The answer is I don't like hardcoded paths in the executables <g>.

"Walter" <walter@digitalmars.com> wrote in message news:ad9ocd$1fsl$1@digitaldaemon.com...

> "Carlos" <carlos8294@msn.com> wrote in message news:ad99c8$10d0$1@digitaldaemon.com...
> >
> > "Walter" <walter@digitalmars.com> escribió en el mensaje news:ad8cjp$31eo$2@digitaldaemon.com...
> > > Try the flag:
> > >     -I\dm\src\phobos
> > It seems to be very common. Why don't you make the compiler to
> automatically
> > look for that path? Then the -I flag would only modify the default.
>
> Good question. The answer is I don't like hardcoded paths in the
executables
> <g>.

It's not necessary such, by the way. Mine version is
E:\Language\DMD\src\phobos =)
Maybe a config file, or an environment variable?

Have it search GetModulePath\..\lib if it can't find the import library anywhere else.  That's hardcoded yet relative to the compiler \bin folder; it's not quite so bad.  ;)  And, lib is the standard folder in the dmd distribution.  This would be equivalent to C's #include <sysheader.h> yet D would not have to require special syntax for system imports.

Since DMD is a Win32 executable, the proper Way of Doing Things on Windows these days is to store these sort of paths in the registry.  It's part of the compiler installation process and is not hardcoded.

Sean

"Walter" <walter@digitalmars.com> wrote in message news:ad9ocd$1fsl$1@digitaldaemon.com...
>
> "Carlos" <carlos8294@msn.com> wrote in message news:ad99c8$10d0$1@digitaldaemon.com...
> >
> > "Walter" <walter@digitalmars.com> escribió en el mensaje news:ad8cjp$31eo$2@digitaldaemon.com...
> > > Try the flag:
> > >     -I\dm\src\phobos
> > It seems to be very common. Why don't you make the compiler to
> automatically
> > look for that path? Then the -I flag would only modify the default.
>
> Good question. The answer is I don't like hardcoded paths in the
executables
> <g>.

Environment variables are old school.

Mine's installed in C:\DMD\src\phobos, because that's where the few D samples' script seemed to want to look for it.

Installation into the root is old school and is annoying.  Programs are supposed to install into the Program Files folder by default.

Sean

> It's not necessary such, by the way. Mine version is
> E:\Language\DMD\src\phobos =)
> Maybe a config file, or an environment variable?

"Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:ad9rlb$1lpi$1@digitaldaemon.com...

> Have it search GetModulePath\..\lib if it can't find the import library anywhere else.  That's hardcoded yet relative to the compiler \bin folder; it's not quite so bad.  ;)  And, lib is the standard folder in the dmd distribution.  This would be equivalent to C's #include <sysheader.h> yet
D
> would not have to require special syntax for system imports.

Yes, agreed. I think it is the best way. Used it in my "compiler" =) stuff myself. Very convenient to the end-users - just unzip the archive, and compiler's ready.

Also an automatic installer that set it all up would be good. Or even a
setup program that first searches the most likly places.  I agree that It's
a frustraion to new users to have to type
-I\dm\src\phobos.

If it doesn't find the phobos libary in a list of most likly places, it could give the user the option to search for it and record it in a local file.

I've written such thing myself and there not that hard.

"Pavel Minayev" <evilone@omen.ru> wrote in message news:adaa8u$4ht$1@digitaldaemon.com...
> "Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:ad9rlb$1lpi$1@digitaldaemon.com...
>
> > Have it search GetModulePath\..\lib if it can't find the import library anywhere else.  That's hardcoded yet relative to the compiler \bin
folder;
> > it's not quite so bad.  ;)  And, lib is the standard folder in the dmd distribution.  This would be equivalent to C's #include <sysheader.h>
yet
> D
> > would not have to require special syntax for system imports.
>
> Yes, agreed. I think it is the best way. Used it in my "compiler" =) stuff myself. Very convenient to the end-users - just unzip the archive, and compiler's ready.
>
>

Sean L. Palmer wrote:
> Environment variables are old school.
> 
> Mine's installed in C:\DMD\src\phobos, because that's where the few D
> samples' script seemed to want to look for it.
> 
> Installation into the root is old school and is annoying.  Programs are
> supposed to install into the Program Files folder by default.

windows isn't THE ONLY operating system... IMHO