DOCSLIB.ORG

Conan Documentation Release 1.7.4

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Conan Documentation Release 1.7.4 conan Documentation Release 1.7.4 conan Sep 24, 2021 CONTENTS 1 Introduction 3 1.1 Open Source...............................................3 1.2 Decentralized package manager.....................................3 1.3 Binary management...........................................4 1.4 Cross platform, build system agnostic..................................4 1.5 Stable...................................................5 2 Install 7 2.1 Install with pip (recommended).....................................7 2.2 Install from brew (OSX).........................................8 2.3 Install from AUR (Arch Linux).....................................8 2.4 Install the binaries............................................8 2.5 Initial configuration...........................................8 2.6 Install from source............................................9 2.7 Python 2 Deprecation Notice.......................................9 3 Getting Started 11 3.1 A Timer Using POCO Libraries..................................... 11 3.2 Installing Dependencies......................................... 12 3.3 Building the Timer Example....................................... 14 3.4 Inspecting Dependencies......................................... 14 3.5 Searching Packages........................................... 15 3.6 Building with Other Configurations................................... 15 4 Using packages 17 4.1 Installing dependencies......................................... 17 4.2 Using profiles............................................... 21 4.3 Workflows................................................ 23 5 Creating Packages 27 5.1 Getting Started.............................................. 27 5.2 Recipe and Sources in a Different Repo................................. 31 5.3 Recipe and Sources in the Same Repo.................................. 32 5.4 Packaging Existing Binaries....................................... 34 5.5 Understanding Packaging........................................ 36 5.6 Defining Package ABI Compatibility.................................. 38 5.7 Inspecting Packages........................................... 45 5.8 Packaging Approaches.......................................... 45 5.9 Package Creator Tools.......................................... 50 6 Uploading Packages 53 i 6.1 Remotes................................................. 53 6.2 Uploading Packages to Remotes..................................... 54 6.3 Using Bintray............................................... 55 6.4 Artifactory Community Edition for C/C++............................... 60 6.5 Running conan_server.......................................... 61 7 Developing Packages 67 7.1 Package development flow........................................ 67 7.2 Workspaces [experimental]....................................... 71 8 Package apps and devtools 75 8.1 Running and deploying packages.................................... 75 8.2 Creating conan packages to install dev tools............................... 78 8.3 Build requirements............................................ 81 9 Mastering conan 87 9.1 Python requires: reusing python code in recipes............................. 87 9.2 Use conanfile.py for consumers..................................... 89 9.3 Conditional settings, options and requirements............................. 91 9.4 Version ranges.............................................. 93 9.5 Build policies............................................... 94 9.6 Environment variables.......................................... 95 9.7 Virtual Environments........................................... 96 9.8 Logging.................................................. 98 9.9 Sharing the settings and other configuration............................... 100 9.10 Conan local cache: concurrency, Continuous Integration, isolation................... 100 10 Systems and cross building 103 10.1 Cross building.............................................. 103 10.2 Windows Subsystems.......................................... 111 11 Integrations 115 11.1 CMake.................................................. 115 11.2 Autotools: configure/make........................................ 124 11.3 Visual Studio............................................... 124 11.4 Apple/Xcode............................................... 127 11.5 Compilers on command line....................................... 129 11.6 Android Studio.............................................. 131 11.7 CLion................................................... 136 11.8 Ninja, NMake, Borland......................................... 141 11.9 pkg-config and .pc files....................................... 141 11.10 Boost Build................................................ 145 11.11 QMake.................................................. 145 11.12 Premake................................................. 146 11.13 qbs.................................................... 147 11.14 Meson Build............................................... 148 11.15 Docker.................................................. 148 11.16 Git.................................................... 148 11.17 Jenkins.................................................. 149 11.18 Travis Ci................................................. 151 11.19 Appveyor................................................. 153 11.20 Gitlab................................................... 155 11.21 Circle CI................................................. 156 11.22 YouCompleteMe (vim).......................................... 158 11.23 SCons................................................... 158 ii 11.24 Custom integrations........................................... 159 11.25 Linting conanfile.py........................................... 163 12 Howtos 165 12.1 How to package header-only libraries.................................. 165 12.2 How to launch conan install from cmake................................ 167 12.3 How to create and reuse packages based on Visual Studio....................... 168 12.4 Creating and reusing packages based on Makefiles........................... 171 12.5 How to manage the GCC >= 5 ABI................................... 173 12.6 Using Visual Studio 2017 - CMake integration............................. 174 12.7 How to manage C++ standard...................................... 177 12.8 How to use docker to create and cross build C and C++ conan packages................ 178 12.9 How to reuse Python code in recipes................................... 181 12.10 How to create and share a custom generator with generator packages................. 184 12.11 How to manage shared libraries..................................... 188 12.12 How to reuse cmake install for package() method............................ 193 12.13 How to collaborate on other users’ packages.............................. 193 12.14 How to link with Apple Frameworks.................................. 194 12.15 How to package Apple Frameworks................................... 195 12.16 How to collect licenses of dependencies................................. 195 12.17 How to capture package version from SCM: git............................. 196 12.18 How to capture package version from text or build files......................... 196 12.19 How to use Conan as other language package manager......................... 197 12.20 How to manage SSL (TLS) certificates................................. 202 12.21 How to check the version of the Conan client inside a conanfile.................... 203 12.22 Use a generic CI with Conan and Artifactory.............................. 204 13 Reference 205 13.1 Commands................................................ 205 13.2 conanfile.txt............................................... 248 13.3 conanfile.py............................................... 250 13.4 Generators................................................ 278 13.5 Profiles.................................................. 295 13.6 Build helpers............................................... 299 13.7 Tools................................................... 315 13.8 Configuration files............................................ 336 13.9 Environment variables.......................................... 341 14 Videos and links 349 15 FAQ 351 15.1 Upgrading to conan 1.0......................................... 351 15.2 General.................................................. 353 15.3 Using conan............................................... 354 15.4 Troubleshooting............................................. 356 16 Changelog 359 16.1 1.7.4 (18-September-2018)........................................ 359 16.2 1.7.3 (6-September-2018)........................................ 359 16.3 1.7.2 (4-September-2018)........................................ 359 16.4 1.7.1 (31-August-2018)......................................... 359 16.5 1.7.0 (29-August-2018)......................................... 359 16.6 1.6.1 (27-July-2018)........................................... 360 16.7 1.6.0 (19-July-2018)........................................... 361 16.8 1.5.2 (5-July-2018)............................................ 362 iii 16.9 1.5.1 (29-June-2018)........................................... 362 16.10 1.5.0 (27-June-2018)........................................... 362 16.11 1.4.5 (22-June-2018)........................................... 363 16.12 1.4.4 (11-June-2018)........................................... 363 16.13 1.4.3 (6-June-2018)........................................... 363 16.14 1.4.2 (4-June-2018)..........................................
Load more

