![]() Project are basically the repositories to fetch, they will use the remote defined above, the name on the hosting server, and then clone them into a path. Remotes are defined as below, they are named to be used later for each project: Take as an example the manifest located in: Defaults This will generate a directory structure with the given repositories defined in the XML manifest, normally in Yocto it will create a sources directory with each layer, and a setup script to create a build. m NAME.xml, -manifest-name=NAME.xml: initial manifest file (defaults to default.xml), you can also use this to specify a completely different manifest in your system and it will be used.Īfter doing repo init, you can sync it using: b REVISION, -manifest-branch=REVISION : manifest branch or revision (use HEAD for default) ![]() u URL, -manifest-url=URL : manifest repository location With these options being the most important: For example, using a Boundary Devices repository with a manifest we can use: Repo uses an XML manifest in order to enumerate multiple remotes, repositories, branches and revisions, then it fetches them. Append the directory if it's not already in PATH Add repo script to bin directory in home.Ģ. The repo command is an executable Python script that you can put anywhere in your path.ġ. Repo is not meant to replace Git, only to make it easier to work with Git. Repo helps manage many Git repositories, does the uploads to revision control systems, and automates parts of the development workflow. In here you can find some tools and how to use them related to Yocto.įrom repo documentation: repo is a tool built on top of Git. ![]() 3 Using tools inside a docker container.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |