On 4 December 2011 18:11, Marco van de Voort wrote: > > Because then you can't have multiple projects using the same content and > sources in different paths.
I'm afraid I don't understand your point? fpdoc is about documenting API's. Those are rather specific to a single project. Could you supply a concrete example backup your statement? I already mentioned that macros in the unit paths could be used to fix path issues. In the case of FPC's RTL for example. Simply switch for example a $(fpc_src) macro you can compile help for FPC 2.4.4 or 2.7.1. The unit path could even contain TargetOS and TargetCPU macros if you wanted to differentiate further. > One more rigidity added. I see more flexibility. -- Regards, - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://fpgui.sourceforge.net _______________________________________________ fpc-devel maillist - [email protected] http://lists.freepascal.org/mailman/listinfo/fpc-devel
