From 96d6da4e252b06dcfdc041e7df23e86161c33007 Mon Sep 17 00:00:00 2001 From: rihab kouki Date: Tue, 28 Jul 2020 11:24:49 +0100 Subject: Official ARM version: v5.6.0 --- docs/Pack/html/createPackPublish.html | 24 ++++++++++++++++++++---- 1 file changed, 20 insertions(+), 4 deletions(-) (limited to 'docs/Pack/html/createPackPublish.html') diff --git a/docs/Pack/html/createPackPublish.html b/docs/Pack/html/createPackPublish.html index 4a5207a..466f7fb 100644 --- a/docs/Pack/html/createPackPublish.html +++ b/docs/Pack/html/createPackPublish.html @@ -32,7 +32,7 @@ Logo
CMSIS-Pack -  Version 1.5.0 +  Version 1.6.0
Delivery Mechanism for Software Packs
@@ -111,6 +111,22 @@ $(document).ready(function(){initNavTree('createPackPublish.html','');});

There are multiple ways to distribute a software pack:

+

+Prerequisites

+

Before you start to distribute a software pack, you need to make sure that it does not contain errors. An error- and warning-free run of the gen_pack.bat script from the Pack Tutorial is a good start. but you also need to make sure that the schema has been validated. Pack Installer provides an easy mechanism to check the XML schema:

+
    +
  • Install the pack using Pack Installer.
    • +
  • Right-click on the pack version number and select Schema Check:
    +
    +schema_check.png +
    +
    • +
  • The Output window shows the result. If errors are reported, please make sure to fix them before continuing.
    +
    +schema_check_output.png +
    + This is especially important when handing in the pack to be indexed by Arm's pack index service. The pack importer will ignore all PDSC files that do not pass the check against the most recently published PACK.xsd schema file and thus your pack will not be available for download.
    • +

Local Installation

The easiest way to distribute a software pack is attaching it to an email or using other means of electronic distribution (for example using a company internal file server). The installation of a software pack is usually triggered by double-clicking the Pack file. The pack management tool is invoked and the Pack is installed on the local machine. After installation, the Pack will be shown in the list of installed packs (tool dependent). If the PDSC file does not contain a valid <url> element, a manual installation is required to update a software pack. Otherwise, pack management tools can check for updates on the server or the local machine that is specified by <url>.

@@ -145,8 +161,8 @@ Web installation and update

-Publishing on www.keil.com/pack

-

Arm maintains a list of available software packs. If you wish to add your packs to that list, send either your vendor.pidx file or your PDSC file to the following email address: CMSIS@arm.com. The PIDX file will be processed and all referenced PDSC files will be validated. The following content will be processed in order to generate the web site (www.keil.com/dd2/pack) and index file (www.keil.com/pack/index.pidx):

+Publishing using Arm's Pack Index Service +

Arm maintains a list of available software packs. If you wish to add your packs to that list, send either your vendor.pidx file or your PDSC file to the following email address: CMSIS@arm.com. The PIDX file will be processed and all referenced PDSC files will be validated. The following content will be processed in order to generate the web site (https://developer.arm.com/embedded/cmsis/cmsis-packs):