You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I avoided creating any dependency on yourkit. In addition, there was
no way to give arguments to the JVM without losing the ones defined in
ANT_OPTS, which has been a massive pain for a while. So there is now
"jvm.opts" which is simply appended to ANT_OPTS, e.g.
% ant -Djvm.opts=-verbose
[echo] Forking with JVM opts: -Xms1536M -Xmx2g -Xss1M -XX:MaxPermSize=192M -XX:+UseParallelGC -verbose
There is a minimal stub defining a profiler interface:
scala.tools.util.Profiling
Then the yourkit wrapper implements that interface. Once your locker has
been rebuilt once, you can do this:
ant yourkit.run
And it will build quick.lib/comp with profiling enabled, assuming it
can find the necessary files. See the yourkit.init target for values to
change: or ant -Dyourkit.home=/path/to/it might be enough.
Review by dragos.
Copy file name to clipboardExpand all lines: build.xml
+59-7Lines changed: 59 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,6 @@
1
1
<?xml version="1.0" encoding="UTF-8"?>
2
2
3
3
<projectname="sabbus"default="build">
4
-
5
4
<description>
6
5
SuperSabbus for Scala core, builds the scala library and compiler. It can also package it as a simple distribution, tests it for stable bootstrapping and against the Scala test suite.
7
6
</description>
@@ -185,16 +184,18 @@ PROPERTIES
185
184
<!-- These are NOT the flags used to run SuperSabbus, but the ones written
186
185
into the script runners created with scala.tools.ant.ScalaTool -->
0 commit comments