[jruby-user] [Q] limelight + rawr for .exe

Chuck_Remes · 13 October 2011 17:40

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:

gist.github.com

https://gist.github.com/chuckremes/1284895

build_configuration.rb

configuration do |c|
	# The name for your resulting application file (e.g., if the project_name is 'foo' then you'll get foo.jar, foo.exe, etc.)
	# default value: "test"
	#
	c.project_name = "test"

	# Undocumented option 'output_dir'
	# default value: "package"
	#
	c.output_dir = "package"

This file has been truncated. show original

output.txt

Mac-Pro:test cremes$ rake rawr:jar
Loaded /Users/cremes/.rvm/gems/jruby-1.6.3/gems/rawr-1.6.0/lib/rawr/core_ext.rb
javac -target 1.6 -cp lib/java/jruby-complete.jar:src:lib/ruby -sourcepath src:lib/ruby -d package/classes/java src/org/rubyforge/rawr/Main.java
Compile src/foo.rb into package/classes/ruby/foo.class
   compile_dirs has src_dirs = ["src", "lib/ruby"]
   glob_ruby_files has directory 'src' glob ["src/foo.rb"]
files for src: 1
   glob_ruby_files has directory 'lib/ruby' glob []
files for lib/ruby: 0
   ruby_globs.each has glob_data = #<OpenStruct files=["foo.rb"], directory="src">

This file has been truncated. show original

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] http://spin.atomicobject.com/2008/07/02/rolling-a-jruby-desktop-application/

[2] https://gist.github.com/1284895

···

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

Chuck Remes 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/<ruby src>
~/proj/vendor/<unpacked gems>

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.