DOCSLIB.ORG

Building C/C++ Libraries with Perl

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Building C/C++ Libraries with Perl Building C and C++ Libraries with Perl Building C/C++ libraries with Perl Author Alberto Simões <[email protected]>. Biography: Alberto Simões I am just another Perl hacker. Programming Perl for more than a dozenyears, I use it mainly for web development and natural languageprocessing. My academic formation is in computer science, with a MSc and a PhD innatural language processing using Perl, of course. My main activity is teaching at university level. Unfortunately I amnot lucky to teach Perl. This last year I have taught Bison and Flexin a Languages Processing course, and used a pseudo-language for acourse in Artificial Intelligence for Games. I do research in natural language processing, with emphasis in thePortuguese language. This explains the amount of modules in the Lingua:: and Lingua::PT:: name-spaces. The need for speed makesme rely on C libraries which in turn causes my need for building C andC++ libraries using Perl. Finally, in the Perl Community, I am member of the YAPC EuropeFoundation board, the chair of The Perl Foundation Grants Committee,treasurer of the Portuguese Perl Programmers Association and a sporadic Dancer hacker. Abstract We all know that the popular AutoTools is evil. AutoConf ismessy, AutoMake a confusion, and the lack of an automated way tobuild this kind of projects on most Linux distributions, Mac OS X and Windows makes these applications portability poor. If together with all this, your non-Perl code (let's talk mostly of Cand C++) will be only used from within your own Perl module, it is aheadache and a shame to make available these libraries in tarballsthat somehow are not easy to install. After years of user complains, I decided to bundle some librariesinside my Perl modules. I am sorry for anyone who wants to use thelibrary from another language (I do not think there is such an user yet), but bundling the code in a Perl module that can be automaticallyinstalled by any CPAN tool is just great. And it is even greater ifthey work mostly out of the box on the three major operating systems(for Windows I need Strawberry Perl). In this article I explain how I bundle some modules that includeC or C++ libraries, like Lingua::Identify::CLD, Lingua::NATools, Lingua::Jspell or Text::BibTeX. Introduction and Motivation Before starting, I would like to make a statement: this article ismy point of view on how things are in the open source world, and how Ichoose to solve some of those issues. My solution is not unique, andnot the best, surely. Most C and C++ libraries that are available in open source projectsare shipped in tarballs with a configure script and a makefile. That is an acceptable approach, but it is not thebest. Other approaches are available, like cmake, but it didn'thave much impact (at least, yet). Most developers keep using the well known AutoTools, not because oftheir quality or even flexibility, but because everybody uses them,and the alternatives are not widespread. Also, there are lots of macros already available, and most autoconf scripts are just abunch of copy and paste blocks from another projects, with minorchanges, where maintainers just hope to work, and prayeveryday. What are these tools? They are mostly written in Perl (yes, that istrue) and they use M4 macros, a language nobody on earthunderstands and likes to use. These Perl scripts parse a definition ofa configuration file, and generate a shell script, that will try todetect how to build your application. It will detect a C compiler, abunch of libraries, the size of your integers, where the requiredlibraries are, Page 1 Building C and C++ Libraries with Perl and a lot of more useful and not so usefulvariables. So, for a user to build one of these libraries, he needs to have aPerl interpreter, autoconf, automake, libtool, m4, make, and all the software needed to really build the library,typically a C compiler (gcc, probably) and all the libraries thesoftware depends on. This tool chain is too big to be easy to maintain, and to have usersto install on non-Linux systems. Even Mac OS X that is supposed to bean Unix system has problems with these tools. I have been bitten by AutoTools a lot of times, having to givesupport to users to install a library I maintain, just because theywant to use a Perl module that uses that library. I got enough from it, and decided to go all Perl. If AutoTools arewritten in Perl, users need Perl. Then, if I go for Perl as arequirement, I am not requesting that much. Then, I will probably needsome modules that are not in the core. But those should be easy toinstall using any CPAN tool. With this in mind I decided to investsome time, and I got a tool chain of Perl modules to compile any C andC++ code that might be bundled with any of my Perl modules. In the next section I will describe each of the modules I use in mytool chain for building my modules that include C or C++ code: Lingua::Identify::CLD, Lingua::NATools, Lingua::Jspell, Text::BibTeX or Lingua::FreeLing3. Then, I will describe brieflyhow some of these modules' build systems is working (no, I will notdetail the code, you can see it on CPAN). At the end I will drawsome conclusions. Do not expect a step by step tutorial of how to write your modulebuild system. Each module is different and has its ownspecifics. Also, some code blocks might have been simplified. Modules Tool Chain In this section I describe the modules used, and for what they areused. I will not enter in detail on how to use them, or how to gluethem with each other. Module::Build Although the most used module in CPAN, unfortunately ExtUtils::MakeMaker has a big limitation: therules are expressed in a makefile, where actions are shellcommands. This makes it harder to detect what commands to run, and runthem accordingly. Regarding this, Module::Build has a big advantage. As the rules areexpressed as Perl functions there is a lot more versatility. It is easyto write a module to subclass Module::Build and rewrite some of themethods according with our needs. ExtUtils::CBuilder We are talking about building C software, whichmeans we need a C compiler. For that, Perl bundles in its core modulesthe ExtUtils::CBuilder module, that is able to detect, using the Config module, which C compiler to use and with whichflags. It also has information on how to link a library and how tolink an executable. It even guesses some C++ flags quite well. Its main drawback is that it is prepared to build Perl libraries: whatI mean with Perl libraries is, the libraries that are built with XScode and are loaded with DynaLoader. These librarieshave some differences from the standard libraries, at least on someoperating systems. For instance, in Mac OS X, the Perl libraries areknown as bundles and the standard C libraries are known as dyldlibraries (standard dynamic libraries). They have differentfunctionality (not that I am aware of the real differences, myknowledge in this aspect is just superficial). ExtUtils::ParseXS Also in the Perl core modules is ExtUtils::ParseXS. It parses XS files and generates the corresponding C (or C++) code. If you use ExtUtils::MakeMaker or Module::Build built-in mechanism for building C extensions you areusing this module by default. As I am building my extensions manuallyI need to call it myself, to create the C/C++ glue file. Page 2 Building C and C++ Libraries with Perl ExtUtils::Mkbootstrap Just like the previous module, ExtUtils::Mkbooktrap is also a Perl core module, and used by theusual build tools to compile XS code. It is used to create a file usedby DynaLoader to load dynamically your extension. Again, as I ambuilding everything by hand, it is part of my tool chain. ExtUtils::PkgConfig / PkgConfig At the moment I am using ExtUtils::PkgConfigto detect some libraries that bundle a .pc file. This mechanism wasused originally with Gnome (if I recall correctly), and now is commonon most libraries. To include a pkg-config file is easy, and can makethe life of other programmers easier. So, why not. The problem with ExtUtils::PkgConfig is that it uses the pkg-config binary file. This extra dependency is a problem. Sometime ago it was discussed that it should exist a pure Perl implementation of this module. PkgConfig seems to bethat module, but I am not using it yet. But I will probably migrate mybuild scripts to use PkgConfig in the future. Config::AutoConf With Config::AutoConf I start presenting twomodules written by me (and with a lot of patches and contributions) tohelp me with the C and C++ libraries build process. Config::AutoConf is a module to mimic some of the behavior you canget with autoconf. It has some methods to help detect if a libraryis available, if it can be linked with, if some header files are available, if some binary is available, etc. To complete some of these tasks Config::AutoConf uses ExtUtils::CBuilder to build some simple C programs and detect ifthey build and run properly. ExtUtils::LibBuilder Finally, ExtUtils::LibBuilder is probablythe most relevant module to build standalone system libraries, butalso, the module that needs more work. It is a hairy module that usesa set of heuristics to, based on the information from Config andusing ExtUtils::CBuilder, detect how to build a standalone systemlibrary. For that, it uses some magic, looks to the system type, triesto build a bunch of files, and if it succeeds, it returns the requiredflags for building the library.
Load more

Recommended publications
  • [PDF] Beginning Raku
    Beginning Raku Arne Sommer Version 1.00, 22.12.2019 Table of Contents Introduction. 1 The Little Print . 1 Reading Tips . 2 Content . 3 1. About Raku. 5 1.1. Rakudo. 5 1.2. Running Raku in the browser . 6 1.3. REPL. 6 1.4. One Liners . 8 1.5. Running Programs . 9 1.6. Error messages . 9 1.7. use v6. 10 1.8. Documentation . 10 1.9. More Information. 13 1.10. Speed . 13 2. Variables, Operators, Values and Procedures. 15 2.1. Output with say and print . 15 2.2. Variables . 15 2.3. Comments. 17 2.4. Non-destructive operators . 18 2.5. Numerical Operators . 19 2.6. Operator Precedence . 20 2.7. Values . 22 2.8. Variable Names . 24 2.9. constant. 26 2.10. Sigilless variables . 26 2.11. True and False. 27 2.12. // . 29 3. The Type System. 31 3.1. Strong Typing . 31 3.2. ^mro (Method Resolution Order) . 33 3.3. Everything is an Object . 34 3.4. Special Values . 36 3.5. :D (Defined Adverb) . 38 3.6. Type Conversion . 39 3.7. Comparison Operators . 42 4. Control Flow . 47 4.1. Blocks. 47 4.2. Ranges (A Short Introduction). 47 4.3. loop . 48 4.4. for . 49 4.5. Infinite Loops. 53 4.6. while . 53 4.7. until . 54 4.8. repeat while . 55 4.9. repeat until. 55 4.10. Loop Summary . 56 4.11. if . ..
    [Show full text]
  • Files: Cpan/Test-Harness/* Copyright: Copyright (C) 2007-2011
    Files: cpan/Test-Harness/* Copyright: Copyright (c) 2007-2011, Andy Armstrong <[email protected]>. All rights reserved. License: GPL-1+ or Artistic Comment: This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. Files: cpan/Test-Harness/lib/TAP/Parser.pm Copyright: Copyright 2006-2008 Curtis "Ovid" Poe, all rights reserved. License: GPL-1+ or Artistic Comment: This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. Files: cpan/Test-Harness/lib/TAP/Parser/YAMLish/Reader.pm Copyright: Copyright 2007-2011 Andy Armstrong. Portions copyright 2006-2008 Adam Kennedy. License: GPL-1+ or Artistic Comment: This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. Files: cpan/Test-Simple/* Copyright: Copyright 2001-2008 by Michael G Schwern <[email protected]>. License: GPL-1+ or Artistic Comment: This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. Files: cpan/Test-Simple/lib/Test/Builder.pm Copyright: Copyright 2002-2008 by chromatic <[email protected]> and Michael G Schwern E<[email protected]>. License: GPL-1+ or Artistic 801 Comment: This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. Files: cpan/Test-Simple/lib/Test/Builder/Tester/Color.pm Copyright: Copyright Mark Fowler <[email protected]> 2002. License: GPL-1+ or Artistic Comment: This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
    [Show full text]
  • Learning Perl Through Examples Part 2 L1110@BUMC 2/22/2017
    www.perl.org Learning Perl Through Examples Part 2 L1110@BUMC 2/22/2017 Yun Shen, Programmer Analyst [email protected] IS&T Research Computing Services Spring 2017 Tutorial Resource Before we start, please take a note - all the codes and www.perl.org supporting documents are accessible through: • http://rcs.bu.edu/examples/perl/tutorials/ Yun Shen, Programmer Analyst [email protected] IS&T Research Computing Services Spring 2017 Sign In Sheet We prepared sign-in sheet for each one to sign www.perl.org We do this for internal management and quality control So please SIGN IN if you haven’t done so Yun Shen, Programmer Analyst [email protected] IS&T Research Computing Services Spring 2017 Evaluation One last piece of information before we start: www.perl.org • DON’T FORGET TO GO TO: • http://rcs.bu.edu/survey/tutorial_evaluation.html Leave your feedback for this tutorial (both good and bad as long as it is honest are welcome. Thank you) Yun Shen, Programmer Analyst [email protected] IS&T Research Computing Services Spring 2017 Today’s Topic • Basics on creating your code www.perl.org • About Today’s Example • Learn Through Example 1 – fanconi_example_io.pl • Learn Through Example 2 – fanconi_example_str_process.pl • Learn Through Example 3 – fanconi_example_gene_anno.pl • Extra Examples (if time permit) Yun Shen, Programmer Analyst [email protected] IS&T Research Computing Services Spring 2017 www.perl.org Basics on creating your code How to combine specs, tools, modules and knowledge. Yun Shen, Programmer Analyst [email protected] IS&T Research Computing
    [Show full text]
  • An Introduction to Raku
    Perl6 An Introduction Perl6 Raku An Introduction The nuts and bolts ● Spec tests ○ Complete test suite for the language. ○ Anything that passes the suite is Raku. The nuts and bolts ● Spec tests ○ Complete test suite for the language. ○ Anything that passes the suite is Raku. ● Rakudo ○ Compiler, compiles Raku to be run on a number of target VM’s (92% written in Raku) The nuts and bolts ● Spec tests ○ Complete test suite for the language. ○ Anything that passes the suite is Raku. ● Rakudo ○ Compiler, compiles Raku to be run on a number of target VM’s (92% written in Raku) ● MoarVM ○ Short for "Metamodel On A Runtime" ○ Threaded, garbage collected VM optimised for Raku The nuts and bolts ● Spec tests ○ Complete test suite for the language. ○ Anything that passes the suite is Raku. ● Rakudo ○ Compiler, compiles Raku to be run on a number of target VM’s (92% written in Raku) ● MoarVM ○ Short for "Metamodel On A Runtime" ○ Threaded, garbage collected VM optimised for Raku ● JVM ○ The Java Virtual machine. The nuts and bolts ● Spec tests ○ Complete test suite for the language. ○ Anything that passes the suite is Raku. ● Rakudo ○ Compiler, compiles Raku to be run on a number of target VM’s (92% written in Raku) ● MoarVM ○ Short for "Metamodel On A Runtime" ○ Threaded, garbage collected VM optimised for Raku ● JVM ○ The Java Virtual machine. ● Rakudo JS (Experimental) ○ Compiles your Raku to a Javascript file that can run in a browser Multiple Programming Paradigms What’s your poison? Multiple Programming Paradigms What’s your poison? ● Functional
    [Show full text]
  • LAMP and the REST Architecture Step by Step Analysis of Best Practice
    LAMP and the REST Architecture Step by step analysis of best practice Santiago Gala High Sierra Technology S.L.U. Minimalistic design using a Resource Oriented Architecture What is a Software Platform (Ray Ozzie ) ...a relevant and ubiquitous common service abstraction Creates value by leveraging participants (e- cosystem) Hardware developers (for OS level platforms) Software developers Content developers Purchasers Administrators Users Platform Evolution Early stage: not “good enough” solution differentiation, innovation, value flows Later: modular architecture, commoditiza- tion, cloning no premium, just speed to market and cost driven The platform effect - ossification, followed by cloning - is how Chris- tensen-style modularity comes to exist in the software industry. What begins as a value-laden proprietary platform becomes a replaceable component over time, and the most successful of these components finally define the units of exchange that power commodity networks. ( David Stutz ) Platform Evolution (II) Example: PostScript Adobe Apple LaserWriter Aldus Pagemaker Desktop Publishing Linotype imagesetters NeWS (Display PostScript) OS X standards (XSL-FO -> PDF, Scribus, OOo) Software Architecture ...an abstraction of the runtime elements of a software system during some phase of its oper- ation. A system may be composed of many lev- els of abstraction and many phases of opera- tion, each with its own software architecture. Roy Fielding (REST) What is Architecture? Way to partition a system in components
    [Show full text]
  • Linux Lunacy V & Perl Whirl
    SPEAKERS Linux Lunacy V Nicholas Clark Scott Collins & Perl Whirl ’05 Mark Jason Dominus Andrew Dunstan Running Concurrently brian d foy Jon “maddog” Hall Southwestern Caribbean Andrew Morton OCTOBER 2ND TO 9TH, 2005 Ken Pugh Allison Randal Linux Lunacy V and Perl Whirl ’05 run concurrently. Attendees can mix and match, choosing courses from Randal Schwartz both conferences. Doc Searls Ted Ts’o Larry Wall Michael Warfield DAY PORT ARRIVE DEPART CONFERENCE SESSIONS Sunday, Oct 2 Tampa, Florida — 4:00pm 7:15pm, Bon Voyage Party Monday, Oct 3 Cruising The Caribbean — — 8:30am – 5:00pm Tuesday, Oct 4 Grand Cayman 7:00am 4:00pm 4:00pm – 7:30pm Wednesday, Oct 5 Costa Maya, Mexico 10:00am 6:00pm 6:00pm – 7:30pm Thursday, Oct 6 Cozumel, Mexico 7:00am 6:00pm 6:00pm – 7:30pm Friday, Oct 7 Belize City, Belize 7:30am 4:30pm 4:30pm – 8:00pm Saturday, Oct 8 Cruising The Caribbean — — 8:30am – 5:00pm Sunday, Oct 9 Tampa, Florida 8:00am — Perl Whirl ’05 and Linux Lunacy V Perl Whirl ’05 are running concurrently. Attendees can mix and match, choosing courses Seminars at a Glance from both conferences. You may choose any combination Regular Expression Mastery (half day) Programming with Iterators and Generators of full-, half-, or quarter-day seminars Speaker: Mark Jason Dominus Speaker: Mark Jason Dominus (half day) for a total of two-and-one-half Almost everyone has written a regex that failed Sometimes you’ll write a function that takes too (2.5) days’ worth of sessions. The to match something they wanted it to, or that long to run because it produces too much useful conference fee is $995 and includes matched something they thought it shouldn’t, and information.
    [Show full text]
  • Current Issues in Perl Programming Overview
    Current Issues In Perl Programming Lukas Thiemeier Current Issues In Perl Programming DESY, Zeuthen, 2011-04-26 Overview > Introduction > Moose – modern object-orientation in Perl > DBIx::Class – comfortable an flexible database access > Catalyst – a MVC web application framework Lukas Thiemeier | Current issues in Perl programming | 2011-04-26 | Page 2 Introduction > What is this talk about? . Modern Perl can do more than most people know . A quick overview about some modern features . Illustrated with some short examples > What is this talk not about? . Not an introduction to the Perl programming language . Not a Perl tutorial . Not a complete list of all current issues in Perl 5 . Not a complete HowTo for the covered topics Lukas Thiemeier | Current issues in Perl programming | 2011-04-26 | Page 3 Overview > Introduction > Moose – modern object-orientation in Perl . About Moose . Creating and extending classes . Some advanced features > DBIx::Class – comfortable an flexible database access > Catalyst – a MVC web application framework Lukas Thiemeier | Current issues in Perl programming | 2011-04-26 | Page 4 About Moose > “A postmodern object system for Perl 5” > Based on Class::MOP, a metaclass system for Perl 5 > Look and feel similar to the Perl 6 object syntax “The main goal of Moose is to make Perl 5 Object Oriented programming easier, more consistent and less tedious. With Moose you can to think more about what you want to do and less about the mechanics of OOP.” Lukas Thiemeier | Current issues in Perl programming | 2011-04-26 | Page 5 Creating Classes > A very simple Moose-Class: . Create a file called “MyAnimalClass.pm” with the following content: package MyAnimalClass; use Moose; no Moose; 1; Lukas Thiemeier | Current issues in Perl programming | 2011-04-26 | Page 6 Creating Classes > A very simple Moose-Class: The package name is used as class name.
    [Show full text]
  • How the Camel Is De-Cocooning (YAPCNA)
    How the Camel! is de-cocooning Elizabeth Mattijsen! YAPC::NA, 23 June 2014 The Inspiration coccoon? Perl 5 Recap: 2000 - 2010 • 2000 - Perl 5.6 • 2002 - Perl 5.8 • 2007 - Perl 5.10 • 2010 - Perl 5.12 + yearly release • The lean years have passed! Perl 6 Recap: 2000 - 2010 • Camel Herders Meeting / Request for Comments • Apocalypses, Exegeses, Synopses • Parrot as a VM for everybody • Pugs (on Haskell) / Perl 6 test-suite • Rakudo (on Parrot) / Niecza (on mono/.NET) • Nothing “Production Ready” The 0’s - Cocooning Years • Perl was busy with itself • Redefining itself • Re-inventing itself • What is Perl ? • These years have passed! Not your normal de-cocooning Perl 5 and Perl 6 will co-exist for a long time to come! Perl 5 in the 10’s • A new release every year! • Many optimisations,5.20 internalis codeout! cleanup! ! • Perl 6-like features: say, state, given/when, ~~, //, …, packageGo {}, lexical getsubs, sub signaturesit! • Perl 6-like Modules: Moose / Moo / Mouse, Method::Signatures,and Promisesuse it! • and a Monthly development release Perl 6 in the 10’s • Niecza more feature-complete, initially • Not Quite Perl (NQP) developed and stand-alone • 6model on NQP with multiple backends • MoarVM - a Virtual Machine for Perl 6 • Rakudo runs on Parrot, JVM, MoarVM • also a Monthly development release Co-existence? Yes! But Perl 6 will become larger and be more future proof! Cool Perl 6 features in Perl 5 • say • yada yada yada (…) • state variables • defined-or (//)! • lexical subs • subroutine signatures • OK as long as it doesn’t involve types print "Foo\n"; Foo ! say "Foo"; Foo print "Foo\n"; !Foo say "Foo"; Foo print "Foo\n"; Foo ! say "Foo"; Foo print "Foo\n"; Foo ! say "Foo"; Foo sub a { ..
    [Show full text]
  • Multimedia Applications for Training in Communications
    New technologies for university education PARROT VIRTUAL MACHINE AS A PEDAGOGIC TOOL C. Aperghis-Tramoni, J. Guizol Universite de la Mediterranee For about 20 years now, Perl programming language did develop itself up to the actual release which is 5. Former releases were : Perl 1 : January 1988 Perl 2 : June 1988 Perl 3 : October 1989 Perl 4 : In 992 Perl 5 : Since August 1997 Lets say first some words on how releases are numbered. Three elements have to be considered : Revision. Version. Subversion. It means that, if we consider Perl 5.6.1, Revision is 6, Version is 5 and subversion is 1. Even versions are maintenance one (5.6.x) Odd versions are versions for development (5.7.x) Before reaching 5.6.0, subversions _01 à _49 will have been reserved for debugging. Subversions _50 à _99 are considered as unstable versions. Perl contains a magical variable ($]) that contains the number of the release. This coding uses the composite scheme of numbering in floating point mode. Value is computed as : Revision + Version/1000 + Subversion/10000 Up to now, all these evolutions have never been revolutions, language did remains an interpreted one, only release 5 did propose objects as a new feature. On contrary, the last one, number 6, will bring a radical change in Perl design, it will no more be interpreted but compiled in a byte codes that will be carried out on a virtual machine, the parrot machine.. The simplicity of this machine, the power of its assembly language did decide us to use it as a support for assembly language courses.
    [Show full text]
  • Web Development with Perl
    Web Development with Perl Paul Fenwick Jacinta Richardson Kirrily Robert Web Development with Perl by Paul Fenwick, Jacinta Richardson, and Kirrily Robert Copyright © 1999-2000 Netizen Pty Ltd Copyright © 2000 Kirrily Robert Copyright © 2001 Obsidian Consulting Group Pty Ltd Copyright © 2001-2006 Perl Training Australia Pty Ltd Copyright © 2001-2006 Paul Fenwick ([email protected]) Copyright © 2001-2006 Jacinta Richardson ([email protected]) Open Publications License 1.0 This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/). Distribution of this work or derivative of this work in any standard (paper) book form is prohibited unless prior permission is obtained from the copyright holder. This document includes content from the CGI Programming with Perl training notes originally created by Kirrily Robert and Netizen Pty Ltd. All additional material written by Paul Fenwick and Jacinta Richardson. Copies of the Netizen training manuals can be found at http://sourceforge.net/projects/spork This training manual is maintained by Perl Training Australia. This is version 1.2 of Perl Training Australia’s "Web Development with Perl" training manual. Table of Contents 1. Introduction..................................................................................................................................... 1 Introduction................................................................................................................................
    [Show full text]
  • Grokking the CPAN
    Grokking the I. Genesis What is the CPAN? Comprehensive Perl Archive Network - ~2gb and 220 mirrors Began as an idea by Jared Rhine in December 1993 as a place to store all the Perl bits then scattered all over the map. “I congratulate on your effort to create a new Perl archive site. I too, have begun to create a comprehensive Perl archive. It is this about which I wish to speak. As you no doubt have noticed, there are far too many different structures of Perl archives out there and none are canonical. I propose that we cooperate to create a unified structure, much like the CTAN project which has managed to create a collection of canonical sites for TeX [...] The advantages to the Perl community would be numerous, I imagine. There would be no searching for the correct random directory to find something, and users would not have to go to multiple sites looking for the particular bit they are looking for.”[ http://history.perl.org/packratsarch/93 for the full message ] The idea sits dormant for over a year until Jarkko prods the packrats about it in early 1995. Jarkko works on the CPAN archive and Andreas also tosses around the concept of a ‘Master Module Archive’. CPAN announced to the world on 26 October 1995 http:// www.cpan.org/clpa/1995-10/19951026-142858 Who was instrumental in bringing CPAN from concept to reality? - Bill Middleton, Mark of Coombs, Tom Christiansen, Andreas König, Jared Rhine, Jarkko Hietaniemi, Stephen Potter, Tim Bunce, Jon Orwant Where is CPAN? Everywhere...well, almost.
    [Show full text]
  • Buildroot Vs Yocto: Differences for Your Daily Job
    Buildroot vs Yocto: Differences for Your Daily Job Luca Ceresoli — AIM Sportline [email protected] http://lucaceresoli.net ELC-E 2018 About me • Embedded Linux engineer at AIM Sportline http://www.aim-sportline.com/ • Develop products on custom hardware • Kernel, drivers, bootloader, FPGA • Integration, build system • Open source enthusiast • Contributor to Buildroot, the Linux kernel and a few other projects 1 Introduction • This is not a feature comparison, not a selection guide • If you need one: • Buildroot vs. OpenEmbedded/Yocto: A Four Hands Discussion, Belloni and Petazzoni, ELC 2016 (slides and video online) • http://www.jumpnowtek.com/linux/ Choosing-an-embedded-linux-build-system.html • https://opensource.com/article/18/6/embedded-linux-build-tools • Fact: both tools have pros and cons This is not… • This is not a tutorial 2 • If you need one: • Buildroot vs. OpenEmbedded/Yocto: A Four Hands Discussion, Belloni and Petazzoni, ELC 2016 (slides and video online) • http://www.jumpnowtek.com/linux/ Choosing-an-embedded-linux-build-system.html • https://opensource.com/article/18/6/embedded-linux-build-tools • Fact: both tools have pros and cons This is not… • This is not a tutorial • This is not a feature comparison, not a selection guide 2 • Fact: both tools have pros and cons This is not… • This is not a tutorial • This is not a feature comparison, not a selection guide • If you need one: • Buildroot vs. OpenEmbedded/Yocto: A Four Hands Discussion, Belloni and Petazzoni, ELC 2016 (slides and video online) • http://www.jumpnowtek.com/linux/ Choosing-an-embedded-linux-build-system.html • https://opensource.com/article/18/6/embedded-linux-build-tools 2 This is not… • This is not a tutorial • This is not a feature comparison, not a selection guide • If you need one: • Buildroot vs.
    [Show full text]