1. Ecw for Borland
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.
Compiling manually and using upx works. The winwire demo compiles to a 60k
executable, and the generic win32lib demo to 142k.
@echo off
rem goecwb.bat
if "%1"=="" goto usage
if exist %1 goto usage
%eudir%\ecwb\ecw %1.exw
bcc32 -w- -5 -tW -e%1.exe *.c %eudir%\ecwb\ecw.lib
upx %1.exe
del *.c
del main_.h
del emake.bat
del objfiles.lnk
del *.obj
del %1.tds
goto done
:usage
echo usage: goecwb file --file.exw assumed, uses bcc32
:done
2. Re: Ecw for Borland
- Posted by Euman <euman at BELLSOUTH.NET>
Nov 04, 2000
-
Last edited Nov 05, 2000
Have you tried copying over ecw.lib in
\euphoria\bin with the version of ecw.lib
that came with the Borland version
you probably would need to also copy
over euphoria.h in
\euphoria\include with that of the version
supplied with the Borland version..
If you've already done this and it still doesnt
work you probably need to try and download
the Borland version again...
My Borland version works fine....
euman at bellsouth.net
----- Original Message -----
From: "Ken Roger" <kennethroger at PRODIGY.NET>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Saturday, November 04, 2000 6:50 PM
Subject: Ecw for Borland
> 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.
>
> Compiling manually and using upx works. The winwire demo compiles to a 60k
> executable, and the generic win32lib demo to 142k.
>
> @echo off
> rem goecwb.bat
> if "%1"=="" goto usage
> if exist %1 goto usage
> %eudir%\ecwb\ecw %1.exw
> bcc32 -w- -5 -tW -e%1.exe *.c %eudir%\ecwb\ecw.lib
> upx %1.exe
> del *.c
> del main_.h
> del emake.bat
> del objfiles.lnk
> del *.obj
> del %1.tds
> goto done
> :usage
> echo usage: goecwb file --file.exw assumed, uses bcc32
> :done
>
3. Re: Ecw for Borland
- Posted by Ken Roger <kennethroger at PRODIGY.NET>
Nov 04, 2000
-
Last edited Nov 05, 2000
Euman writes:
>--copying over ecw.lib in \euphoria\bin--etc.
Yes, I've done that. I've also tried both the free and the complete
editions.
If watcom is set, it writes an emake for wcc, otherwise it writes one for
lccwin even though no lcc environment variable is set. I've even tried
changing the name of my lcc directory. I don't normally have a borland
environment variable, but set one for this and it didn't help.
Anyway, I've got a workaround (and upx does wonders for both lcc and bcc32).
---Thanks
4. 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
5. Re: Ecw for Borland
- Posted by Ken Roger <kennethroger at PRODIGY.NET>
Nov 04, 2000
-
Last edited Nov 05, 2000
Robert Craig writes--
>ecw is looking for ...borland\bcc... somewhere on your PATH.
I guess that's the problem. I have a non-free Builder-4 in the Borland
directory so I installed the free stuff in c:\bcc55.
Thanks.
6. Re: Ecw for Borland
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
7. Re: Ecw for Borland
- Posted by Derek Parnell <dparnell at BIGPOND.NET.AU>
Nov 09, 2000
-
Last edited Nov 10, 2000
Robert,
this might be a bug in the translator. The 'dir' function is not returning a
file-found condition.
The program below works in the interpretor but not when compiled (Borland
5.5).
--------------------
include file.e
include msgbox.e
object dirResult
sequence aMsg
integer in
sequence FileName
FileName = "testdir.exw"
dirResult = dir(FileName)
if atom(dirResult)
then
aMsg = sprintf("The source file '%s' cannot be found.", {FileName})
in = message_box (aMsg, " Error ", 0)
else
aMsg = sprintf("File is %s", {dirResult[1][D_NAME]})
in = message_box (aMsg, " Good ", 0)
end if
--------------------
------
Derek Parnell
Melbourne, Australia
(Vote [1] The Cheshire Cat for Internet Mascot)
8. Re: Ecw for Borland
Derek Parnell writes:
> this might be a bug in the translator. The 'dir' function
> is not returning a file-found condition.
dir() hasn't been completed yet for Borland or LccWin.
This is mentioned near the top of the readme.txt file.
I think it always returns -1. I'll try to finish it for the
next release. I think dir() is the only functionality missing
in the Borland version.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
