Re: gforth dos/win
- From: Krishna Myneni <krishnamyneni@xxxxxxxxxxxxx>
- Date: Thu, 06 Sep 2007 04:48:28 -0500
Ed wrote:
"Bernd Paysan" <bernd.paysan@xxxxxx> wrote in message news:doh2r4-re5.ln1@xxxxxxxxxxxxxxxxxxxx
...
The way to create Gforth from CVS on Windows is the same way as on Unix -
you just need to install Cygwin (with build tools) to get there.
Which is a problem in itself - and probably why Bill asked.
Downloading tens (hundreds?) of megabytes of tools and maybe
getting nowhere is not the Windows paradigm. Most users only
want the final EXE.
I don't know how many users use Gforth on Windows
...
Ask them - then you'll know whether it's worth supporting.
In the past, I've created a kForth EXE package for Windows/Cygwin. I no longer
do this. The problem with an EXE package is that if the user upgrades his basic
Cygwin installation, the EXE may no longer work with the new DLLs. It is too
much trouble to make EXE packages for every version of Cygwin and the associated
DLLs/libraries. It is much cleaner to simply build from source with the existing
Cygwin installation, and for the application to fully document needed tools and
libraries. That's the price to be paid for using a non-native application.
Krishna
.
- References:
- Re: gforth dos/win
- From: Ed
- Re: gforth dos/win
- From: Bernd Paysan
- Re: gforth dos/win
- From: Ed
- Re: gforth dos/win
- Prev by Date: Re: gforth dos/win
- Next by Date: Re: gforth dos/win
- Previous by thread: Re: gforth dos/win
- Next by thread: Re: gforth dos/win
- Index(es):
Relevant Pages
|