- Done! :-) --Fnl 21:51, 28 November 2007 (UTC)
Does anyone know how to compile in Eclipse with jikes? (which does in fact compile with smaller codesize than the default javac) --Starrynte 06:20, 15 November 2009 (UTC)
|21:49, 16 March 2013
I decided to try using Eclipse after my Robot Editor started crashing every other time I compiled. I followed the Eclipse tutorials and everything is working alright, but I haven't figured out where to find the Codesize of the robot I just compiled.
I tried downloading the code size utility, but the link on the wiki didn't work for me. As a backup, you can always add your workspace project folder under Options -> Preferences -> Development Options in Robocode and use the Robot -> Package robot for upload option. That is what I do.
I actually still use the codesize.jar from an ancient version of Robocode, which I just uploaded here. Usage is like:
java -jar ./robocode_1.07/codesize.jar robocode_1732/robots/voidious.Diamond_1.8.22.jar OR java -jar ./robocode_1.07/codesize.jar robocode_1732/robots/voidious/mini/*.class
There used to be a newer codesize.jar with Robocode, but I never got it to work smoothly from the command line like this.
I think the old codesize can also be used as part of an ant script. Which can be very helpful.
You can find the codesize.jar file in the downloads section of the Sourceforge Robocode site. I set up a script that reruns the codesize calculation each time I hit a key, and I check after I compile.
Oh, and I use jGrasp as an IDE, I find Eclipse to be a bit heavyweight for bot development.
Thank you all for your help. I like using Eclipse as an IDE, but it isn't really suited for low-Codesize development. I thought about writing my code in Eclipse and then copying it to the Robot Editor to compile it, but I still haven't fixed the issue with the robot database.
Hi mate. Not sure if you have figured this out by now, you can set up an "External Tool Configuration" in Eclipse. I wrote a little script (very basic) and saved for every bot a configuration with the name pattern. After that you can start the script after every change you made and eclipse will show you the codesize of your classes. Depending on you scripting skills you can do almost everything you need (like sum up the class sizes and whatnot).
for i in $*
java -jar ./codesize.jar <your_development_path>/$i*.class