search

rubymotion-community / sugarcube

Some sugar for your cocoa. RubyMotion helpers.
Other
422 stars 66 forks source link

cgcolor problem breaks release 0.13 #20

Closed dimitrivdp closed 11 years ago

dimitrivdp commented 11 years ago

I just created an empty new motion project with the last version of the gem 0.13

Added

require 'sugarcube'

to my app_delegate.rb

Rake

-> Got this error:

Cannot define method cgcolor' because no Objective-C stub was pre-compiled for types^{CGColor=}@:'. Make sure you properly link with the framework or library that defines this message. (main)> *\ simulator session ended with error: Error Domain=DTiPhoneSimulatorErrorDomain Code=1 "The simulated application quit." UserInfo=0x100506650 {NSLocalizedDescription=The simulated application quit., DTiPhoneSimulatorUnderlyingErrorCodeKey=-1} rake aborted! Command failed with status (1): [DYLD_FRAMEWORK_PATH="/Applications/Xcode.a...]

Uninstalled 0.13 and installed 0.11, works like a charm.

I guess that the merge of issue #18 caused this error. But don't take my word on it, because it's my first day experimenting with rubymotion.

Dimitri.

colinta commented 11 years ago

I got this same message, and then recompiled and it went away :-/

I'll double check it. Thanks!

On Dec 27, 2012, at 4:05 PM, Dimitri Van de Putte notifications@github.com wrote:

I just created an empty new motion project with the last version of the gem 0.13

Added

require 'sugarcube'

to my app_delegate.rb

Rake

-> Got this error:

Cannot define method cgcolor' because no Objective-C stub was pre-compiled for types^{CGColor=}@:'. Make sure you properly link with the framework or library that defines this message. (main)> *\ simulator session ended with error: Error Domain=DTiPhoneSimulatorErrorDomain Code=1 "The simulated application quit." UserInfo=0x100506650 {NSLocalizedDescription=The simulated application quit., DTiPhoneSimulatorUnderlyingErrorCodeKey=-1} rake aborted! Command failed with status (1): [DYLD_FRAMEWORK_PATH="/Applications/Xcode.a...]

Uninstalled 0.13 and installed 0.11, works like a charm.

I guess that the merge of issue #18 caused this error. But don't take my word on it, because it's my first day experimenting with rubymotion.

Dimitri.

\ Reply to this email directly or view it on GitHub.

colinta commented 11 years ago

i was able to get the error message again - can you try it with v0.13.2?

dimitrivdp commented 11 years ago

I removed v0.11 and installed v0.13.2 and now it works like a Charm.

Thanks.

Dimitri.