Is there a good reason not to include pre-built html files in release tarballs? It's not like there's anything system specific that happens with them, and then end users wouldn't have to worry about doxygen, but would still get the help files. I don't see much benefit to distributing only the uncompiled documentation files.
-Stephen On Jun 8, 2012, at 6:25 AM, Stestagg wrote: > running ./configure ... --without-doxygen worked for me, > > Thanks > > Steve > > On Fri, Jun 8, 2012 at 12:37 AM, Patrick > <[email protected]>wrote: > >> I was surprised at the size of the doxygen dependency, about 500M. Is >> this mandatory? I am day dreaming about using fish in an embedded >> design. I was thinking that the multiline support and coloured syntax >> might be very nice for a front panel control. With the sensible syntax, >> users could even create their own function to control the instrument I >> am thinking of building. >> >> Any feedback would be appreciated-Patrick ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
