Hi All,
I found the problem using a process of elimination and found the the
IFDEF LINUX define causes "makeskel" to crash. Luckily I don't need
the Kylix ifdef's anymore, so was able to remove it and continue
working with makeskel.
Still not sure what in the IFDEF LINUX caused the problem thou
Hi,
Finally fixed a long standing issue I had with these two apps. :-)
Using fpdoc and makeskel on a system that has multiple versions of FPC
installed, I never know what version of each of these tools I am
running.
Now the version information is included below the title line. Version
number is
On Thursday 14 September 2006 07:06, Graeme Geldenhuys wrote:
> Still not sure what in the IFDEF LINUX caused the problem though...
> Does makeskel and FPC support the "If Declared(...)" syntax?
This might not be a big help with your specific problem, but the set if IFDEFs
doesn't quite work the
I haven't used Kylix 3 Pro for over a year. I had my copy of Kylix
fully patched - not sure if that made a difference. The IFDEF's did
work at that stage though. Strange I guess, seeing that yours doesn't.
If I remember correctly, I got all those ifdef's from the Indy
project.
Anyway, Kylix wasn
On Thursday 14 September 2006 09:18, Graeme Geldenhuys wrote:
> I haven't used Kylix 3 Pro for over a year. I had my copy of Kylix
> fully patched - not sure if that made a difference. The IFDEF's did
> work at that stage though. Strange I guess, seeing that yours doesn't.
Yeah, that's definitely
People, just found an error in the consolerunner/testrunner.pp demo
application. It's constructor
and destrutor differs from the frameworktest sample in the tests directory.
The correct methods are:
constructor TTestRunner.Create(AOwner: TComponent);
begin
inherited Create(AOwner);
FXMLResul
Leonardo M. Ramé ha scritto:
> People, just found an error in the consolerunner/testrunner.pp demo
> application. It's constructor
> and destrutor differs from the frameworktest sample in the tests directory.
>
> The correct methods are:
>
> constructor TTestRunner.Create(AOwner: TComponent);
>
On 14/09/06, Dean Zobec <[EMAIL PROTECTED]> wrote:
mechanism to build the test cases. But there IS an error in the
testrunner in the demo directory, the unit testreport was substituted
with the new xmlreporter that lacks some methods used by the runner.
For Vincent: what if we simply use here you
> But there IS an error in the
> testrunner in the demo directory, the unit testreport was substituted
> with the new xmlreporter that lacks some methods used by the runner.
> For Vincent: what if we simply use here your text test runner in the
> lazarus/test directory? I'll prepare a patch.
The a
