On Fri, 2 Dec 2011, Tomas Hajny wrote:
On Thu, December 1, 2011 13:27, [email protected] wrote:
On Thu, 1 Dec 2011, Marco van de Voort wrote:
In our previous episode, Hans-Peter Diettrich said:
commandline, which are not handled properly by the Windows shell. I
fixed this manually, by editing the Makefile.
Next I get the following error messages:
Afaik the docs are hardwired for Linux. Even if you are on host windows,
you
should enter paths and defines like it was Linux.
I already committed a fix so that the linux paths are appended in windows.
Is this the right fix? Shouldn't it be possible to generate docs based on
other targets as an option? Or possibly something like a superset for all
targets (showing the differences)? The current situation is that
Linux-specific extensions to common units (e.g. variables, functions,
etc.) are always included in the docs, while extensions/additions existing
on other targets are not documented at all (and just adding their
description to the respective .xml files wouldn't make any difference to
that if I understand it correctly)...
The patch changes nothing to the content of the docs, it just makes sure that
the parser finds all files on Windows.
If there are any platform-specific identifiers, the docs have always contained
the linux-specific ones.
The patch changes nothing about this.
Michael.
_______________________________________________
fpc-devel maillist - [email protected]
http://lists.freepascal.org/mailman/listinfo/fpc-devel
