I was reading the readme in FPC\utils\fppkg and saw that there should be
a tool called fpmkconv that converts makefile.fpc to fpmake.pp files. I
just cannot find it in the FPC sources.
Darius
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
On Fri, 10 Aug 2007, wrote:
> One of my customers asked me if I can recompile a Delphi application that
> uses TDataSet
> descendants. Can someone tell me if FPC's TDataSet implementation is
> compatible with Delphi's?, or
> I must rewrite the whole application?.
The implementation is compat
On Sat, 11 Aug 2007, Darius Blaszijk wrote:
> I was reading the readme in FPC\utils\fppkg and saw that there should be a
> tool called fpmkconv that converts makefile.fpc to fpmake.pp files. I just
> cannot find it in the FPC sources.
fppkg does it by itself. The functionality has been integrat
On Fri, 10 Aug 2007, Darius Blaszijk wrote:
> Johann Glaser wrote:
> > Is there any documentation (like the things you've written in this
> > thread) in the Wiki? If not, I'd like to copy-paste (and clean up) your
> > discussion. Please point me to a place where the information best fits.
> >
Michael,
Thanks for explaining that, but.
I tried to convert a sample Makefile.fpc, but I keep getting the
following error message;
>fppkg convertmk Makefile.fpc
Loading global configuration from "C:\pp\bin\i386-Win32\fppkg.cfg"
Generating default compiler configuration in
"C:\pp\bin\i38
On Sat, 11 Aug 2007, Darius Blaszijk wrote:
> Michael,
>
> Thanks for explaining that, but.
>
> I tried to convert a sample Makefile.fpc, but I keep getting the following
> error message;
>
> >fppkg convertmk Makefile.fpc
> Loading global configuration from "C:\pp\bin\i386-Win32\fppkg.cfg
You're right. I don't have a clue why, but when I remove poNoConsole for
the TProcess it works. I attached a patch.
Unfortunately it still doesn't work. Fppkg cannot find the Makefile.fpc.
Output below.
>fppkg convertmk Makefile.fpc
Loading global configuration from "C:\pp\bin\i386-Win32\fppk
On Sat, 11 Aug 2007, Darius Blaszijk wrote:
> You're right. I don't have a clue why, but when I remove poNoConsole for the
> TProcess it works. I attached a patch.
>
> Unfortunately it still doesn't work. Fppkg cannot find the Makefile.fpc.
> Output below.
>
> >fppkg convertmk Makefile.fpc
> L
Michael Van Canneyt wrote:
fppkg mkconvert
Should be "fppkg convertmk" ;)
It will convert the Makefile.fpc in the current directory and compiles
and runs it. I just tested here, and it works fine.
Right, much better indeed :) But
I got the following error message:
Unknown name/valu
At 17:15 11-8-2007, you wrote:
Michael Van Canneyt wrote:
fppkg mkconvert
Should be "fppkg convertmk" ;)
It will convert the Makefile.fpc in the current directory and
compiles and runs it. I just tested here, and it works fine.
Right, much better indeed :) But
I got the following erro
Peter Vreman wrote:
I got the following error message:
Unknown name/value pair in compiler section : unittargetdir
Unknown name/value pair in clean section : files
Which is:
unittargetdir=./units/$(CPU_TARGET)-$(OS_TARGET)
files=$(wildcard ./units/$(CPU_TARGET)-$(OS_TARGET)/*$(OEXT)) \
$(w
At 18:37 11-8-2007, you wrote:
Peter Vreman wrote:
I got the following error message:
Unknown name/value pair in compiler section : unittargetdir
Unknown name/value pair in clean section : files
Which is:
unittargetdir=./units/$(CPU_TARGET)-$(OS_TARGET)
files=$(wildcard ./units/$(CPU_TARGET)-$
Peter Vreman wrote:
I got the following error message:
Unknown name/value pair in compiler section : unittargetdir
Unknown name/value pair in clean section : files
Which is:
unittargetdir=./units/$(CPU_TARGET)-$(OS_TARGET)
files=$(wildcard ./units/$(CPU_TARGET)-$(OS_TARGET)/*$(OEXT)) \
$(
Btw,
How would
./units/$(CPU_TARGET)-$(OS_TARGET)
be translated to fpmake.pp format?
Do we need to use a "Case Installer.OS of" construct or can we
implement$(CPU_TARGET) and $(OS_TARGET) as functions that return a
string with the current targets?
I would say just replace the macros with {$I
Darius Blaszijk schreef:
Do we need to use a "Case Installer.OS of" construct or can we
implement$(CPU_TARGET) and $(OS_TARGET) as functions that return a
string with the current targets?
I would say just replace the macros with {$I %FPCTARGETOS%} and {$I
%FPCTARGETCPU%} but how do others fee
Vincent Snijders wrote:
Darius Blaszijk schreef:
Do we need to use a "Case Installer.OS of" construct or can we
implement$(CPU_TARGET) and $(OS_TARGET) as functions that return a
string with the current targets?
I would say just replace the macros with {$I %FPCTARGETOS%} and {$I
%FPCTARGET
Darius Blaszijk schreef:
Vincent Snijders wrote:
Darius Blaszijk schreef:
Do we need to use a "Case Installer.OS of" construct or can we
implement$(CPU_TARGET) and $(OS_TARGET) as functions that return a
string with the current targets?
I would say just replace the macros with {$I %FPCTARG
I'm now trying to compile FlexCel v.2.5.3 (latest open source version
before it's bought by TMS) using FPC v.2.0.4 on Linux (Kubuntu 6.10
Feitsy). After adding IFDEFs here and there, finally FPC is able to
compile it. But, I don't know why FPC fails to linking program (to
executable) that uses
Three things needed in FPC:
1) Garbage collection. Anybody who's worked on apps with objects of objects
of objects of objects will see the value in this. If CMEM is used, can the
Boehm garbage collector be used? Even a resurrection of the split-heap stuff
into something more generalized (mini-heap
Hi,
I'm talking from my own knowledge and experience, and not in behalf of
anyone else...
On 8/12/07, JK Smith at Grid-Sky <[EMAIL PROTECTED]> wrote:
> Three things needed in FPC:
>
> 1) Garbage collection. Anybody who's worked on apps with objects of objects
> of objects of objects will see the
20 matches
Mail list logo
