View previous topic :: View next topic |
Author |
Message |
sylverpyro
Joined: 23 May 2006 Posts: 28
|
Posted: Mon Jun 26, 2006 10:59 am Post subject: build 3.02 - module object cannot read file 'object.d' |
|
|
Just updated to build 3.02 to try and build Derelict. When I attempted to run the buildme.d script for Derelict I got a bunch of sh: @rm: command not found errors, so I tried to just straight up build the buildme.d script.
Code: | :~/Software/Linux/D/Derelict/Derelict$ build buildme.d |
To which build said:
Code: | object.d: module object cannot read file 'object.d' |
I checked my dmd.conf file and the phobos files are pointed to correctly. Also tried with the -LIBPATH= switch with no luck. Envoking the dmd compiler directly also seems to work. I also tried to run build with the -V switch to try and get some more meaning out of the error, but it still only gave me the one line of code. Any ideas? |
|
Back to top |
|
|
keinfarbton
Joined: 03 Dec 2005 Posts: 224 Location: Stuttgart - Germany
|
Posted: Thu Jul 06, 2006 4:00 pm Post subject: |
|
|
not finding object.d normally means, that the sources of phobos were not in the include path.
Edit /etc/dmd.conf, if it does not exist, copy it from the dmd package.
or add -I<path> to the commandline. |
|
Back to top |
|
|
wilsonk
Joined: 21 Apr 2006 Posts: 40
|
Posted: Sun Jul 09, 2006 6:00 pm Post subject: |
|
|
Hello all,
I seem to get a similar error message:
sprite.d: module object cannot read file 'sprite.d'
when I use an include like "-I~/Arcgames/"....this seems to be coming from the "~" not being expanded to my home directory. If I use a fully qualified directory like "-I/home/wilsonk/Arcgames" then the compilation works fine.
Just thought I would let you know. Maybe I missed this limitation under Linux, in the documentaiton somewhere.
Kelly Wilson
P.S. I am using build 2.9 so maybe I just need to upgrade?!? |
|
Back to top |
|
|
csauls
Joined: 27 Mar 2004 Posts: 278
|
Posted: Sun Jul 09, 2006 11:01 pm Post subject: |
|
|
You know, I seem to vaguely recall a couple years ago us all discussing a strange error that turned out to be caused by '~' characters not getting expanded... the same old error coming back to haunt us again somehow, or something new yet related, perhaps? I haven't been able to dig up the original discussion though. _________________ Chris Nicholson-Sauls |
|
Back to top |
|
|
Derek Parnell
Joined: 22 Apr 2004 Posts: 408 Location: Melbourne, Australia
|
Posted: Mon Jul 10, 2006 6:44 am Post subject: |
|
|
csauls wrote: | You know, I seem to vaguely recall a couple years ago us all discussing a strange error that turned out to be caused by '~' characters not getting expanded... the same old error coming back to haunt us again somehow, or something new yet related, perhaps? I haven't been able to dig up the original discussion though. |
I'm pretty sure that ~ doesn't get expanded if its inside a quoted string. Maybe Build will have to do this for you. So if a file name begins with '~' then I'll replace that with the contents of $HOME symbol. How does that sound? _________________ --
Derek
skype name: derek.j.parnell |
|
Back to top |
|
|
wilsonk
Joined: 21 Apr 2006 Posts: 40
|
Posted: Mon Jul 10, 2006 10:20 pm Post subject: |
|
|
Hey Derek,
The idea of replacing a double-quoted ~ with the contents of $HOME sounds good to me. It should fix things and save me some typing
Thanks,
K.Wilson |
|
Back to top |
|
|
|