From faa47b1d830a510b0923245fca2f9e204d92d63a Mon Sep 17 00:00:00 2001 From: Miruna Paun Date: Thu, 4 May 2017 16:45:20 +0200 Subject: Removing the include note in relnotes virt LXCR-7635 continuing updates of el relnotes virt LXCR-7714 adding need prebuilt images and source info Signed-off-by: Miruna Paun --- .../doc/build_boot_template.xml | 10 +- .../doc/getting_enea_linux.xml | 227 +++++++++++++++------ 2 files changed, 174 insertions(+), 63 deletions(-) diff --git a/doc/book-enea-linux-release-info/doc/build_boot_template.xml b/doc/book-enea-linux-release-info/doc/build_boot_template.xml index 2200997..e39dd81 100644 --- a/doc/book-enea-linux-release-info/doc/build_boot_template.xml +++ b/doc/book-enea-linux-release-info/doc/build_boot_template.xml @@ -7,8 +7,14 @@ If the source has been fetched (), there will be a target specific README file containing the build and boot instructions. To make it easier for the - reader, the contents of these build/boot instruction have been extracted - into the following sections. + reader, the contents of this file(s) have been extracted into the following + sections. + + + The build process duration may vary and be longer than expected in + some cases, depending on the individual build resources and parameters of + each target/machine supported in this release. + NOTE: Only EDIT THE TEMPLATE build_boot_template.xml file here and also only edit the manifest template ".README" (name starting by a dot)! diff --git a/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml b/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml index 055be15..f1617c3 100644 --- a/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml +++ b/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml @@ -4,81 +4,186 @@ Getting Enea Linux + Enea Linux is available as both pre-built binary images and source + code. Both serve a specific purpose and each have their advantages. However, + using the pre-built binary images allows for getting up and running faster. + Please refer to the sections below for details on how to get Enea Linux as + pre-built binary images or source code. +
Getting Pre-built Binaries - Application developers will download pre-complied images from the - Enea Portal or will receive prebuilt images from the platform developers. - For further information on this see Enea Linux Application - Development Guide. -
+ Enea Linux pre-built binaries are available for download on Enea + Download Portal. Log in using the credentials provided. Using the + menu, browse to the Linux section. You + will now have access to the Files section + and the Online Documentation + section. -
- Getting the Source - - The source for this Enea Linux release is available for cloning from - a set of Git repositories. To manage the different repositories, Google's - repo tool is used. The basic idea is to store a list with (repo-URL, - version) tuples in a separate file, known as the manifest. The repo tool - is then used to traverse the list and clone the specified versions of the - repositories. See https://code.google.com/p/git-repo/ - for more info. + The Files section lists each Enea Linux distribution, one for each + version and profile, as a separate download package. Clicking on the name + of the distribution will open a new page, which presents further details + about the content of the release and a list of downloadable archives, one + for each hardware target included in the release. Each archive provides + the following content: + + + + images directory – this directory + includes the binary image files needed to boot the target with Enea + Linux. This includes the kernel, the root file system, device tree, + etc. + + + + sdk directory – this directory + includes the installer for the SDK. + + + + rpm directory – this directory + contains all the packages included in the distribution in rpm format, + which can be installed using the package manager. + + + + For faster downloads, each archive is mirrored in several places, + geographically. Choose the archive in the region closest to you. - To use repo tool to download the source for Enea Linux, follow the - steps below: + The Documentation section lists all the documents delivered with the + release: - + - Make sure that the repo tool is installed. If not, follow the - instructions below. The instruction assumes a suitable place in your - PATH to use. You might change that.INFO: Below is include of - ID "eltf-getting-repo-install-command" from - eltf_params_updated.xml - - + Enea Linux Platform Developer’s Guide - Use the repo tool to download the source: Please define MACHINE - to your target, uncomment and use one of the MACHINE lines listed - here,Below is the "machine_list" programlisting in - machine_list_generated.xml created by the make system by extracting - from the manifest - - - - and use the repo command below: Below is include of ID - "eltf-repo-cloning-enea-linux" from eltf_params_updated.xml. Here the - $MACHINE shall be given! - - + Enea Linux Application Developer's Guide + + change profile as required - - The source code is now downloaded. Current directory will contain a - README file with instructions on how to build the distro and boot the - target. For convenience, these instructions are also copied into this - document. See . + + Enea Linux Virtualization Guide + + + + Enea Linux Open Source Report + + + + Eclipse Open Source Report + + + + Enea Linux Release Info + + +
+ +
+ Getting the Sources + + Enea Linux sources are available for cloning from a set of Git + repositories on git.enea.com. + Since Enea Linux requires multiple repositories, Google Repo tool is used + in order to manage configurations and make the cloning step simpler. + Google Repo tool uses files, known as manifests, which store a list of + tuples (repository URL, version). The Repo tool is then used to traverse + the list of tuples in the manifest file and clone the specified versions + of each repository. See https://code.google.com/p/git-repo/ + for more info. + +
+ Get access to git.enea.com + + In order to get access to git.enea.com, a ssh key is required for + Git authentication. If you don't already have such a key, follow the + steps below to generate one: + + + + Generate the ssh key pair: + + $ ssh-keygen -t rsa + + When asked for a password, just press Enter. This will create + two files in the .ssh directory in your home directory. + + id_rsa +id_rsa.pub + + + + Copy the public key into an authorized_keys file: + + $ cat id_rsa.pub >> authorized_keys + + + + Once these steps are done and you have a valid ssh key pair, send + the public key, id_rsa.pub, via email to + mailto:git_support@list.enea.se in order to get access to + git.enea.com. +
+ +
+ Get Sources + + To use the Repo tool to download the sources for Enea Linux, + follow these steps: + + + + Make sure that the repo tool is installed. If not, do the + following: Below is include of ID + "eltf-getting-repo-install-command" from + eltf_params_updated.xml + + + + + + Define the MACHINE from one of the targets listed + here,Below is the "machine_list" programlisting in + machine_list_generated.xml created by the make system by extracting + from the manifest + + + + and use the repo command below: Below is include of ID + "eltf-repo-cloning-enea-linux" from eltf_params_updated.xml. Here + the $MACHINE shall be given! + + + + + + Once the source code is downloaded, the current directory will + contain a README file with instructions on how to build the distro and + boot the machine you choose. For ease of use, these instructions are + also copied into this document, see . - It is not necessary to explicitly clone the manifest repository - since that is done automatically by the repo tool. To see the current - manifest, e.g. to get a list of the repositories, use the following - command: + It's not necessary to explicitly clone the manifest repository + since that is done automatically by the repo tool. To see the current + manifest, use the following command: - $ repo manifest + $ repo manifest - The UG should be updated with instructions on how to add - customisations. That section should also contain some more info about the - manifest: The manifest templates, using a branch instead of the tag EL6, - ... When this is done a reference from here should be added. + The UG should be updated with instructions on how to add + customizations. That section should also contain more info about the + manifest: the manifest templates, using a branch instead of the tag EL6, + etc. When this is done a reference from here should be added. +
\ No newline at end of file -- cgit v1.2.3-54-g00ecf