Doc:latest/evalguide/app ide - Revision history

Prasad: /* Generating Configuration and Source Code */

2014-11-11T02:53:53Z

‎Generating Configuration and Source Code

2014-11-05T10:25:33Z

‎Configuring & Building Generated Code, and Starting SAFplus Platform

2014-11-05T10:24:11Z

‎Configuring & Building Generated Code, and Starting SAFplus Platform

2014-11-05T10:20:51Z

‎Configuring & Building Generated Code, and Starting SAFplus Platform

2014-11-05T10:19:53Z

‎Configuring & Building Generated Code, and Starting SAFplus Platform

2014-11-05T10:17:59Z

‎Configuring & Building Generated Code, and Starting SAFplus Platform

2014-11-05T10:13:38Z

‎Configuring & Building Generated Code, and Starting SAFplus Platform

2014-11-05T10:10:52Z

‎Configuring & Building Generated Code, and Starting SAFplus Platform

2014-11-05T10:05:27Z

‎Configuring & Building Generated Code, and Starting SAFplus Platform

2014-11-05T10:04:18Z

‎Configuring & Building Generated Code, and Starting SAFplus Platform

@@ Line 62: / Line 62: @@
 <li>'''Python Location''':
-<br>Again the location of Python 2.4.2 should appear by default. If this is not the case python can be located within
+<br>Again the location of Python 2.4.2 or above should appear by default. If this is not the case python can be located within
 <br><code><installation-directory>/6.1/buildtools/local/bin</code>
 <br>The default <code><installation-directory></code> is <code>/opt/clovis</code> for root installation and <code>$HOME/clovis</code> for non root users. This is determined during the installation of the SDK.

@@ Line 99: / Line 99: @@
 </pre></code>
-<li>[[Doc:latest/evalguide/build#Configuration file - target.conf|Configuration file - target.conf]]
+<li>[[Doc:latest/evalguide/build#Configuration File - target.conf|Configuration file - target.conf]]
 <br>The Hardware Setup choice you made will be required here in setting up the target.conf file

@@ Line 111: / Line 111: @@
 <br>Once the  images have been created this section provides information on how these can be copied to the target.
-Once the images are copied to their targets we now have to start/stop SAFplus Platform. This is discussed within Section [[Doc:Evalguide/csa#Starting and Stopping SAFplus|Starting and Stopping SAFplus]].
+Once the images are copied to their targets we now have to start/stop SAFplus Platform. This is discussed within Section [[Doc:latest/evalguide/csa#Starting and Stopping SAFplus Platform|Starting and Stopping SAFplus Platform]].
 </ul>

@@ Line 105: / Line 105: @@
 <br>Lists commands required to build the target images.
-<li>[[Doc:Evalguide/build#Content of Target Images|Content of Target Images]]
+<li>[[Doc:latest/evalguide/build#Content of Target Images|Content of Target Images]]
 <br>Provides details of the content of the target images for both the singe and distributed setups.
-<li>[[Doc:Evalguide/build#Runtime Software Installation|Runtime Software Installation]]
+<li>[[Doc:latest/evalguide/build#Runtime Software Installation|Runtime Software Installation]]
 <br>Once the  images have been created this section provides information on how these can be copied to the target.

@@ Line 102: / Line 102: @@
 <br>The Hardware Setup choice you made will be required here in setting up the target.conf file
-<li>[[Doc:Evalguide/build#Building Single/Distributed Target Image(s)|Building Single/Distributed Target Image(s)]]
+<li>[[Doc:latest/evalguide/build#Building Single/Distributed Target Image(s)|Building Single/Distributed Target Image(s)]]
 <br>Lists commands required to build the target images.

@@ Line 93: / Line 93: @@
 <li>[[Doc:latest/evalguide/build#Building SAFplus Platform and the Evaluation System|Building SAFplus Platform and the Evaluation System]]
-<br>Provides details on how to configure and build SAFplus Platform and the generated model. One small difference here is that when we run <code><install_dir>/sdk-5.0/src/SAFplus/configure -with-model-name</code> it should be run with the generated eval model. E.g.:
+<br>Provides details on how to configure and build SAFplus Platform and the generated model. One small difference here is that when we run <code><install_dir>/6.1/sdk/src/SAFplus/configure -with-model-name</code> it should be run with the generated eval model. E.g.:
 <code><pre>
-$ <install_dir>/sdk-5.0/src/SAFplus/configure \
+$ <install_dir>/6.1/sdk/src/SAFplus/configure \
    --with-asp-build --with-model-name=eval
 </pre></code>

@@ Line 89: / Line 89: @@
 <ul>
-<li>[[Doc:Evalguide/build#Modifying the Clovis Sample Applications|Modifying the Clovis Sample Applications]]
+<li>[[Doc:latest/evalguide/build#Modifying the Clovis Sample Applications|Modifying the Clovis Sample Applications]]
 <br>Provides instructions on modifying the generated code.

@@ Line 86: / Line 86: @@
 The next logical step is to configure and build this code. There are two methods of doing this, the first via the OpenClovis IDE, as covered within the ''OpenClovis Sample Application Tutorial''.
-The second method, as discussed earlier, is via the command line. As you already have this document open we suggest looking again at Chapter [[Doc:Evalguide/build#Building the Evaluation System and Deploying Runtime Images|Building the Evaluation System and Deploying Runtime Images]]:
+The second method, as discussed earlier, is via the command line. As you already have this document open we suggest looking again at Chapter [[Doc:latest/evalguide/build#Building the Evaluation System and Deploying Runtime Images|Building the Evaluation System and Deploying Runtime Images]]:
 <ul>