D People,

    	D compiler use the LIB environment variable to search the runtime
library for linking.
    	But this variable, with INCLUDE and PATH, is used for most of all
compilers, interpreters, middleware... And every setup add yours... For
example in command.com you have a limit ( 80 char ? ) and this could be
a potential problem.
    	Why not change the name for another name specific ? You need
configure the variable anyway?

Sugestions, Comments, Negatives ?

Juarez Rudsatz

This reliance on 1980 technology is why command line tools suck ass.

I *never* want to compile a project from a command line.  I want to set up a project via some kind of make file and either have the IDE / Editor build it or double-click some file to cause the build.

Ideally every piece of information the compiler and linker need could be
stored in either (A) the makefile (B) a "project build settings" file in the
project folder or (C) in some file where the compiler resides or (D) in the
registry.

There's always that lame limit on how long a command line can be, which makes it infeasible to do one-step build and link via command line for large projects.

I don't expect the D specification to require any kind of build system, but you'd think the tools people would get a clue.

Walter actually has a pretty nice script engine built into SC, it's like Make in a lot of ways.  I just wish the tools didn't require getting info from environment variables or command line parameters.

Sean

"Juarez Rudsatz" <juarez@correio.com> wrote in message news:Xns921FE77FA9713juarezcom@63.105.9.61...
> D People,
>
>     D compiler use the LIB environment variable to search the runtime
> library for linking.
>     But this variable, with INCLUDE and PATH, is used for most of all
> compilers, interpreters, middleware... And every setup add yours... For
> example in command.com you have a limit ( 80 char ? ) and this could be
> a potential problem.
>     Why not change the name for another name specific ? You need
> configure the variable anyway?
>
> Sugestions, Comments, Negatives ?
>
> Juarez Rudsatz

"Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:ad9a3u$119n$1@digitaldaemon.com...
> Walter actually has a pretty nice script engine built into SC, it's like Make in a lot of ways.  I just wish the tools didn't require getting info from environment variables or command line parameters.

No surprise there, it is derived from the source to make. <g>

I needed it in order to run test suites. It has a nifty feature where a block of commands can be run over and over with a factorial combination of arguments. Very handy for compiling a sample program with every possible combination of optimization, debug, memory model and code gen flags. The test suite is more or less a compilation of every bug report received for the last 20 years.

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

> Ideally every piece of information the compiler and linker need could be
> stored in either (A) the makefile (B) a "project build settings" file in
the
> project folder or (C) in some file where the compiler resides or (D) in
the
> registry.

(E) from the code of the program itself. Some special construct to order the compiler to link with some object or library file could be useful.

> Walter actually has a pretty nice script engine built into SC, it's like Make in a lot of ways.  I just wish the tools didn't require getting info from environment variables or command line parameters.

Whoa, not so fast! I agree that env variables are bad (config files are
better), but hey, leave the command line to us UNIX fans! =)

"Pavel Minayev" <evilone@omen.ru> wrote in message news:ad9r09$1j8e$1@digitaldaemon.com...
> "Sean L. Palmer" <seanpalmer@earthlink.net> wrote in message news:ad9a3u$119n$1@digitaldaemon.com...
>
> > Ideally every piece of information the compiler and linker need could be
> > stored in either (A) the makefile (B) a "project build settings" file in
> the
> > project folder or (C) in some file where the compiler resides or (D) in
> the
> > registry.
>
> (E) from the code of the program itself. Some special construct to order the compiler to link with some object or library file could be useful.
>
> > Walter actually has a pretty nice script engine built into SC, it's like Make in a lot of ways.  I just wish the tools didn't require getting
info
> > from environment variables or command line parameters.
>
> Whoa, not so fast! I agree that env variables are bad (config files are
> better), but hey, leave the command line to us UNIX fans! =)
>


That is why he says he wishes that the tools do not *require* parameters from the command line. So that you can use the command line, while he can use an IDE / Editor / Makefile / ...


--
Stijn
OddesE_XYZ@hotmail.com
http://OddesE.cjb.net
_________________________________________________
Remove _XYZ from my address when replying by mail