aboutsummaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-support/libftdi
AgeCommit message (Collapse)Author
2015-02-27libftdi: remove libtool-m4.patch, leftover from 0.19 -> 1.1 updateAndre McCurdy
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-12-31libftdi: Fix license format QA errorOtavio Salvador
Fix following QA error: ,---- | WARNING: Recipe libftdi, LICENSE (LGPLv2.1 GPLv2) has invalid format, | LICENSES must have operator "([&|() ])" between them. `---- Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-12-10libftdi: update to 1.1Raphael Silva
Previous version was 0.19 but it had a failing recipe due to the fact that libusb was not detect during do_configure. This problem does not happen in version 1.1. Signed-off-by: Mario Goulart <mario.goulart@gmail.com> Signed-off-by: Raphael Silva <rapphil@gmail.com> Acked-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-06-21libftdi, soft66: Blacklist, because of libftdi is broken without libusb-configMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-07-30libftdi: add PACKAGECONFIG for cpp-wrapperMartin Jansa
* also fixes WARNING: QA Issue: libftdi: The compile log indicates that host include and/or library paths were used. Please check the log '/OE/oe-core/tmp-eglibc/work/x86_64-oe-linux/libftdi/0.19-r1/temp/log.do_compile' for more information. 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>
2012-10-10libftid: Change to use GPLv2 intead of GPLv2-RLE.Martin Ertsaas
libftdi itself is licensed under LGPLv2, with some parts (eeprom programmer) is licensed under GPLv2. There doesn't seem to be any part licensed under a GPLv2-RLE variation of GPLv2, and so we should use GPLv2 instead of GPLv2-RLE. Signed-off-by: Martin Ertsaas <mertsas@cisco.com> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
2011-10-24libftdi: import 0.18 from OE classic, update to 0.19Koen Kooi
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>