-
Notifications
You must be signed in to change notification settings - Fork 0
TraceCompass Setup
Please refer to this page for a detailed description of what you need to do to compile tracecompass from source. You will have to do this if you want to use many of its new features including the VM analysis which are part of the incubator. However, I will post some of my experiences with the set up in the following:
-
Note: For using the incubator plugins such as for VM analysis you need to set the target platform to
tracecompass-incubator-master.targetinstead of the tracecompass one. -
Once loading the .target file, you could have complaints such as "No repository found at http://download.eclipse.org/eclipse/updates/4.8milestones/...". In this case just find the next replacement for this repository which in this case would be simply the 4.8 itself: http://download.eclipse.org/eclipse/updates/4.8
-
Make sure you
git pullregularly from both thetracecompassandtracecompass-incubatorrepositories as they are changed frequently and need to be in sync for your code to compile correctly. -
In case requiring
VMblockAnalysisyou would have to clone the following two repositories instead of the above: -
If you get many
deprecatederrors then switch this to warning in your eclipse environment -
I also switched
Invalid @sinceerrors to warnings. I am not sure if this was a correct move though! -
As for the VM related XML analyses, make sure you have views associated with them, because that is what will trigger the analysis, when you open a view. If you do not have views, but want to see the results of the analysis, open the "State System Explorer" view, expand the VM experiment and click on the analysis, this will also trigger the execution.
TODO Warning: Callstack XML analysis: no analysis called org.eclipse.tracecompass.incubator.virtual.machine.analysis.VMblockAnalysis