www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - dmake error

reply "news.digitalmars.com" <gtbass studiotekne.com> writes:
Hello,

I've changed the configfile and env_LIB paths in dmake for my own use as 
follows:

    //String configfile="c:\\dmd\\bin\\sc.ini";
    String configfile="D:\\...\\dmd\\bin\\sc.ini";

    //char [100] env_LIB=r"LIB=c:\dm\lib;c:\dmd\lib";
    char [100]env_LIB = r"LIB=D:\\...\\dm\\lib;D:\\...\\dmd\\lib";

When I try to make a simple Win32 D program (a modified sample), I get the 
following error:

    Error: std\c\windows\windows.d: path not found

I can compile my program manually with dmd.exe as follows:

    dmd main graphics gdi32.lib main.def

I'd appreciate some help resolving this issue.  The error message doesn't 
appear in dmake.d, so I suspect dmake.exe might be causing this problem when 
it calls dmd.exe.

Thanks,
Garett 
Nov 14 2004
parent reply Thomas =?UTF-8?B?S8O8aG5l?= <thomas-dloop kuehne.cn> writes:
news.digitalmars.com schrieb am Montag, 15. November 2004 00:30:
 I've changed the configfile and env_LIB paths in dmake for my own use as
 follows:
 
     //String configfile="c:\\dmd\\bin\\sc.ini";
     String configfile="D:\\...\\dmd\\bin\\sc.ini";
 

I use Windows platforms rarely, but could you please explain what the effects of "..." is supposed to be? I'm aware of "." as well as "..", though haven't heart of "...". Thomas
Nov 14 2004
next sibling parent "Garett Bass" <gtbass studiotekne.com> writes:
I just inserted elipses in place of the long path to my dmd 
folder.  The actual path is 
"D:\Code\Compilers\D\dmd\bin\sc.ini".  Sorry for the 
confusion.


"Thomas Khne" <thomas-dloop kuehne.cn> wrote in message 
news:cn99o7$odt$1 digitaldaemon.com...
 news.digitalmars.com schrieb am Montag, 15. November 2004 
 00:30:
 I've changed the configfile and env_LIB paths in dmake 
 for my own use as
 follows:

     //String configfile="c:\\dmd\\bin\\sc.ini";
     String configfile="D:\\...\\dmd\\bin\\sc.ini";

I use Windows platforms rarely, but could you please explain what the effects of "..." is supposed to be? I'm aware of "." as well as "..", though haven't heart of "...". Thomas

Nov 14 2004
prev sibling parent reply Daniel Keep <daniel.keep dummy.gmail.com> writes:
Dont' know if this still applies in the latest version, but back in the 
old days (heh), . meant current directory, .. meant parent, ... meant 
parent of parent, .... meant parent of parent of parent,... and so on.

I still occationally do that when I'm on a UNIX system :P

	-- Daniel

Thomas Khne wrote:
 news.digitalmars.com schrieb am Montag, 15. November 2004 00:30:
 
I've changed the configfile and env_LIB paths in dmake for my own use as
follows:

    //String configfile="c:\\dmd\\bin\\sc.ini";
    String configfile="D:\\...\\dmd\\bin\\sc.ini";

I use Windows platforms rarely, but could you please explain what the effects of "..." is supposed to be? I'm aware of "." as well as "..", though haven't heart of "...". Thomas

Nov 15 2004
parent reply Thomas =?UTF-8?B?S8O8aG5l?= <thomas-dloop kuehne.cn> writes:
Daniel Keep schrieb am Montag, 15. November 2004 10:28:
 Dont' know if this still applies in the latest version, but back in the
 old days (heh), . meant current directory, .. meant parent, ... meant
 parent of parent, .... meant parent of parent of parent,... and so on.
 
 I still occationally do that when I'm on a UNIX system :P

What shell are/were you using? I tried "..."/"...." in a bunch of shells and got only error messages. The notation of "the parrent of the parent" I know is "../..". Maybe "..." is an alias in your shell for "../.."? Thomas
Nov 15 2004
next sibling parent Daniel Keep <daniel.keep dummy.gmail.com> writes:
Sorry... it was something that only COMMAND.COM/CMD.EXE did.  It don't 
work in UNIX shells (that's what I meant--sometimes I forget it doesn't 
work :P)

ごめん!

	-- Daniel "Whoops, wrong shell!"

Thomas Kühne wrote:
 Daniel Keep schrieb am Montag, 15. November 2004 10:28:
 
Dont' know if this still applies in the latest version, but back in the
old days (heh), . meant current directory, .. meant parent, ... meant
parent of parent, .... meant parent of parent of parent,... and so on.

I still occationally do that when I'm on a UNIX system :P

What shell are/were you using? I tried "..."/"...." in a bunch of shells and got only error messages. The notation of "the parrent of the parent" I know is "../..". Maybe "..." is an alias in your shell for "../.."? Thomas

Nov 15 2004
prev sibling parent reply larrycowan <larrycowan_member pathlink.com> writes:
In all the Unix'es I have seen in 24 years (30% of them?) "..." is a valid file
name, even as a directory, and ./../.../... would be the file ... in the
subdirectory ... of the parent of the current directory.  Can't check linux
without rebooting, but I presume it's that way there also.  Win2k generally just
disallows it (Access denied), but "dir ...." tries to display ... as a directory
(and gives you File Not Found).  Haven't seen anywhere that "...", "...." were
grandparent, greatgrandparent, etc.  Where was this?

The use of ellipses to indicate left out directory names in a displayed pathname
has been common for a long time and is used by many windows programs and the OS
itself where there is not enough room to display the full pathname. 

In article <cna2li$227e$1 digitaldaemon.com>, Thomas =?UTF-8?B?S8O8aG5l?=
says...
Daniel Keep schrieb am Montag, 15. November 2004 10:28:
 Dont' know if this still applies in the latest version, but back in the
 old days (heh), . meant current directory, .. meant parent, ... meant
 parent of parent, .... meant parent of parent of parent,... and so on.
 
 I still occationally do that when I'm on a UNIX system :P

What shell are/were you using? I tried "..."/"...." in a bunch of shells and got only error messages. The notation of "the parrent of the parent" I know is "../..". Maybe "..." is an alias in your shell for "../.."? Thomas

Nov 15 2004
parent "Carlos Santander B." <carlos8294 msn.com> writes:
"larrycowan" <larrycowan_member pathlink.com> escribi en el mensaje 
news:cnc3fi$1ut5$1 digitaldaemon.com...
| In all the Unix'es I have seen in 24 years (30% of them?) "..." is a valid 
file
| name, even as a directory, and ./../.../... would be the file ... in the
| subdirectory ... of the parent of the current directory.  Can't check linux
| without rebooting, but I presume it's that way there also.  Win2k generally 
just
| disallows it (Access denied), but "dir ...." tries to display ... as a 
directory
| (and gives you File Not Found).  Haven't seen anywhere that "...", "...." were
| grandparent, greatgrandparent, etc.  Where was this?
|
| The use of ellipses to indicate left out directory names in a displayed 
pathname
| has been common for a long time and is used by many windows programs and the 
OS
| itself where there is not enough room to display the full pathname.
|

Win Me and Win 98, I think. Can't say about 95.

-----------------------
Carlos Santander Bernal 
Nov 16 2004