FAQ - Revision history

Jefro: /* How can I use my own kernel with my project? */

2015-05-04T17:18:21Z

How can I use my own kernel with my project?

← Older revision		Revision as of 17:18, 4 May 2015
Line 220:		Line 220:
	==== How can I use my own kernel with my project? ====		==== How can I use my own kernel with my project? ====

	If you just want to change the kernel configuration, you can follow [http://www.yoctoproject.org/docs/current/kernel-~~manual~~/kernel-~~manual~~.html~~#kernel-configuration~~ these instructions] to edit the stock kernel's configuration using <code>make menuconfig</code>.		If you just want to change the kernel configuration, you can follow [http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html these instructions] to edit the stock kernel's configuration using <code>make menuconfig</code>.

	If you have a separate kernel you wish to use, the simplest method for adding a new kernel to your build is to create a recipe for it and then add a line like this to <code>conf/local.conf</code>:		If you have a separate kernel you wish to use, the simplest method for adding a new kernel to your build is to create a recipe for it and then add a line like this to <code>conf/local.conf</code>:

Jefro: /* How can I add a package to my project? */

2015-04-20T17:27:44Z

How can I add a package to my project?

← Older revision		Revision as of 17:27, 20 April 2015
Line 216:		Line 216:
	IMAGE_INSTALL_append = " package1 package2 package3"		IMAGE_INSTALL_append = " package1 package2 package3"

	For more information, read [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-~~addpkg~~ this chapter in the Yocto Project Development Manual].		For more information, read [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage-localconf this chapter in the Yocto Project Development Manual].

	==== How can I use my own kernel with my project? ====		==== How can I use my own kernel with my project? ====

Dennis Meier: /* Technical */

2013-12-18T12:14:54Z

Technical

← Older revision		Revision as of 12:14, 18 December 2013
Line 198:		Line 198:

	The Yocto Project is an open source project with support provided by the open source community. Products can be created by OSVs who use the Yocto Project as their upstream or by customers who create their own “roll your own” Linux products from the Yocto Project.		The Yocto Project is an open source project with support provided by the open source community. Products can be created by OSVs who use the Yocto Project as their upstream or by customers who create their own “roll your own” Linux products from the Yocto Project.

			==== What are the Yocto ADT and Yocto SDK and how do they relate? ====

			The Yocto Project provides support for target-device software developers. The SDK (software developement kit) can be created using ''bitbake <image> -c populate_sdk'', which builds the cross-toolchain and produces an installer in the build/tmp/deploy/sdk directory. This installer contains the image's rootfs and environment setup scripts that are needed for cross-developement. The ADT (application developper tools) are based on the SDK (i.e. architecture-specific cross-toolchain and matching sysroot), but when talking about the ADT we also mean the Eclipse Yocto Plug-in, the Quick EMUlator (QEMU, which lets you simulate target hardware) and various user-space tools (e.g. for application profiling or latency measurements).

	== Usage FAQs ==		== Usage FAQs ==

Waynr: removed extraneous initial spaces from paragraphs

2012-09-28T20:06:25Z

removed extraneous initial spaces from paragraphs

Show changes

Waynr: Changed Bold Q/A sections into headings to create page index, slight reorganization and added answer to the release-cycle question. Could do with a closer inspection to more sensibly organize the "Technical" section

2012-09-28T20:02:07Z

Changed Bold Q/A sections into headings to create page index, slight reorganization and added answer to the release-cycle question. Could do with a closer inspection to more sensibly organize the "Technical" section

Show changes

Jefro: /* Usage FAQs */

2012-08-23T17:15:37Z

Usage FAQs

← Older revision		Revision as of 17:15, 23 August 2012
Line 211:		Line 211:
	If you have a separate kernel you wish to use, the simplest method for adding a new kernel to your build is to create a recipe for it and then add a line like this to <code>conf/local.conf</code>:		If you have a separate kernel you wish to use, the simplest method for adding a new kernel to your build is to create a recipe for it and then add a line like this to <code>conf/local.conf</code>:

	PREFERRED_PROVIDER_virtual/kernel= "<i>your-recipe-for-kernel</i>"		PREFERRED_PROVIDER_virtual/kernel = "<i>your-recipe-for-kernel</i>"

	You can find several kernel examples in the Yocto Project file's meta/recipes-kernel/linux directory that you can use as references. [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#platdev-newmachine-kernel Look here] for more information.		You can find several kernel examples in the Yocto Project file's meta/recipes-kernel/linux directory that you can use as references. [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#platdev-newmachine-kernel Look here] for more information.

Rpjday at 16:51, 21 August 2012

2012-08-21T16:51:06Z

← Older revision		Revision as of 16:51, 21 August 2012
Line 198:		Line 198:
	IMAGE_INSTALL_append = " package"		IMAGE_INSTALL_append = " package"

	Use your own package name in place of '''package'''. Note the leading space before the package name.		Use your own package name in place of '''package'''. Note the leading space before the package name. If you want to add multiple packages, you can
			use multiple lines like the above, or list all packages on a single line with:

			IMAGE_INSTALL_append = " package1 package2 package3"

	For more information, read [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-addpkg this chapter in the Yocto Project Development Manual].		For more information, read [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-addpkg this chapter in the Yocto Project Development Manual].

PaulEggleton: Use _append = not _append +=, the latter does nothing (except adding a space which we don't need)

2012-08-21T16:34:30Z

Use _append = not _append +=, the latter does nothing (except adding a space which we don't need)

← Older revision		Revision as of 16:34, 21 August 2012
Line 196:		Line 196:
	'''A:''' As with any complex system, the real answer is ''it depends'', but of course that is not very helpful. The simplest method for adding a single package to your build is to add a line like this to <code>conf/local.conf</code>:		'''A:''' As with any complex system, the real answer is ''it depends'', but of course that is not very helpful. The simplest method for adding a single package to your build is to add a line like this to <code>conf/local.conf</code>:

	IMAGE_INSTALL_append += " package"		IMAGE_INSTALL_append = " package"

	Use your own package name in place of '''package'''. Note the leading space before the package name.		Use your own package name in place of '''package'''. Note the leading space before the package name.

Jefro at 20:30, 10 July 2012

2012-07-10T20:30:32Z

← Older revision		Revision as of 20:30, 10 July 2012
Line 199:		Line 199:

	Use your own package name in place of '''package'''. Note the leading space before the package name.		Use your own package name in place of '''package'''. Note the leading space before the package name.

			For more information, read [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-addpkg this chapter in the Yocto Project Development Manual].

			'''Q: How can I use my own kernel with my project?'''

			'''A:''' If you just want to change the kernel configuration, you can follow [http://www.yoctoproject.org/docs/current/kernel-manual/kernel-manual.html#kernel-configuration these instructions] to edit the stock kernel's configuration using <code>make menuconfig</code>.

			If you have a separate kernel you wish to use, the simplest method for adding a new kernel to your build is to create a recipe for it and then add a line like this to <code>conf/local.conf</code>:

			PREFERRED_PROVIDER_virtual/kernel= "<i>your-recipe-for-kernel</i>"

			You can find several kernel examples in the Yocto Project file's meta/recipes-kernel/linux directory that you can use as references. [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#platdev-newmachine-kernel Look here] for more information.

	'''Q: Who may I contact for further questions regarding the Yocto Project?'''		'''Q: Who may I contact for further questions regarding the Yocto Project?'''

	'''A:''' For any additional questions, please contact [mailto:jeffrey.osier-mixon@intel.com Jeff Osier-Mixon], the Yocto Project Community Manager.		'''A:''' For any additional questions, please contact [mailto:jeffrey.osier-mixon@intel.com Jeff Osier-Mixon], the Yocto Project Community Manager.

Jefro at 23:49, 29 June 2012

2012-06-29T23:49:07Z

← Older revision		Revision as of 23:49, 29 June 2012
Line 1:		Line 1:
	'''Yocto Project Public Messages and FAQ'''		'''Yocto Project Public Messages and FAQ'''

	Last edited: ~~10 November~~, ~~2011~~		Last edited: 29 June, 2012

			Note: technical FAQs are being added to the end of this document


Line 61:		Line 62:
	'''Q: Why not just call this project Poky? What has changed between Poky and the Yocto Project?'''		'''Q: Why not just call this project Poky? What has changed between Poky and the Yocto Project?'''

	'''A:''' The Yocto Project is an umbrella project. Accordingly, it includes a number of projects and resources specifically intended for facilitating development with Linux on embedded devices, and it is an appropriate place for larger organizations to collaborate on the development of build infrastructure for embedded Linux. Poky is one of the the largest components of the Yocto Project, and Poky continues as an independent, open source project developing the build system used by the Yocto Project, as well as by other open source projects.		'''A:''' The Yocto Project is an umbrella project. Accordingly, it includes a number of projects and resources specifically intended for facilitating development with Linux on embedded devices, and it is an appropriate place for larger organizations to collaborate on the development of build infrastructure for embedded Linux. Poky is one of the the largest components of the Yocto Project, and Poky continues as an independent, open source project developing the build system used by the Yocto Project, as well as by other open source projects.

			Poky is a reference system for the Yocto Project, showing how the tools work together. It includes BitBake, openembedded-core, and several other components that anyone can use to start developing with embedded Linux. Poky as a build system is tested by the Yocto Project teams before each release. When you download and use the Yocto Project build system, you are actually downloading Poky and using it to create a distribution that by default is also named Poky. (You can, of course, name your distribution anything you like.)


Line 67:		Line 70:
	'''Q: What is the difference between OpenEmbedded and the Yocto Project?'''		'''Q: What is the difference between OpenEmbedded and the Yocto Project?'''

	'''A:''' The Yocto Project and OpenEmbedded share a core collection of metadata called openembedded-core. However, the two organizations remain separate, each with its own focus. OpenEmbedded provides a comprehensive set of metadata for a wide variety of architectures, features, and applications. The Yocto Project focuses on providing powerful, easy-to-use, well-tested tools, metadata, and board support packages (BSPs) for a core set of architectures and specific boards.		'''A:''' The Yocto Project and OpenEmbedded share a core collection of metadata called openembedded-core. However, the two organizations remain separate, each with its own focus. OpenEmbedded provides a comprehensive set of metadata for a wide variety of architectures, features, and applications. The Yocto Project focuses on providing powerful, easy-to-use, interoperable, well-tested tools, metadata, and board support packages (BSPs) for a core set of architectures and specific boards.


Line 187:		Line 190:
	'''A:''' The Yocto Project is an open source project with support provided by the open source community. Products can be created by OSVs who use the Yocto Project as their upstream or by customers who create their own “roll your own” Linux products from the Yocto Project.		'''A:''' The Yocto Project is an open source project with support provided by the open source community. Products can be created by OSVs who use the Yocto Project as their upstream or by customers who create their own “roll your own” Linux products from the Yocto Project.

			== Usage FAQs ==

			'''Q: How can I add a package to my project?'''

			'''A:''' As with any complex system, the real answer is ''it depends'', but of course that is not very helpful. The simplest method for adding a single package to your build is to add a line like this to <code>conf/local.conf</code>:

			IMAGE_INSTALL_append += " package"

			Use your own package name in place of '''package'''. Note the leading space before the package name.

	'''Q: Who may I contact for further questions regarding the Yocto Project?'''		'''Q: Who may I contact for further questions regarding the Yocto Project?'''

	'''A:''' For any additional questions, please contact [mailto:jeffrey.osier-mixon@intel.com Jeff Osier-Mixon], the Yocto Project Community Manager.		'''A:''' For any additional questions, please contact [mailto:jeffrey.osier-mixon@intel.com Jeff Osier-Mixon], the Yocto Project Community Manager.