Searched refs:bblock (Results 1 – 12 of 12) sorted by relevance
3 Locking and Unlocking Recipes Using ``bblock``19 To prevent this, use ``bblock`` to lock specific tasks or recipes to24 Use ``bblock`` only during the development phase.37 $ bblock recipe41 $ bblock recipe1 recipe247 $ bblock -t task1,task2 recipe55 $ bblock -r recipe59 $ bblock -r recipe1 recipe265 $ bblock -r -t task1,task2 recipe69 $ bblock -r[all …]
52 bblock
458 bblock = os.path.join(builddir, 'bitbake.lock')461 if not os.path.exists(bblock):465 if 10 < os.stat(bblock).st_size:470 … raise BuildSetupException("Cannot find bitbake server lock file '%s'. Exiting." % bblock)472 with open(bblock) as fplock:480 … raise BuildSetupException("localhostbecontroller: can't read bitbake port from %s" % bblock)
338 .. _structure-build-conf-bblock.conf:340 ``build/conf/bblock.conf``343 This configuration file is generated by :doc:`bblock </dev-manual/bblock>` and344 contains the signatures locked by ``bblock``. By default, it does not exist345 and will be created upon the first invocation of ``bblock``.
8516 Alternatively, you can also use :doc:`bblock </dev-manual/bblock>` to
45 - dev-manual: add bblock documentation46 - dev-manual: bblock: use warning block instead of attention
44 - dev-manual: bblock: use warning block instead of attention
36 - dev-manual: add bblock documentation
203 - New documentation on ``bblock``: :doc:`/dev-manual/bblock`.
230 - ``scripts/bblock`` was added, allowing the user to lock/unlock specific
925 int bblock = ((struct yaffs_block_index *)b)->block; in yaffs2_ybicmp() local928 return ablock - bblock; in yaffs2_ybicmp()
835 include conf/bblock.conf