2011/3/11 Greg Troxel <g...@ir.bbn.com>:
> If this is for building docs about the source code, a la doxygen, then
> it would be nice if it's possible to easily build viking without this
> documentation, while simultaneously allowing those who are hacking on it
> to have the docs.  Is that what you think you did?

Yes, it is what I tried to do.
To ensure this, I put the Makefile in a subdirectory not linked by
other Makefile. So, the "make" must be manually activated on this
But I'm not really sure abou one aspect: dependencies. Is this change
brings some new dependencies?

I whish to build something easy for packager and user: no more
dependencies, nor time spent on building a internal/reference

-=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com
-=- mailto:guilhem.bonnefi...@gmail.com
-=- http://nathguil.free.fr/

Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
Viking-devel mailing list
Viking home page: http://viking.sf.net/

Reply via email to