Hi guys,

For those who are not following trunk, macruby_deploy got some changes recently:

- The --gem option is added. This option will embed the given RubyGem and its 
dependencies inside the application's bundle.

  ex. $ macruby_deploy --embed --gem nokogiri Foo.app

- The --bs option is added. This option will embed the system BridgeSupport 
files inside the application's bundle. This can be useful if you rely on 
BridgeSupport preview.

  ex. $ macruby_deploy --embed --bs Foo.app

- A bug has been fixed, when macruby_deploy was called with --embed but not 
--compile. The main application executable would not have its load path 
updated. This was a serious problem.

- When using --embed, the 'Current' symlink of the framework is now deleted. 
Apparently this fixes the Mac AppStore validation process which was following 
both '0.9' and 'Current' symlinks and ending with a "Payload not declared in 
Package info" error.

Please give tonight's nightly build a try and let us know if you find something 
wrong :)

Laurent
_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Reply via email to