Changes between Version 42 and Version 43 of Developer/Projects/Open/TraceTool

Timestamp:

08/10/09 20:07:34 (15 years ago)

Author:

Cocanlucian

Comment:

Developer/Projects/Open/TraceTool

@@ -25 +25 @@
 
   
-   Usage: ./rtems_trace.py -m compile 
-                           -i name of the compiler 
-                           -g path to the wrapping code 
-                           -o path to where the compiled wrapping code should be saved
-                           -l path to where the RTEMS libraries were installed
-          ./rtems_trace.py --mode=compile 
-                           --compiler=name of the compiler  
-                           --genpath=path to the wrapping code
-                           --objpath=path to where the compiled wrapping code should be saved
-                           --lib=path to where the RTEMS libraries were installed
+   Usage: ./rtems_trace.py '''-m''' ''compile''
+                           '''-i''' ''name of the compiler''
+                           '''-g''' ''path to the wrapping code''
+                           '''-o''' ''path to where the compiled wrapping code should be saved''
+                           '''-l''' ''path to where the RTEMS libraries were installed''
+          ./rtems_trace.py '''--mode'''=''compile''
+                           '''--compiler'''=''name of the compiler''
+                           '''--genpath'''=''path to the wrapping code''
+                           '''--objpath'''=''path to where the compiled wrapping code should be saved''
+                           '''--lib'''=''path to where the RTEMS libraries were installed''
 
 Using this mode the user can compile all the .c files from a directory (usually the .c files from the wrapping code directory) and save the resulted files (.o files) in the directory specified by the -o option. If the -g and -o options are not specified then the rtems_trace tool will look in the ''wrappers'' directory located in cwd and save the .o files in a directory named ''objects'' also from cwd. Also, if the -l option it's not specified than the tool will choose this path by default: ''/opt/rtems-4.10/i386-rtems4.10/pc386/lib/''.
@@ -47 +47 @@
    Usage: ./rtems_trace.py '''-m''' ''link''
                            '''-i''' ''name of the compiler''
-                           -b RTEMS build path
-                           -o path to the compiled code (.o files)
-                           -  list of comma separated object files that should be included in the final executable
-                           -l path to where the RTEMS libraries were installed
-          ./rtems_trace.py --mode=link 
-                           --compiler=name of the compiler   
-                           --build=RTEMS build path
-                           --objpath=path to the compiled code(.o files)
-                           --trace-o=list of comma separated object files that should be included in the final executable
-                           --lib path to where the RTEMS libraries were installed
+                           '''-b''' ''RTEMS build path''
+                           '''-o''' ''path to the compiled code (.o files)''
+                           '''-'''  ''list of comma separated object files that should be included in the final executable''
+                           '''-l''' ''path to where the RTEMS libraries were installed''
+          ./rtems_trace.py '''--mode'''=''link''
+                           '''--compiler'''=''name of the compiler''
+                           '''--build'''=''RTEMS build path''
+                           '''--objpath'''=''path to the compiled code(.o files)''
+                           '''--trace-o'''=''list of comma separated object files that should be included in the final executable''
+                           '''--lib'''=''path to where the RTEMS libraries were installed''
 
 In this mode, the RTEMS trace tool will link all the object files from the specified directory (or from the default one if no directory is specified using the -o or --objpath option) if the --trace-o option it's not used. The user can specify only a subset of object files to be included in the final executable using the --trace-o option. The final executable file is placed into the same directory where the object files are found, under the ''wrapper.exe'' name.
@@ -180 +180 @@
 = How to use it =
 
+The following section will try to illustrate how to properly use the RTEMS trace tool in order to get the decoded file containing the information needed.
 
  *  Set up the configuration file as explained here.