Hi

Is fpdoc supposed to handle multiple include paths with one -Fi parameter? eg:
--input='-Fi../src/corelib;../src/corelib/x11
../src/corelib/fpg_utils.pas' --descr=xml/corelib/fpg_utils.xml \

The above line fails. fpdoc cannot find the include file used my fpg_utils.pas unit. Changing that line to rather use two -Fi parameters seems to fix it. But isn't fpdoc supposed to can handle multiple paths in one -Fi param?

The modified (and fixed) version of the above line: --input='-Fi../src/corelib -Fi../src/corelib/x11
../src/corelib/fpg_utils.pas' --descr=xml/corelib/fpg_utils.xml \

I'm using fpdoc from FPC 2.4.1 and FPC 2.5.1 under Linux.

No. You must specify a -Fi per path. It doesn't split the path. (coincidentally, the path separator is : on linux, not ; :))

Michael.

Michael Van Canneyt wrote

No. You must specify a -Fi per path. It doesn't split the path. (coincidentally, the path separator is : on linux, not ; :))

At least for the fpc/ppcXXX binaries, the path separator is ";" on all platforms.

Jonas

Op 2010-06-08 13:26, Michael Van Canneyt het geskryf:

No. You must specify a -Fi per path. It doesn't split the path.

Umm, but FPC allows it in fpc.cfg file, so maybe allowing it in fpdoc will be more consistent don't you think. It should be rather easy to add.

eg:
A sample from FPC generated ~/.fpc.cfg file shows two examples where multiple paths are allowed:

-----------------------------
## searchpath for includefiles
#-Fi/pp/inc;/pp/rtl/inc

...

# searchpath for libraries
-Fl/usr/lib/gcc/i486-linux-gnu/4.0.2
#-Fl/pp/lib
#-Fl/lib;/usr/lib
-----------------------------

(coincidentally, the path separator is : on linux, not ; :))

I know, and tried both just too see. But as Jonas has said, FPC itself uses semi-colon on all platforms, hence the reason I tried semi-colon first.

Regards,
- Graeme -

Graeme Geldenhuys wrote

I know, and tried both just too see. But as Jonas has said, FPC itself uses semi-colon on all platforms, hence the reason I tried semi-colon first.

The compiler should actually be changed to use the platform-specific separator, because a directory on a unix platform can perfectly contain a semi-colon.

Jonas

Op 2010-06-08 14:23, Jonas Maebe het geskryf:

The compiler should actually be changed to use the platform-specific separator, because a directory on a unix platform can perfectly contain a semi-colon.

I guess, but do you really want to go down that route? :-) Linux (and probably other *nix's too) support just about any character in a path or filename - even non-visible escaped characters. In fact, if I am not mistaken Linux supports any character (even escaped or non-visual) except for / and NULL. :-)

Regards,
- Graeme -

Jonas Maebe schrieb: because a directory on a unix platform can perfectly contain a semi-colon.

That applies to Windows too.

Hello FPC-Pascal,

you wrote

> I know, and tried both just too see. But as Jonas has said, FPC > itself uses > semi-colon on all platforms, hence the reason I tried semi-colon > first.

JM> The compiler should actually be changed to use the platform-specific JM> separator, because a directory on a unix platform can perfectly JM> contain a semi-colon.

A Windows folder can have a ';' also.

------------------------------------------
F:\>md "Dot;comma"

F:\>dir dot*

Volume in drive F is unlabeled Serial number is 40AC:DFAA Directory of F:\dot*

8/06/2010 18:29 <DIR> Dot;comma
0 bytes in 0 files and 1 dir
15.094.943.744 bytes free
-----------------------------------------