[Soot-list] Not jimplify entire java standard library in whole-program mode

[Thomas Finsterbusch]

As I understand it from the soot documentation and the mailing list archive, 
soot looks at the entire standard library when running an analysis in 
whole-proram mode. "Looking at" means it jimplifies the classes, but it does 
not apply the jimple-phase transformations (at least not by default), since 
they are considered library classes and not application classes. 

Now, is it possible for me to turn off the jimplification process also? I want 
to perform a data flow analysis on my own .class files, but I don't want the 
overhead of indexing the entire standard library, which costs me about 2.5 
minutes and 1GB of RAM every time I run my analysis with soot. I need to run 
it in whole-program mode because I need access to the call graph and possibly 
the spark points-to analysis.

Am I overlooking something?

--Thomas