[Q] limelight + rawr for .exe

I have a limelight [1] application that I would like to package up with
rawr to make a double-clickable Windows application. The problem I am
having is that limelight and rawr are a bit at odds in two respects.

  1. project directory layout

  2. launching the code

For #1, rawr wants the project source code laid out like:

~/proj/src/
~/proj/vendor/

and limelight wants its code laid out like:

~/proj/

For #2, limelight applications are opened by executing a ‘limelight’
script in the jruby ~/bin directory.

e.g. % limelight open project_name

Has anyone figured out how to reconcile these differences to produce a
rawr application? Pointers and suggestions are welcome!

cr

[1] http://limelight.8thlight.com
[2] GitHub - rawr/rawr: Packaging and deployment for standalone JRuby apps

Chuck R. wrote:

I have a limelight [1] application that I would like to package up with rawr to
make a double-clickable Windows application. The problem I am having is that
limelight and rawr are a bit at odds in two respects.

  1. project directory layout

  2. launching the code

For #1, rawr wants the project source code laid out like:

~/proj/src/
~/proj/vendor/

No it doesn’t. There’s nothing in rawr about loading gems (or anything)
from a ‘vendor’ dir. (The only place the source code references the
word ‘vendor’ is in the currently non-working jnlp code.)

Look at how Monkeybars apps are bundled.

It’s pretty much up to you and how you define things in
build_configuration.rb to define where things live.

There are some defaults (such as lib/ruby and lib/java) but you can
change these.

James B.

On Oct 12, 2011, at 8:57 PM, James B. wrote:

Look at how Monkeybars apps are bundled.

It’s pretty much up to you and how you define things in build_configuration.rb
to define where things live.

There are some defaults (such as lib/ruby and lib/java) but you can change
these.

You are right. I was mixing up some things I read on another web page
[1] regarding building double-clickable binaries for JRuby.

I cloned the rawr repository and tried doing a simple “hello world”
packaging, but it doesn’t work. I always get a noclassdeffounderror:

I created a simple project with one file named “foo.rb” and put it in
the src/ directory. I modified the build_configuration.rb file [2] and
created a jar. Running that jar fails.

A simple example showing how to get this to work would be much
appreciated.

cr

[1]

[2] build_configuration.rb · GitHub

Try using limelight pack feature. This bundles the production into a
.llp
file that’s double-clickable assuming you have the Limelight app
installed.

$ limelight pack my_production_dir

Then double click the .llp it generates.

Chuck R. wrote:

On Oct 12, 2011, at 8:57 PM, James B. wrote:

There are some defaults (such as lib/ruby and lib/java) but you can change
these.

You are right. I was mixing up some things I read on another web page [1]
regarding building double-clickable binaries for JRuby.

I cloned the rawr repository and tried doing a simple “hello world” packaging,
but it doesn’t work. I always get a noclassdeffounderror:

build_configuration.rb · GitHub

What version of jruby are you using? There was a report of 1.6.4 not
getting along with rawr that I need to look at.

I created a simple project with one file named “foo.rb” and put it in the src/
directory. I modified the build_configuration.rb file [2] and created a jar.
Running that jar fails.

A simple example showing how to get this to work would be much appreciated.

OK.

Also, it might be better to continue this discussion on the rawr mailing
list.

http://groups.google.com/group/rawr-lib

Thanks,

James