I just want to point out that there are limitations to your approach. There is a hard limit on the size of the cmd line which is what you depend on when you pass the files individually. Using the @files.txt as I eluded to in my post works around this limitation. It can be used in conjunction with an Ant fileset assuming you echo the fileset to an output file prior to running the command. I’d suggest any custom ant task or tool take this into consideration as there’s nothing more frustrating than picking up an Ant build that was working until you added a few more files. Diagnosing such a problem could be impossible for someone unfamiliar with Ant and RAPC.

<target name=”build” >
<apply executable=”${rim.blackberry.home}/bin/rapc.exe” parallel=”true”>
<arg value=”-quiet”/>
<arg value=”import=${rim.blackberry.home}/lib/net_rim_api.jar” />
<arg value=”codename=${cod.name}” />
<arg value=”-midlet”/>
<arg value=”jad=${cod.name}.jad”/>
<fileset file=”${cod.name}.jad”/>
<fileset file=”resources.jar” />
<fileset dir=”${src.dir}” />
</apply>
</target>

This article is really good, I just want to make a comment on how to pass the multiple java files to rapc,

I make an ant script like this:

The above script is equivalent to the following command:

rapc.exe -quiet import=net_rim_api.jar codename=MIDletDemo -midlet jad=MIDletDemo.jad resource.jar file1.java file2.java … filen.java

Here I use Ant apply task, http://ant.apache.org/manual/CoreTasks/apply.html

Apply task allow us to pass a fileset, and it will pass each file one by one to the rapc.exe. Please note that here we choose parallel=”true” attribute, it means the command execute only once, which is just what we want rapc.exe do that for us.

For details please refer my blog:
http://code-dojo.blogspot.com/2009/09/using-ant-to-build-blackberry-j2me.html

I’ve seen this soo many times in the past. It’s sad but true that things start to go silly when you load big cod files. I never really found any definitive root cause when I started experiencing this problem. I believe it finally boiled down to our using the wrong version of rapc and other tools. At one point we were using the Sun WTK preverifier version 4.2.2 of RAPC and deploying to version 4.2.1 OS. once we got all of the tools lined up, (version 4.2.1 of RAPC with RAPC preverify for OS 4.2.1 and higher) the problems all melted away. If you’re running RAPC 4.7 and installing on 4.5 then you’ll probably see radically different behavior by making sure your target OS is of an equal or higher version than that of the RAP build tools. In Eclipse you can install different versions of RAPC using the update site. If you’re using the JDE then download the correct version of the JDE (JDE 4.5 or lower for OS 4.5). If you’re installing Jad/Jar files switch to the JDE or the Blackberry Eclipse plugin and you’ll get a far better experience. If none of these is your problem try removing the images/graphics files from the package and downloading them from an HTTP server on 1st run. Also try removing class files that you may not be using. RAPC should do this but I’ve had limited success using the Ant tag to prune out unused class files from my jar before pointing RAPC at the jar.

I’m porting game with many graphics to BB and recently after adding new ones generated .cod file size is over 7,5mb and it won’t install – after loading java program it doesn’t show in downloaded folder, as it used to.

After running simulator with attached debugger I found above message showing while loading file:

Jvm: errors in game.cod
CMM: add game-1(5301)
CMM: add game-2(5434)
CMM: add game-3(5437)

and so on (about 150 of them).

I checked on debugger loading smaller file (5,5mb) and “Jvm: errors..” doesn’t show. Only diffrence beetwen those two versions is size of one included resource file (so far not used in code)

What could those errors be? Is there maybe some limit on individual resource file size? Or maybe limit on .cod file (but from what I read there’s no such limit) ?”

It would be great if you got something on this one, I’m sitting on it for too damn long already..

Be careful with RAPC. you may get your application to compile. You may even manage to get it to run on the device. However, your next hurdle will definitely be either verification errors or the white screen of death. The only way to avoid these problems is to use ONLY the RIM preverifier and also use the correct version of the preverifier/rapc compiler for your target audience. If you target older 8800’s and 8830s that run OS 4.1 then you’ll have another set of hurdles as the older rapc compiler works differently than the newer compiler. You should definitely use the older compiler unless you’re developing for internal company use only as it increases your audience. Most people on Blackberry don’t know how/ain’t got time/lack the patience to upgrade their OS and will likely have the older version installed.

Thank you.

I was able to successfully compile and use a simple app I made using the command line compiler, however I am also having an issue regarding the images.

Is there a tutorial on how to add the images to the project?