On 10/07/2011 07:09 AM, Richard Purdie wrote:
I've been trying to figure out why our builds take as long as they do.
It appears our dependency chains are getting more and more convoluted
and this certainly isn't helping things. Specific pain points look like:
bison-native -> gettext-native
flex-native -> gettext-native
(which limits binutils-cross)
gettext-native -> libxml2-native -> python-native
(hence gettext takes a *long* time to be built)
What uses the python xml bindings?
I thought that by having the --with-included-libxml, we got rid of the
libxml2-native dependency, we should investigate that further.
Digging shows that it is needed for python to create the xml2po tool for
doc translation.
Sau!
pseudo-native -> sqlite3-native
(dragging out the time our effectively single threaded init takes)
I'm mentioning this in case anyone has good ideas for fixing some of
these...
Cheers,
Richard
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