Recommended publications
  • Creating Rpms Guide
    CREATING RPMS (Student version) v1.0 Featuring 36 pages of lecture and a 48 page lab exercise This docu m e n t serves two purpose s: 1. Representative sample to allow evaluation of our courseware manuals 2. Make available high quality RPM documentation to Linux administrators A bout this m aterial : The blue background you see simulates the custom paper that all Guru Labs course w are is printed on. This student version does not contain the instructor notes and teaching tips present in the instructor version. For more information on all the features of our unique layout, see: http://ww w . g urulabs.co m /courseware/course w are_layout.php For more freely available Guru Labs content (and the latest version of this file), see: http://www.gurulabs.co m/goodies/ This sample validated on: Red Hat Enterprise Linux 4 & Fedora Core v3 SUSE Linux Enterprise Server 9 & SUSE Linux Professional 9.2 About Guru Labs: Guru Labs is a Linux training company started in 199 9 by Linux experts to produce the best Linux training and course w are available. For a complete list, visit our website at: http://www.gurulabs.co m/ This work is copyrighted Guru Labs, L.C. 2005 and is licensed under the Creative Common s Attribution- NonCom mer cial- NoDerivs License. To view a copy of this license, visit http://creativecom m o n s.org/licenses/by- nc- nd/2.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 943 0 5, USA. Guru Labs 801 N 500 W Ste 202 Bountiful, UT 84010 Ph: 801-298-5227 WWW.GURULABS.COM Objectives: • Understand
    [Show full text]
  • CERN R&D on Spack and the Turnkey Stack
    CERN R&D on Spack and the Turnkey Stack HSF Software Workshop - 2020/11/19 Valentin Volkl (CERN), Key4hep Software Group Thanks to Andre Sailer, Pere Mato, Ben Morgan for use of Slides Valentin Volkl: Key4HEP & Spack Table of Contents ● Key4HEP - Introduction and motivation ● The Spack package manager ● Technical considerations ● Deployment to CVMFS ● Workflow -Spack for Development Valentin Volkl: Key4HEP & Spack 2 Dependency Graph of Key4HEP Stack Experiment-specific Packages Valentin Volkl: Key4HEP & Spack 3 Dependency Graph of Key4HEP stack Experiment-specific Packages + HEP-specific packages Valentin Volkl: Key4HEP & Spack 4 Dependency Graph of Key4HEP stack Experiment-specific Packages + HEP-specific Packages + General Purpose Libraries Valentin Volkl: Key4HEP & Spack 5 Requirements for a Build System [ ] Need to be able to scale to a typical experiment software stack [ ] Combinatorics of multiple platforms, versions, Release/Debug ... [ ] Easy deployment to CVMFS [ ] Allow local builds independent of central CVMFS installations [ ] Support software development usecases The KEY4HEP stack contains some 300 packages ● 60 Experiment-specific ● 50 HEP-specific ● 200 System/General Purpose 14 GB install size, some 6h to build on single 4-core machine Valentin Volkl: Key4HEP & Spack 6 Key4HEP ● Future detector studies critically rely on well-maintained software stacks to model detector concepts and to understand a detector’s limitations and physics reach ● We have a scattered landscape of specific software tools on the one hand and integrated
    [Show full text]
  • Building Embedded Linux Systems ,Roadmap.18084 Page Ii Wednesday, August 6, 2008 9:05 AM
    Building Embedded Linux Systems ,roadmap.18084 Page ii Wednesday, August 6, 2008 9:05 AM Other Linux resources from O’Reilly Related titles Designing Embedded Programming Embedded Hardware Systems Linux Device Drivers Running Linux Linux in a Nutshell Understanding the Linux Linux Network Adminis- Kernel trator’s Guide Linux Books linux.oreilly.com is a complete catalog of O’Reilly’s books on Resource Center Linux and Unix and related technologies, including sample chapters and code examples. ONLamp.com is the premier site for the open source web plat- form: Linux, Apache, MySQL, and either Perl, Python, or PHP. Conferences O’Reilly brings diverse innovators together to nurture the ideas that spark revolutionary industries. We specialize in document- ing the latest tools and systems, translating the innovator’s knowledge into useful skills for those in the trenches. Visit con- ferences.oreilly.com for our upcoming events. Safari Bookshelf (safari.oreilly.com) is the premier online refer- ence library for programmers and IT professionals. Conduct searches across more than 1,000 books. Subscribers can zero in on answers to time-critical questions in a matter of seconds. Read the books on your Bookshelf from cover to cover or sim- ply flip to the page you need. Try it today for free. main.title Page iii Monday, May 19, 2008 11:21 AM SECOND EDITION Building Embedded Linux SystemsTomcat ™ The Definitive Guide Karim Yaghmour, JonJason Masters, Brittain Gilad and Ben-Yossef, Ian F. Darwin and Philippe Gerum Beijing • Cambridge • Farnham • Köln • Sebastopol • Taipei • Tokyo Building Embedded Linux Systems, Second Edition by Karim Yaghmour, Jon Masters, Gilad Ben-Yossef, and Philippe Gerum Copyright © 2008 Karim Yaghmour and Jon Masters.
    [Show full text]
  • Robust Linux Binaries.Pdf
    Robust Linux Binaries How to use Portage to provide a solid base stack for HEP G. Amadio https://xkcd.com/1987 Why do we fall into this kind of situation? ● We want software that’s not part of the system ● Use pip, conda, homebrew, etc to get it somewhere ● Not compiled with same compiler → incompatible ABI ● Often requires setting LD_LIBRARY_PATH and/or PYTHONPATH ● Problems if a package is both in the system and in add-ons ● Updates to the system do not take add-ons into account 3 Classic example: ROOT, Python, and Anaconda ● User has Anaconda installation with Python, wants ROOT ● User then tries to build ROOT with system compiler and link with Python from Anaconda installation ● libPyROOT.so has to link against system’s libstdc++.so and anaconda’s libpython2.7.so ● Problem: libpython2.7.so from Anaconda is not guaranteed to be ABI-compatible with system libraries ● Solution: install GCC from anaconda that was used to build Python and build ROOT with that compiler instead 4 Why LD_LIBRARY_PATH should be avoided ● LD_LIBRARY_PATH is commonly used to add directories to the linker’s search path ● Problem: LD_LIBRARY_PATH takes precedence, overrides important system libraries ○ See e.g. https://sft.its.cern.ch/jira/browse/SPI-1083 ● Solution: use a wrapper script or even better, don’t use LD_LIBRARY_PATH $ ssh lxplus7 $ lsb_release -d Description: CentOS Linux release 7.5.1804 (Core) $ source /cvmfs/sft.cern.ch/lcg/views/LCG_latest/x86_64-centos7-gcc7-opt/setup.sh $ ldd /usr/bin/git linux-vdso.so.1 => (0x00007ffdb55b3000) libpcre.so.1
    [Show full text]
  • ^`Nrfpfqflk=Oةًة~يإ = Pىهمًهيةا=Oةىهيٍ=ًةيفةً=
    UCI-AM-12-195 ^`nrfpfqflk=oÉëÉ~êÅÜ= péçåëçêÉÇ=oÉéçêí=ëÉêáÉë= Investigating Advances in the Acquisition of Secure Systems Based on Open Architectures 30 August 2012 A Compilation of Reports by Thomas A. Alspaugh, Project Scientist Walt Scacchi, Senior Research Scientist Institute for Software Research University of California, Irvine With contributions from Craig Brown, Programmer/Analyst Kari Nies, Programmer/Analyst Institute for Software Research University of California, Irvine Rihoko (Inoue) Kawai, Associate Professor, Saitama Institute of Technology Hazeline U. Asuncion, Assistant Professor Computing and Software Systems University of Washington, Bothell Approved for public release, distribution is unlimited. Prepared for: Naval Postgraduate School, Monterey, California 93943 = ^Åèìáëáíáçå=oÉëÉ~êÅÜ=mêçÖê~ã= do^ar^qb=p`elli=lc=_rpfkbpp=C=mr_if`=mlif`v= =============k^s^i=mlpqdo^ar^qb=p`elli= The research presented in this report was supported by the Acquisition Research Program of the Graduate School of Business & Public Policy at the Naval Postgraduate School. To request defense acquisition research, to become a research sponsor, or to print additional copies of reports, please contact any of the staff listed on the Acquisition Research Program website (www.acquisitionresearch.net). = ^Åèìáëáíáçå=oÉëÉ~êÅÜ=mêçÖê~ã= do^ar^qb=p`elli=lc=_rpfkbpp=C=mr_if`=mlif`v= =============k^s^i=mlpqdo^ar^qb=p`elli= About the Authors Thomas A. Alspaugh is a project scientist at the Institute for Software Research, University of California, Irvine. His research interests are in software engineering, requirements, and licensing. Before completing his PhD, he worked as a software developer, team lead, and manager in industry, and as a computer scientist at the Naval Research Laboratory on the Software Cost Reduction, or A‐7 project.
    [Show full text]
  • NVIDIA CUDA Installation Guide for Linux
    NVIDIA CUDA Installation Guide for Linux Installation and Verification on Linux Systems DU-05347-001_v11.4 | September 2021 Table of Contents Chapter 1. Introduction........................................................................................................ 1 1.1. System Requirements...............................................................................................................1 1.2. About This Document............................................................................................................... 3 Chapter 2. Pre-installation Actions..................................................................................... 4 2.1. Verify You Have a CUDA-Capable GPU....................................................................................4 2.2. Verify You Have a Supported Version of Linux........................................................................ 5 2.3. Verify the System Has gcc Installed........................................................................................5 2.4. Verify the System has the Correct Kernel Headers and Development Packages Installed........................................................................................................................................5 2.5. Install MLNX_OFED.................................................................................................................. 7 2.6. Choose an Installation Method................................................................................................ 7 2.7. Download
    [Show full text]
  • Openscenegraph 3.0 Beginner's Guide
    OpenSceneGraph 3.0 Beginner's Guide Create high-performance virtual reality applications with OpenSceneGraph, one of the best 3D graphics engines Rui Wang Xuelei Qian BIRMINGHAM - MUMBAI OpenSceneGraph 3.0 Beginner's Guide Copyright © 2010 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the authors, nor Packt Publishing and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: December 2010 Production Reference: 1081210 Published by Packt Publishing Ltd. 32 Lincoln Road Olton Birmingham, B27 6PA, UK. ISBN 978-1-849512-82-4 www.packtpub.com Cover Image by Ed Maclean ([email protected]) Credits Authors Editorial Team Leader Rui Wang Akshara Aware Xuelei Qian Project Team Leader Reviewers Lata Basantani Jean-Sébastien Guay Project Coordinator Cedric Pinson
    [Show full text]
  • The Spack Package Manager: Bringing Order to HPC Software Chaos
    The Spack Package Manager: Bringing Order to HPC Software Chaos Todd Gamblin Matthew LeGendre Michael R. Collette Gregory L. Lee [email protected] [email protected] [email protected] [email protected] Adam Moody Bronis R. de Supinski Scott Futral [email protected] [email protected] [email protected] Lawrence Livermore National Laboratory ABSTRACT Worse, the space of required builds grows combinatorially with Large HPC centers spend considerable time supporting software for each new configuration parameter. As a result, LLNL staff spend thousands of users, but the complexity of HPC software is quickly countless hours dealing with build and deployment issues. outpacing the capabilities of existing software management tools. Existing package management tools automate parts of the build Scientific applications require specific versions of compilers, MPI, process [2, 10, 11, 12, 23, 24, 38, 39, 41]. For the most part, they and other dependency libraries, so using a single, standard software focus on keeping a single, stable set of packages up to date, and stack is infeasible. However, managing many configurations is they do not handle installation of multiple versions or configurations. difficult because the configuration space is combinatorial in size. Those that do handle multiple configurations typically require that We introduce Spack, a tool used at Lawrence Livermore National package files be created for each combination of options [10, 11, Laboratory to manage this complexity. Spack provides a novel, re- 12, 23], leading to a profusion of files and maintenance issues. cursive specification syntax to invoke parametric builds of packages Some allow limited forms of composition [11, 12, 23], but their and dependencies.
    [Show full text]
  • Cernvm – a Virtual Software Appliance for LHC Applications
    17th International Conference on Computing in High Energy and Nuclear Physics (CHEP09) IOP Publishing Journal of Physics: Conference Series 219 (2010) 042003 doi:10.1088/1742-6596/219/4/042003 CernVM – a virtual software appliance for LHC applications P Buncic1, C Aguado Sanchez1, J Blomer1, L Franco1, A Harutyunian2,3, P Mato1, Y Yao3 1 CERN, 1211 Geneve 23, Geneva, Switzerland 2Armenian e-Science Foundation, Yerevan, Armenia 3Yerevan Physics Institute after A.I. Alikhanyan, Yerevan, Armenia 4 Lawrence Berkeley National Laboratory, 1 Cyclotron Road, CA 94720 Abstract. CernVM is a Virtual Software Appliance capable of running physics applications from the LHC experiments at CERN. It aims to provide a complete and portable environment for developing and running LHC data analysis on any end-user computer (laptop, desktop) as well as on the Grid, independently of Operating System platforms (Linux, Windows, MacOS). The experiment application software and its specific dependencies are built independently from CernVM and delivered to the appliance just in time by means of a CernVM File System (CVMFS) specifically designed for efficient software distribution. The procedures for building, installing and validating software releases remains under the control and responsibility of each user community. We provide a mechanism to publish pre-built and configured experiment software releases to a central distribution point from where it finds its way to the running CernVM instances via the hierarchy of proxy servers or content delivery networks. In this paper, we present current state of CernVM project and compare performance of CVMFS to performance of traditional network file system like AFS and discuss possible scenarios that could further improve its performance and scalability.
    [Show full text]
  • Symantec™ Data Loss Prevention Third-Party License Agreements
    Symantec™ Data Loss Prevention Third-Party License Agreements Version 15.1 Symantec Data Loss Prevention Third-Party License Agreements Documentation version: 15.1 Legal Notice Copyright © 2018 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo and the Checkmark Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party (“Third Party Programs”). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information on the Third Party Programs. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION.
    [Show full text]
  • Crossmark Content Copyright Information
    CrossMark Content Copyright Information In addition to BAPCo produced content and source code, BAPCo CrossMark uses licensed libraries listed below in the benchmark programs. OpenCV, Opencv Contrib By downloading, copying, installing or using the software you agree to this license. If you do not agree to this license, do not download, install,copy or use the software. License Agreement For Open Source Computer Vision Library (3-clause BSD License) Copyright (C) 2000-2019, Intel Corporation, all rights reserved. Copyright (C) 2009-2011, Willow Garage Inc., all rights reserved. Copyright (C) 2009-2016, NVIDIA Corporation, all rights reserved. Copyright (C) 2010-2013, Advanced Micro Devices, Inc., all rights reserved. Copyright (C) 2015-2016, OpenCV Foundation, all rights reserved. Copyright (C) 2015-2016, Itseez Inc., all rights reserved. Third party copyrights are property of their respective owners. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the names of the copyright holders nor the names of the contributors may be used to endorse or promote products derived from this software without specific prior written permission. This software is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed.
    [Show full text]
  • Open Source Software License
    Open Source Software License Contents Open Source Software License.................................................................................................................. 5 Copyright Attribution ................................................................................................................................ 83 3 Open Source Software License GNU GPL This projector product includes the open source software programs which apply the GNU General Public License Version 2 (June 1991) ("GPL Programs"). We provide the source code of the GPL Programs until five (5) years after the discontinuation of same model of this projector product. If you desire to receive the source code of the GPL Programs, contact Epson. These GPL Programs are WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. The list of GPL Programs is as follows and the names of author are described in the source code of the GPL Programs The list of GPL Programs • busybox-1.21.0 • iptables-1.4.21 • linaro-lsk-v4.4 • patches • kernel driver • udhcp 0.9.8 • wireless_tools 29 • dibbler-1.0.1 • backports v4.14-rc2 • Cypress Wi-Fi Linux FMAC Driver • e2fsprogs 1.44.4 • busybox V1.4 • ION Driver • libaio • OpenMAX 5 • U-Boot V2017.11 • eudev The GNU General Public License Version 2 is as follows. You also can see the GNU General Public License Version 2 at http://www.gnu.org/licenses/. GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
    [Show full text]