aboutsummaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-extended/liblockfile/liblockfile_1.09.bb
AgeCommit message (Collapse)Author
2015-07-30liblockfile: add patch of version 1.09-6 from debianKang Kai
Add patch of liblockfile 1.09-6 from debian. And fix error which install so file to manual directory. Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-05-21liblockfile: remove unrecognized configure optionChen Qi
The '--enable-static' is an unrecognized configure option, thus removing it. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-05-21liblockfile: inherit autotools-brokensepChen Qi
Seperation of ${B} and ${S} causes a build failure for liblockfile. The error message is as follows. make: *** No rule to make target `lockfile.c', needed by `lockfile.o'. Stop. Make liblockfile inherit autotools-brokensep to fix this problem. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-04-20liblockfile: set default mailgroup and install libnfslockJackie Huang
* Set the default mailgroup to 'mail' or it will use 'root'. * Set --with-libnfslock so it builds and install libnfslock. * The patch is to fix nfslib build failure and add missing soname lib. * No need to override the do_install, set EXTRA_OEMAKE instead. Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-02-23recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issuesMatthieu CRAPET
Changes: - rename SUMMARY with length > 80 to DESCRIPTION - rename DESCRIPTION with length < 80 to (non present tag) SUMMARY - drop final point character at the end of SUMMARY string - remove trailing whitespace of SUMMARY line Note: don't bump PR Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-04-15recipes: Unify indentationMartin Jansa
* This change is only aesthetic (unlike indentation in Python tasks). * Some recipes were using tabs. * Some were using 8 spaces. * Some were using mix or different number of spaces. * Make them consistently use 4 spaces everywhere. * Yocto styleguide advises to use tabs (but the only reason to keep tabs is the need to update a lot of recipes). Lately this advice was also merged into the styleguide on the OE wiki. * Using 4 spaces in both types of tasks is better because it's less error prone when someone is not sure if e.g. do_generate_toolchain_file() is Python or shell task and also allows to highlight every tab used in .bb, .inc, .bbappend, .bbclass as potentially bad (shouldn't be used for indenting of multiline variable assignments and cannot be used for Python tasks). * Don't indent closing quote on multiline variables we're quite inconsistent wheater it's first character on line under opening quote or under first non-whitespace character in previous line. Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Acked-by: Koen Kooi <koen@dominion.thruhere.net>
2013-01-08liblockfile: Upgrade 1.06 -> 1.09Khem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com>