> Oh, well, then it's the *expanded* path that triggers the warnings, not
> the statement in the sources. This is obviously Windows specific because
> Windows uses '\' in the path whereas Linux uses '/' (of course) which
> doesn't trigger the "unknown command" warning.

Indeed.
The crux is that the doxygen comment had "$(path)" rather than the escaped form "\$(path)" and so the environment $PATH was being read in and expanded - which doxygen (unsurprisingly) did not like much.

The escaped form "\$(path)" works fine though.



Leonardo MW Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL
A company registered in England & Wales.  Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

-- 
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/0e704e6c823c42c4b32b7162c09a3bce%40leonardocompany.com.