Some issues running `mulberry serve` on latest code from master

34 views
Skip to first unread message

favrik

unread,
Aug 28, 2012, 4:42:48 AM8/28/12
to toura-m...@googlegroups.com
Hello!,

I finally decided to give Mulberry a try. :)

I'm installing from a git clone of master branch on Linux Mint (based on Ubuntu 11.X).  Everything goes mostly good (have to run `source ./install.sh` twice because rvm is not loaded on first run).

However, after that, running `mulberry serve` on the kitchensink app gives me the following output:

favio@home:~/sources/mulberry/demos/kitchensink [master]$ mulberry serve
INFO: === gather ===
INFO: === build ===
/home/favio/sources/mulberry/cli/env.rb:4: Use RbConfig instead of obsolete and deprecated Config.
INFO: Dojo is installed. It's all good.
INFO: --> javascript: accepted
Building the JavaScript -- this can take a while, be patient!
sh: ./build.sh: not found
/home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1371:in `initialize': No such file or directory - /home/favio/sources/mulberry/js_builds/dev/vendor/haml.js (Errno::ENOENT)
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1371:in `open'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1371:in `block in copy_file'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1370:in `open'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1370:in `copy_file'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:477:in `copy_file'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:396:in `block in cp'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1515:in `block in fu_each_src_dest'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1531:in `fu_each_src_dest0'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1513:in `fu_each_src_dest'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:395:in `cp'
from /home/favio/sources/mulberry/builder/js.rb:191:in `unminify_haml'
from /home/favio/sources/mulberry/builder/js.rb:93:in `build'
from /home/favio/sources/mulberry/builder.rb:159:in `block in do_step'
from /home/favio/sources/mulberry/builder.rb:155:in `each'
from /home/favio/sources/mulberry/builder.rb:155:in `do_step'
from /home/favio/sources/mulberry/builder.rb:150:in `block in do_steps'
from /home/favio/sources/mulberry/builder.rb:145:in `each'
from /home/favio/sources/mulberry/builder.rb:145:in `do_steps'
from /home/favio/sources/mulberry/builder.rb:91:in `build'
from /home/favio/sources/mulberry/cli/mulberry.rb:257:in `serve'
from /home/favio/sources/mulberry/cli/bin/commands/serve.rb:26:in `initialize'
from /home/favio/sources/mulberry/cli/bin/mulberry.rb:28:in `new'
from /home/favio/sources/mulberry/cli/bin/mulberry.rb:28:in `run'
from /home/favio/sources/mulberry/cli/bin/mulberry.rb:46:in `<main>'

This is because `unminify_haml' in builder/js.rb, tries to remove the file "js_builds/dev/vendor/haml.js" which doesn't exist. 

Any ideas?

Thanks!

Chris Barrett

unread,
Aug 28, 2012, 2:07:37 PM8/28/12
to toura-m...@googlegroups.com
Hi Favrik,
I am unsure of why haml.js is missing for you. The one thing to note is that we're actually in the process of removing install.sh, as the external dependencies are constantly changing and it requires too much maintenance to be useful. We're reviewing the install instructions right now which will replace the install script. 

One thing to try is to make sure you're up to date with the master branch. Next, enter the command 'mulberry build' into the console when you're in the kitchensink directory.
Let us know how that goes.
-Chris

Chris Barrett

unread,
Aug 28, 2012, 2:08:15 PM8/28/12
to toura-m...@googlegroups.com
Oh and then run 'mulberry serve'.
:)

favrik

unread,
Aug 28, 2012, 3:49:40 PM8/28/12
to toura-m...@googlegroups.com
Hi, thanks for your replies!,

yeah, not sure either, I mean haml.js it's not missing from the /app/vendor dir, but the js_build directory doesn't exist.

I ran `mulberry build` (after running git pull) and here's the output:  (it's the same error in disguise!)

favio@home:~/sources/mulberry/demos/kitchensink [master]$ mulberry build
INFO: === gather ===
INFO: --> assets: accepted
INFO: assets: completed
INFO: --> data: accepted
INFO: data: completed
INFO: --> page_defs: accepted
INFO: page_defs: completed
INFO: === build ===
/home/favio/sources/mulberry/cli/env.rb:4: Use RbConfig instead of obsolete and deprecated Config.
INFO: Dojo is installed. It's all good.
INFO: --> javascript: accepted
Building the JavaScript -- this can take a while, be patient!
sh: ./build.sh: not found
/home/favio/sources/mulberry/js_builds
mulberry
/home/favio/sources/mulberry/app
/home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1371:in `initialize': No such file or directory - /home/favio/sources/mulberry/js_builds/mulberry/vendor/haml.js (Errno::ENOENT)
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1371:in `open'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1371:in `block in copy_file'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1370:in `open'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1370:in `copy_file'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:477:in `copy_file'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:396:in `block in cp'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1515:in `block in fu_each_src_dest'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1531:in `fu_each_src_dest0'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:1513:in `fu_each_src_dest'
from /home/favio/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/fileutils.rb:395:in `cp'
from /home/favio/sources/mulberry/builder/js.rb:194:in `unminify_haml'
from /home/favio/sources/mulberry/builder/js.rb:93:in `build'
from /home/favio/sources/mulberry/builder.rb:159:in `block in do_step'
from /home/favio/sources/mulberry/builder.rb:155:in `each'
from /home/favio/sources/mulberry/builder.rb:155:in `do_step'
from /home/favio/sources/mulberry/builder.rb:150:in `block in do_steps'
from /home/favio/sources/mulberry/builder.rb:145:in `each'
from /home/favio/sources/mulberry/builder.rb:145:in `do_steps'
from /home/favio/sources/mulberry/builder.rb:91:in `build'
from /home/favio/sources/mulberry/cli/mulberry.rb:356:in `block (2 levels) in build'
from /home/favio/sources/mulberry/cli/mulberry.rb:349:in `each'
from /home/favio/sources/mulberry/cli/mulberry.rb:349:in `block in build'
from /home/favio/sources/mulberry/cli/mulberry.rb:348:in `each'
from /home/favio/sources/mulberry/cli/mulberry.rb:348:in `build'
from /home/favio/sources/mulberry/cli/mulberry.rb:294:in `device_build'
from /home/favio/sources/mulberry/cli/bin/commands/build.rb:40:in `initialize'
from /home/favio/sources/mulberry/cli/bin/mulberry.rb:28:in `new'
from /home/favio/sources/mulberry/cli/bin/mulberry.rb:28:in `run'
from /home/favio/sources/mulberry/cli/bin/mulberry.rb:46:in `<main>'

So it first tries to run a build.sh script which does not exist too, then stops at `unminify_haml`.  I checked the other branches and the most recent tags, but it seems this js_build directory has not been present for a while.

I'll check the mac install script and see if there are some hints there.

I really want to use Mulberry rather than just phonegap. xD

Thanks!.
Favio

favrik

unread,
Aug 28, 2012, 8:11:44 PM8/28/12
to toura-m...@googlegroups.com
Tested by manually creating the directories:  

js_builds/mulberry, js_builds/dev and sub-directories vendor and dojo.

The `serve` command runs fine, but the application fails with javascript errors (dojo is not defined, etc.).  Also, tried with the develop branch.  

Initially thought this could be related to a partially installed rbenv (had rbenv and rvm at the same time!), but then re-installed without it and kept getting same errors.

I'm thinking this has to do with that missing `build.sh` script, I reviewed some of the code and it assumes there will be some kind of dir structure (but I'm a noob at ruby).

Anyway, the project is really, really awesome!  Can't wait to create something with it.
Reply all
Reply to author
Forward
0 new messages