Mail Archives: djgpp/1999/01/23/18:21:54
This is a multi-part message in MIME format.
--------------C21E3FF85EA6EFC5908F8378
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
I had the same problem with FPC. I am using rhide 1.4.7 running under Win98. I
tried 3 different schemes.
First, I replaced the GNU pascal compiler with FPC by setting the "use FPC"
box in the preferences. The resultant messages (from the redir utility) were:
This is RHIDE Version 1.4.7. Copyright (c) 1996-1998 by Robert H”hne
(Nov 15 1998 23:23:07)
executing: ppc386 -E- display.pas
return value: 1
and also, the program lost mouse control.
I then tried the ctrl-o option for the source file where I set "user" compiler
, typed in the exectuion line : "ppc386 $(SOURCE_FILE)", and set the error
process to FPC. here I got:
This is RHIDE Version 1.4.7. Copyright (c) 1996-1998 by Robert H”hne
(Nov 15 1998 23:23:07)
executing: ppc386 display.pas
return value: 1
Howerver, here I get the correct error messages in the error window of RHIDE.
But I still lost mouse control.
I next tried to run RHIDE from a DOS prompt and repeated the second step. I
used cwsdpmi and a mouse driver. I didn't loose mouse control after
compilation, but FPC said that it could not run in DOS mode.
Here is the error messages I got from just executing "ppc386 display.pas" from
the command prompt:
Free Pascal Compiler version 0.99.10 [1998/12/21] for i386
Copyright (c) 1993-98 by Florian Klaempfl
Target OS: Win32 for i386
Compiling display.pas
display.pas(2,2) Note: Ignored compiler switch $F
Compiling E:\FPC\RTL\WIN32\crt.pp
crt.pp(1,6) Error: Illegal unit name: WINCRT
crt.pp(116,1) Fatal: There were 1 errors compiling module, stopping
I am using FPC because I am trying to compile a set of Turbo Pascal (7.0)
project files and got the impression that FPC would be the closest TP 7.0.
However, if I could find a port of GNU pascal, I could use that if it is
somewhat compatable with TP 7.0.
> >
> > I can't read any message of FPC, because stdout is redirected. So I have
> > to go to a shell and execute ppc386 by hand.
>
> Please run RHIDE in the following way (on DJGPP)
>
> redir -e err rhide -dct YOUR_PROJECT
>
> after compiling, look in the file err, where the
> exact commands are show, how the compiler is called
> and there is also written, in which files stderr and
> stdout are redirected when the compiler is executed.
> The look in those file for the output of the compiler
> run.
>
> On Linux you should use
>
> rhide -dct YOUR_PROJECT 2&>err
>
> (or like this)
>
> And a last note: The support for FPC is not so well
> implemented, since there seems not so much interest
> of it, but maybe this will change in the future.
>
--------------C21E3FF85EA6EFC5908F8378
Content-Type: text/x-vcard; charset=us-ascii;
name="pvanbell.vcf"
Content-Description: Card for Paul Van Bellinghen
Content-Disposition: attachment;
filename="pvanbell.vcf"
Content-Transfer-Encoding: 7bit
begin:vcard
n:Van Bellinghen;Paul
x-mozilla-html:FALSE
org:Lockheed Martin Fairchild Systems
version:2.1
email;internet:pvanbell AT idsi DOT net
title:Staff Analyst
note:businessl e-mail: paul DOT vanbellinghen AT lmco DOT com
x-mozilla-cpt:;0
fn:Paul Van Bellinghen
end:vcard
--------------C21E3FF85EA6EFC5908F8378--
- Raw text -