[fpc-pascal] FPC in DOS environment

[Daniel Franzini]

today (quite late) i've got myself some improvements...so far i was
unable to even compile some parts od fpc within freedos (inside
virtual pc)...the IDE that comes with fpc2.0.5 does not even start at
all...now i can compile correctly all the packages needed to build the
ide (as Pierre pointed)...the problem now is that make is crashing
when i do

make clean all DEBUG=1 OPT=-gl

my guess is that the DPMI support on FreeDOS is somehow incompatible
with the standard cwsdpmi (is there any other DPMI server i can use in
order to achieve 100% compatibility with go32v2?)...right now i'm
making a try with the standard cwsdpmi (provided in the fpcbuild
package)...i will post the results soon

now, i think i can perfom a few tests like you pointed with the ide
compiled with debug suport...question: is the DEBUG=1 parameter for
make to compile with debug support or to instruct the make to be
verbose???

it was a bunch of tricky to get it working correctly...seems that fpc
and freedos are not quite good friends yet...fpc AND freedos relies on
the same env var for completely different things....both of them have
the CFGFILE var...to fpc it means the fpc.cfg standard configuration
file....to freedos it means the standard config.sys-like file...the
(temporary) solution was to unset the cfgfile to freedos and let fpc
use it in his way then setting it again for freedos...is there a
better solution in the sense of changing the makefile (or
makefile.fpc) on the fpc side??

On 1/16/07, Pierre Muller <pierre at freepascal.org> wrote:
>
>
>  The current 2.0 fixes branch should be more
>  stable.
>
>   Could you please try to download and install
> ftp://ftpmaster.freepascal.org/pub/fpc/snapshot/v20/i386-go32v2/fpc-2.0.5dos.zip
>   The file datestamp should be January 15. 2007,
> or later.
>   Let's say that you unpack this into
>   /pas/snp205 directory.
>   he snapshot ppc386 will then be in
>   /pas/snp205/bin/go32v2 directory.
>
>   Unzip the file and test the IDE,
> by compliling and stepping through a simple source.
> (like the ide/test.pas file).
>
>   Please report if this is working OK for you,
> or any problems you might encounter.
>
>
>   A second step would be to recompile the IDE
>  from the current 2.0.5 sources, with debugger information.
>
>   First download and install
> ftp://ftpmaster.freepascal.org/pub/fpc/snapshot/v20/source/fpcbuild.zip
>   You will also need to download and install the GDB libraries:
> the zip file is:
> ftp://ftpmaster.freepascal.org/pub/fpc/contrib/libgdb/v6.1.1/go32v2-v601.zip
>
>   Unzip all librairies (lib*.a files)
> into \pas\libgdb\go32v2 for example
>
> change to fpcbuild/fpsrc/ide directory
>
>   You need to inform where the GDB librairies are,
>   for this you will need to set GDBLIBDIR variable.
>
> set GDBLIBDIR=/pas/ligdb/go32v2
>   should work for this.
>
>   After this, you will need to recompile several directories
>
>   make -C ../rtl DEBUG=1
>   make -C ../packages/base/graph DEBUG=1
>   make -C ../packages/base/regexpr DEBUG=1
>   make -C ../packages/base/gdbint DEBUG=1
>   make -C ../fv DEBUG=1
>   make clean all DEBUG=1  OPT=-gl
>
>
>   If everything works fine, you should have at that point a
>   fp.exe file that is about 10Mb in size.
>
>   The problem for me, (I am stick for the moment on a windows 2000
>   computer), is that the IDE tends to crash randomly, but I don't know
>   if it comes from the IDE or from the poor Dos emulation
>   of Windows 2000...
>
>   Tell me if you succeed in compiling this and if
> the generated IDE is usable, or gives you useful information
> when crashing (the -gl option, should create a verbose stack
> on crashes).
>
>   Thanks for trying this out,
>
>   By the way, testers for emx, os/2 or wdosx targets would also
> be most welcomed,
>
> Pierre
> _______________________________________________
> fpc-pascal maillist  -  fpc-pascal at lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-pascal
>


-- 
Daniel

"Let us change our traditional attitude to the construction of
programs. Instead of imagining that our main task is to instruct a
computer what to do, let us concentrate rather on explaining to human
beings what we want a computer to do." (Donald Knuth)

"Yes, technogeeks can be funny, even if only to each other."
(http://www.boogieonline.com/revolution/science/humor/)"

"Man is driven to create; I know I really love to create things. And
while I'm not good at painting, drawing, or music, I can write
software." (Yukihiro Matsumoto, a.k.a. ``Matz'')