Yocto Project - User contributions [en]

TipsAndTricks/CreateNewLayer

2016-12-22T11:54:47Z

Brendan Le Foll: Created page with "=Creating a new YP Layer with devtool= == Introduction == Devtool lets you create a new layer very easily == How to Get Started =="

=Creating a new YP Layer with devtool=
== Introduction ==
Devtool lets you create a new layer very easily

== How to Get Started ==

TipsAndTricks

2016-12-22T11:53:51Z

Brendan Le Foll: /* Ideas for Articles */

== Background ==
This wiki page captures ideas for "Tips and tricks" articles that are aimed Yocto Project users that have a basic understanding of the core tools and want to extend their knowledge. Articles will written and published using the following process
* Articles must refer to the current (or earlier) release. They must not cover features in development in the master branch.
* Anyone can add entries to the '''Ideas for Articles''' section based on challenges they have encountered when using the Yocto Project
* More experienced developers can start to flesh out articles in the ''Ideas'' section move then to '''Articles in Development''' or contribute directly to this section.
* Approximately once a month an article ready for publishing will be chosen for publication by [mailto:jeffrey.osier-mixon@intel.com Jefro]. The article will be enhanced with the help of a subject matter expert and technical writer and moved to the '''Published Articles ''' section and then published on the Yocto Project wiki and sent to mailing list.

Please contact [mailto:henry.bruce@intel.com?Subject=Yocto%20Project%20Tips%20and%20Tricks Henry Bruce] with any questions.

== Ideas for Articles ==
* [[TipsAndTricks/GeneratingASDK]] (Ross, Paul help please...)
* [[TipsAndTricks/EnablingAPackageFeed]] (Ross)
* [[TipsAndTricks/AddingALicense]] (Ross)
* [[TipsAndTricks/DevPyShell]] (Richard Purdie)
* [[TipsAndTricks/How To Create a BSP]]. And what not to put in it.
* [[TipsAndTricks/Patchwork]]
* [[TipsAndTricks/Patchtest]] (Leo)
* [[TipsAndTricks/CreateNewLayer]] (Brendan)

== Articles in development ==
* [[TipsAndTricks/DebugNativeRecipeWithGdb]] (Joshua Lock)
* [[TipsAndTricks/Netconsole]] (Ross Burton)
* [[TipsAndTricks/ParsingProfiling]] (Richard Purdie)
* [[TipsAndTricks/DemystifyingTheLinuxYoctoKernel]] (Tom Zanussi)
* [[TipsAndTricks/Patching the source for a recipe]] (Paul Eggleton)
* [[TipsAndTricks/Incorporating closed source components]] (Paul Eggleton)
* [[TipsAndTricks/DebuggingAvoidingRebuilds]] (Richard Purdie)
* [[TipsAndTricks/GitBisectABitbake]] (Ross)
* [[TipsAndTricks/PackagingNonversionedLibrary]] (Ross)
* [[TipsAndTricks/RunningEclipseAgainstBuiltImage]] (bavery)
* [[TipsAndTricks/UsingBuildstatsDiff]] (Ross)
* [[TipsAndTricks/PrelinkSomePointersAndWorkarounds]] (bavery)
* [[TipsAndTricks/RunningQemuOnMacOSX]] (Stephano)
* [[TipsAndTricks/Understanding what changed (diffsigs etc)]] (Joshua)
* [[TipsAndTricks/DockerOnImage]] (bavery)
* [[TipsAndTricks/CropsCLIContainers]] (bavery)
* [[TipsAndTricks/QuickAndDirtyKernelConfig]] (bavery)
* [[TipsAndTricks/TestingToasterWithContainers]] (bavery)
* [[TipsAndTricks/InvestigatingBuildTime]] (Leo Sandoval)

== Finished Articles ==
* [[TipsAndTricks/Packaging Prebuilt Libraries | Packaging Prebuilt Libraries]].
* [[TipsAndTricks/NPM | Packaging Node.js Projects]].

TipsAndTricks/NPM

2016-06-27T14:58:03Z

Brendan Le Foll: Created page with "Node.js packages and applications tend to differ from other applications. They tend to have alot of 'smaller' dependencies and often are not very descriptive of what versions ..."

Node.js packages and applications tend to differ from other applications. They tend to have alot of 'smaller' dependencies and often are not very descriptive of what versions of these dependencies they require.

Yocto provides a number to tools to help people packaging node modules from NPM (Node Package Manager) and fit within the traditional metadata structure and obey the do_compile/do_fetch rules as well as helping you check your licensing requirements. This post will show you various methods to make package creation easier.

== Recipetool ==

Recipetool now allows an npm URL to be given like this:

recipetool create "npm://registry.npmjs.org;name=grunt-cli;version=1.1.0"

Note that registry.npmjs.org is the default NPM registry but any registry URL can be used. The name and version tags should be self documenting. Behind the scene, recipetool will download each dependency and write a recipe file. The recipe file is fairly simple but will contain every license that recipetool has found and include it in the LIC_FILES_CHKSUM. Note alot of node modules have unclear licensing so "unknown" happens alot in the LICENSE field, have a look at the modules not listed.

== Integrity of your package ==

Recipetool will also create a shrinkwrap and lockdown file for your recipe. Shrinkwrap files in npm are used to make sure that the full dependency chain of a node module is the same as the user expected. Alot of packages don't provide this so we create one on the fly, you can replace it with your own. Lockdown checks that the files recipetool downloaded are the same as the ones your users will download when using your recipe. This simply checks dependencies have not been changed and that your NPM registry is still handing out the same file.

== Building & dependencies ==

Some stuff here

== Examples ==

TipsAndTricks

2016-06-27T14:44:40Z

Brendan Le Foll: /* Articles in development */

== Articles in development ==

* [[TipsAndTricks/DebugNativeRecipeWithGdb]] (Joshua Lock)
* [[TipsAndTricks/Netconsole]] (Ross Burton)
* [[TipsAndTricks/ParsingProfiling]] (Richard Purdie)
* [[TipsAndTricks/NPM]] (Brendan)

== Articles ready for publishing ==