I just fixed this issue.
In addition, warning messages for gtk-doc was added to autogen.sh.
I also add a configuration summary to configure.ac.
So after running configure, you can clearly see which features are enabled.
Cheers!

On Thu, Aug 11, 2011 at 2:34 AM, Martin Bagge / brother <[email protected]>wrote:

> A HUGE thanks to everyone who helped triage the documentation bug that
> surfaced in libfm.
> Who would have guessed that an documentation issue was the real reason
> (it needs --enable-gtk-doc for configure when doing make dist...).
>
> Anyhow. This pretty much means that we should do another release of
> libfm.
>
> And just a side note.
> In configure.ac the following line is present:
> AC_INIT([libfm], [0.1.16], [http://libfm.sf.net/])
>
> libfm.sf.net does not exist. is this good?
>
> --
> /brother
> http://martin.bagge.nu
> The nuclear launch codes held by the President of the United States are
> secured by an unbreakable system: a plain brown envelope with a picture of
> Bruce Schneier on the flap.
>
>
> ------------------------------------------------------------------------------
> uberSVN's rich system and user administration capabilities and model
> configuration take the hassle out of deploying and managing Subversion and
> the tools developers use with it. Learn more about uberSVN and get a free
> download at:  http://p.sf.net/sfu/wandisco-dev2dev
> _______________________________________________
> Pcmanfm-develop mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pcmanfm-develop
>
------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 
user administration capabilities and model configuration. Take 
the hassle out of deploying and managing Subversion and the 
tools developers use with it. 
http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Pcmanfm-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pcmanfm-develop

Reply via email to