On 3/20/06, Renato <[EMAIL PROTECTED]> wrote:
For now, we considered that we should keep the documentation coherence high, and that's why we tried to make writing access to the wiki something one gains rather that something everyone have. However, we'd be glad to hear about the potential benefits this would bring to our documentation.
Apart
from using the debug=explain scons' command line switch or print
statements, i don't know of a way to extensively debug scons. First, it seems the dev.openwengo.com Wiki is not very wikiish - wouldn't it be
helpful to have a true wiki where people tinkering with the code could post
their successes and failures? Of course, with the steps included..
For now, we considered that we should keep the documentation coherence high, and that's why we tried to make writing access to the wiki something one gains rather that something everyone have. However, we'd be glad to hear about the potential benefits this would bring to our documentation.
I really fail to understand how to define the variables so that SCons finds the
files. Indeed, that's the last thing I would like to ask for: could anyone
sketch a way to test and debug the build environment?
Regards,
--
Julien Gilli
_______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
