> >>    In that doc it could link to the local and/or website docs,
> >>    eg:
> >>
> >>            FLTK Docs:<A 
> HREF="file://path/to/localdocs/html/index.html">(local)</A>
> > 
> > The above would be an autoconfigured path, or optional an expanded
> > environment variable?
> 
>       Good question, I'm not sure.
> 
>       Since this could tie into the build system, which I know little
>       about, I'll just write the HTML, and leave this detail to one
>       of our build system experts ;)

Though note that (as Brian pointed out recently) the auto-generated path
that configure creates for the Msys/mingw case does not actually work in
practice, since the Msys runtime "fakes up" some of the paths to make
things look a bit more *nix-like for configure, but then these fake
paths get baked into the fluid and help_view exe's and don't actually
work there...

Brian has a patch for configure that, in the Msys/mingw case only,
tweaks the path that gets baked into fluid and the help demo so that it
works, though the patch is more of a workaround than an outright fix. It
might still be better than what we have, though.

The environment variable approach is good - in fluid (as built by
Msys/mingw) the environment variable "FLTK_DOCDIR" does work to get
things going if you set it (I generally do).
Rumour has it that this also works for versions of fluid built with the
MS tools too, though I have not tried this myself.


SELEX Galileo 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.
********************************************************************

_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to