From: James Britt Date: 2009-12-05T02:08:17+09:00 Subject: Re: Best way to distribute an app David Masover wrote: > On Monday 30 November 2009 09:03:28 am Omar Campos wrote: >>> This is something that I intensely dislike, personally. It's the >>> antithesis of >>> all that is good and pure about package managers, but it may fit your >>> needs. >> Duly noted. I will not bake my gems :). I will use rawr instead. > > Well, rawr has exactly the same problems -- as I understand it, the only > difference is that it combines your apps and your gems into one giant jar. I may not; it depends on what you set in the config file. But typically, yes, unpacked gems get bundled up into a common jar file. > > In other words, pay no attention to my rambling. > > The main thing I like about rawr is that if you're going that route anyway, > it's a nice cross-platform solution. It builds a Ruby app that's as portable > as any Java app, but gives you native installers for all of them. It also has > an awesome logo. :) > >> What about ExeRb and RubyScript2Exe? Are those any good? > > No idea, that might be answered in the FAQ someone else mentioned. One difference is that rawr will compile your Ruby code into Java classes in such a way to provide very robust code obfuscation, if you need that. I believe the other options do nothing to hide the Ruby code, making it available for people to read/copy. -- James Britt www.jamesbritt.com - Playing with Better Toys www.ruby-doc.org - Ruby Help & Documentation www.rubystuff.com - The Ruby Store for Ruby Stuff www.neurogami.com - Smart application development