Re: Ecw for Borland

new topic     » goto parent     » topic index » view thread      » older message » newer message

Hi Robert,
looking for a hardcoded value in somebody's PATH is a very non-portable way
of doing this. For example, I often install software in places other than
the default area. My Borland compiler is installed in "f:\Borland\C5.5\BIN".
I'm glad I noticed this note before I had a chance to play with the
translator!

Instead of scaning the path, why don't you have a setup program that either
scans for the libraries you need or let the user tell you where they are.
Then save this in a registry key. And anytime you can't find the libraries,
('cos maybe I moved them) you can ask again for there location.

------
Derek Parnell
Melbourne, Australia
(Vote [1] The Cheshire Cat for Internet Mascot)

----- Original Message -----
From: "Robert Craig" <rds at ATTCANADA.NET>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Sunday, November 05, 2000 4:18 PM
Subject: Re: Ecw for Borland


> Ken Roger writes:
> > I couldn't get the new Borland ecw to generate emake.bat for bcc32.
> > It insists on generating it for lcc even though there is no lcc
> > environment variable and there is a (otherwise unused) bcc
> > environment variable.
>
> Assuming you don't have a WATCOM environment variable,
> ecw is looking for ...borland\bcc... somewhere
> on your PATH.
>
> I suppose in the next release, I could add a command-line option
> to select the C compiler, but I would still need to know where
> your borland\bcc55\lib and borland\bcc55\include directories are.
>
> Regards,
>    Rob Craig
>    Rapid Deployment Software
>    http://www.RapidEuphoria.com

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu