c2edaf3119
Use Eclipse-computed paths rather than hard-coding absolute paths
2018-04-18 11:29:27 -05:00
dd1f51e8f0
Buildship removed classpath provider thing from all launch configs
...
This consistently happens when I import WALA as an existing Gradle
project into Eclipse with Buildship. I don't really know what this
change means, or whether it's desirable. For now, I'm going to trust
Buildship and see what happens.
2018-04-18 11:29:25 -05:00
530d74929f
Many improvements to Gradle build support, including within Eclipse
2018-04-18 11:29:24 -05:00
99c2493e37
Revert "Build WALA using Gradle instead of Maven" ( #298 )
2018-04-18 12:15:56 -04:00
83abb6a10a
Use Eclipse-computed paths rather than hard-coding absolute paths
2018-04-17 15:02:35 -05:00
fd4d68d278
Buildship removed classpath provider thing from all launch configs
...
This consistently happens when I import WALA as an existing Gradle
project into Eclipse with Buildship. I don't really know what this
change means, or whether it's desirable. For now, I'm going to trust
Buildship and see what happens.
2018-04-17 15:02:35 -05:00
401fbaf89a
Many improvements to Gradle build support, including within Eclipse
2018-04-17 15:02:35 -05:00
d24519e974
cross-cutting changes to make more of WALA runnable with TeaVM. The biggest change is refactoring to AnalysisCache and friends; since TeaVM does not support SoftReference, I needed to add a layer of interfaces so that I can use a more simpleminded caching implementation for TeaVM. There are other changes to Module and friends to break connections with File and URL, which also cause TeaVM grief. I also organized imports in many places to remove unused types that caused trouble.
2017-02-02 20:33:27 -05:00
cab2bcfd07
add an example of constructing IRs and use of ReferenceCleanser
...
git-svn-id: https://wala.svn.sourceforge.net/svnroot/wala/trunk@3805 f5eafffb-2e1d-0410-98e4-8ec43c5233c4
2010-03-15 22:58:41 +00:00
Ben Liblit
Julian Dolby
msridhar1