Search results

From Yocto Project
Jump to navigationJump to search
  • ...ach separate parsing thread, saving the data to files called profile-parse-Parser-1:X.log where X is the thread number. It then merges all the files together ...ows which functions called those functions. This is useful where you see a function called many times and want to know where it was called from.
    2 KB (289 words) - 13:03, 27 June 2016
  • ...twice, firstly sorted by internal function time and secondly be cumulative function time. ...t speedups in the parser were in places where there were insane numbers of function calls, often in tight loops. By improving the algorithms, the same work cou
    9 KB (1,421 words) - 09:34, 6 December 2012
  • utils: don't overwrite builtin dir() function Split out 'find next buildable task' into a separate generator function
    133 KB (17,262 words) - 16:30, 5 April 2011
  • | Add Directfb (license LGPL) function||Test the exist Directfb, qt-embedded, webkit(may have error from upstream' | License tracking||Build a parser to do license tracking more gracefully and make sure all recipes are correc
    36 KB (5,605 words) - 00:38, 5 May 2011
  • ...as identified during bitbake parsing where memory usage would grow in each parser thread linearly per number of recipes parsed. This would therefore particul ...s can be quickly hacked and used for standalone debugging by replacing the function call at the end with “bash -i” which will then drop you into a shell en
    144 KB (22,009 words) - 15:47, 15 December 2020
  • ...queue (add Tom's patchset, fix bashism in imag_cmd_tar, use hardlink tree function, change autoconf patch) ***ERROR: kconfig-frontends-4.10.0.1-r0 do_compile: Function failed: bug filed: https://bugzilla.yoctoproject.org/show_bug.cgi?id=11574
    1.99 MB (246,245 words) - 09:11, 9 October 2017