On Fri, December 2, 2011 11:27, Michael Van Canneyt wrote: > 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: . . >>>> 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.
I understand this now, but before Marco's post I thought that the reason for the current situation was simply the fact that you always built under Linux rather than that it would never work otherwise. Tomas _______________________________________________ fpc-devel maillist - [email protected] http://lists.freepascal.org/mailman/listinfo/fpc-devel
