Observations

All coins have three sides: Heads, tails, and edge.
~-Robert Kiyosaki

Find a need and fulfill it. Successful businesses are founded on the needs of people.
~A. G. Gaston

It always looks impossible until it's done.
~Nelson Mandela

If you’re creating a company, it’s important to limit the number of miracles in series. Start with something that’s the most doable and then expand from there.
~Elon Musk

Concentrate all your thoughts upon the work at hand. The sun's rays do not burn until brought to a focus.
~Alexander Graham Bell

God, make me so uncomfortable that I will do the very thing I fear.
~Ruby Dee

The most difficult thing is the decision to act. The rest is merely tenacity.
~Amelia Earhart

Software being "Done" is like lawn being "Mowed".
~Jim Benson

A person with a new idea is a crank until the idea succeeds.
~Mark Twain

Everybody told me no at first, including my wife. I turned the nos into yeses and the disadvantages into advantages.
~John H. Johnson

The best way to make dreams come true is to wake up.
~Mae C. Jemison

ROI Clear

ROIClear

When in Doubt, Rake Clean

10 Apr 2014

Earlier today, I upgraded from RubyMotion v 2.24 to v 2.26. Immediately after the upgrade, I attempted to run a RubyMotion app that I’m working on. The result?

$ rake

     Build ./build/iPhoneSimulator-7.1-Development
   Compile ./app/app_delegate.rb
   Compile ./app/views/score_label.rb
   Compile ./app/views/paddle_view.rb
      Link ./build/iPhoneSimulator-7.1-Development/pong-rm4.app/pong-rm4
Undefined symbols for architecture i386:

...

clang: error: linker command failed with exit code 1 (use -v to see invocation)
rake aborted!

$  

What happened? It just ran a few minutes ago, right before the upgrade! Was RubyMotion broken? Was it time to reach out to the Twitterverse or Stack Overflow for assistance?

Not yet.

Cooler Heads

Every time RubyMotion build an app, it stores the results in the ./build directory. Since I had just done an upgrade, it was possible that remnants from a v 2.24 build were interfering with my new v 2.26 build. The solution?

$ rake clean

    Delete ./build

$  

And now the app runs fine. Crisis averted. Back to work!

Featured Articles

Observations

When in Doubt, Rake Clean

Cooler Heads

Comments