Changes between Version 40 and Version 41 of Developer/Projects/Open/TraceTool

Timestamp:

08/10/09 20:01:21 (15 years ago)

Author:

Cocanlucian

Comment:

Developer/Projects/Open/TraceTool

@@ -45 +45 @@
 
 
-   Usage: ./rtems_trace.py -m link 
-                           -i name of the compiler
+   Usage: ./rtems_trace.py '''-m''' ''link''
+                           '''-i''' ''name of the compiler''
                            -b RTEMS build path
-                           -o path to the compiled wrapping code 
-                           -  list of comma separated 
+                           -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   
+                           --compiler=name of the compiler   
                            --build=RTEMS build path
-                           --trace-obj=
+                           --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
 
-                           --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.
 = Decode mode =