search for: nsobject

...t to instance 0x7fe5e1d00d50' *** First throw call stack: ( 0 CoreFoundation 0x00007fff8a12c03c __exceptionPreprocess + 172 1 libobjc.A.dylib 0x00007fff8726c76e objc_exception_throw + 43 2 CoreFoundation 0x00007fff8a12f0ad -[NSObject(NSObject) doesNotRecognizeSelector:] + 205 3 CoreFoundation 0x00007fff8a074e24 ___forwarding___ + 1028 4 CoreFoundation 0x00007fff8a074998 _CF_forwarding_prep_0 + 120 5 CoreFoundation 0x00007fff89ffd11d CFStringGetCString + 173...

Hi I''ve built WxWidgets (2.5.4) and wxruby-swig (CVS) from source on OS X (.3). I''ve got something called wx.bundle in lib/ that looks the right sort of size - 2.5MB - but I don''t know what to do with it to install it - no rake install or make install? btw - wx on OS X looks fantastic, esp after seeing a Tk interface inside Aqua this am ... cheers alex

...t to instance 0x7ffd18605360' *** First throw call stack: ( 0 CoreFoundation 0x00007fff8a12c03c __exceptionPreprocess + 172 1 libobjc.A.dylib 0x00007fff8726c76e objc_exception_throw + 43 2 CoreFoundation 0x00007fff8a12f0ad -[NSObject(NSObject) doesNotRecognizeSelector:] + 205 3 CoreFoundation 0x00007fff8a074e24 ___forwarding___ + 1028 4 CoreFoundation 0x00007fff8a074998 _CF_forwarding_prep_0 + 120 5 CoreFoundation 0x00007fff89ffd11d CFStringGetCString + 173...

I managed to build a reduced test case: ================== foo.m ================== #include <Foundation/Foundation.h> @interface BaseNode : NSObject <NSCoding, NSCopying> { } @end @implementation BaseNode @end int main(int argc, char **argv) { return 0; } ========================================== # clang -o foo -arch i386 -framework Foundation foo.m foo.m:8:1: warning: incomplete implementation @implementation BaseNode ^ 1 warning...

...ve using GCC as mentioned). If we have to create a runtime for PS3 and XBox that seems trivial as the functions are very basic in nature. My comments on OpenStep were more meant to point to the fact that we would write our own library; really just throwing all notion of OpenStep away. Instead of NSObject we would create our own base DObject or something along with a DString, DAarry, DSet, DMap, etc. Truthfully this would be our plan anyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library obj...

...ying to send data: #{data}" send_data data end end module DebuggerController def receive_data(data) $DEBUG_OUTPUT.received_controller_data data end def send_command(data) puts "Trying to send data: #{data}" send_data data end end class Controller < OSX::NSObject ib_outlets :commandClient, :commandController, :outputClient, :outputController def connectToApp(sender) puts ''INFO: Connecting'' # This global var is set to the Controller instance, # this way the connection instances can send the data back to the controller.......

After commit 102300, any obj-c software compiled with clang crashes at launch time with the following stack trace. Reverting this specific commit fix the issue. ------------------------------------------------------------------------------------------------ Date/Time: 2010-04-26 10:07:01.630 +0200 OS Version: Mac OS X 10.6.3 (10D573) Report Version: 6 Interval Since Last Report:

...ntioned). If we have to create a runtime for PS3 and XBox that seems trivial as the functions are very basic in nature. >> >> My comments on OpenStep were more meant to point to the fact that we would write our own library; really just throwing all notion of OpenStep away. Instead of NSObject we would create our own base DObject or something along with a DString, DAarry, DSet, DMap, etc. Truthfully this would be our plan anyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library obj...

...CC as mentioned). If we have to create a runtime for PS3 and XBox that seems trivial as the functions are very basic in nature. > > My comments on OpenStep were more meant to point to the fact that we would write our own library; really just throwing all notion of OpenStep away. Instead of NSObject we would create our own base DObject or something along with a DString, DAarry, DSet, DMap, etc. Truthfully this would be our plan anyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library obj...

...ystem.B.dylib 0x9000b1bc mach_msg + 60 2 com.apple.CoreFoundation 0x907dbb78 __CFRunLoopRun + 832 3 com.apple.CoreFoundation 0x907db47c CFRunLoopRunSpecific + 268 4 com.apple.Foundation 0x92939598 -[NSConnection sendInvocation:] + 1468 5 com.apple.Foundation 0x92938034 -[NSObject(NSForwardInvocation) forward::] + 408 6 libobjc.A.dylib 0x90a430b0 _objc_msgForward + 176 7 com.apple.Foundation 0x9293839c -[NSDistantObject methodSignatureForSelector:] + 268 8 com.apple.Foundation 0x92937f04 -[NSObject(NSForwardInvocation) forward::] + 104 9 libobjc.A...

...ve to create a runtime > for PS3 and XBox that seems trivial as the functions are very basic > in nature. > > My comments on OpenStep were more meant to point to the fact that we > would write our own library; really just throwing all notion of > OpenStep away. Instead of NSObject we would create our own base > DObject or something along with a DString, DAarry, DSet, DMap, etc. > Truthfully this would be our plan anyway because we want to follow > the lead of OSX and provide these objects "toll free bridged"... > meaning we would implement them...

...d XBox that seems trivial as the functions are >>> very basic in nature. >>> >>> My comments on OpenStep were more meant to point to the fact that >>> we would write our own library; really just throwing all notion of >>> OpenStep away. Instead of NSObject we would create our own base >>> DObject or something along with a DString, DAarry, DSet, DMap, >>> etc. Truthfully this would be our plan anyway because we want to >>> follow the lead of OSX and provide these objects "toll free >>> bridged"......

...vial as the functions are >>>> very basic in nature. >>>> >>>> My comments on OpenStep were more meant to point to the fact that >>>> we would write our own library; really just throwing all notion of >>>> OpenStep away. Instead of NSObject we would create our own base >>>> DObject or something along with a DString, DAarry, DSet, DMap, >>>> etc. Truthfully this would be our plan anyway because we want to >>>> follow the lead of OSX and provide these objects "toll free >>>>...

...stem/Library/Frameworks/Cocoa.framework/Headers/Cocoa.h:12, from src/Mac.cpp:1596: /System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:60: error: stray ''@'' in program In file included from /System/Library/Frameworks/Foundation.framework/Headers/NSObject.h:6, from /System/Library/Frameworks/Foundation.framework/Headers/NSAffineTransform.h:8, from /System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:13, ------------------------------------------------------------------------ NSObjCRuntime.h, around...

On 12 January 2011 23:38, Rob Nikander <rob.nikander at gmail.com> wrote: > I have to pass something from the LinkageTypes enum to the > constructor.  I tried others, like GlobalVariable::InternalLinkage, > which dumps as "internal global" but the error was the same. To be honest, your IR is a bit odd. I'm not a JIT expert, but here are a few things that will help you

...0x9000a5c7 mach_msg_trap + 7 1 com.apple.CoreFoundation 0x9082369a CFRunLoopRunSpecific + 2014 2 com.apple.CoreFoundation 0x90822eb5 CFRunLoopRunInMode + 61 3 com.apple.Foundation 0x92778559 -[NSConnection sendInvocation:] + 2126 4 com.apple.Foundation 0x9272f324 -[NSObject(NSForwardInvocation) forward::] + 469 5 libobjc.A.dylib 0x90a51ba1 _objc_msgForward + 49 6 com.apple.Foundation 0x9277798b -[NSDistantObject methodSignatureForSelector:] + 211 7 com.apple.Foundation 0x9272f1b0 -[NSObject(NSForwardInvocation) forward::] + 97 8...

.... If we have to create a runtime for PS3 and XBox that seems trivial as the functions are very basic in nature. >>> >>> My comments on OpenStep were more meant to point to the fact that we would write our own library; really just throwing all notion of OpenStep away. Instead of NSObject we would create our own base DObject or something along with a DString, DAarry, DSet, DMap, etc. Truthfully this would be our plan anyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library obj...

On Wed, Jan 12, 2011 at 6:08 PM, Renato Golin <rengolin at systemcall.org> wrote: > On 12 January 2011 22:28, Rob Nikander <rob.nikander at gmail.com> wrote: >> @x = external global %0* > > Hi Rob, > > Try removing the 'extern', as it implies the variable storage is > elsewhere (ie. another object file). > I have to pass something from the

...9000affc mach_msg + 60 2 com.apple.CoreFoundation 0x907e3b78 __CFRunLoopRun + 832 3 com.apple.CoreFoundation 0x907e347c CFRunLoopRunSpecific + 268 4 com.apple.Foundation 0x9296b598 -[NSConnection sendInvocation:] + 1468 5 com.apple.Foundation 0x9296a034 -[NSObject(NSForwardInvocation) forward::] + 408 6 libobjc.A.dylib 0x90a4b0b0 _objc_msgForward + 176 7 com.apple.Foundation 0x9296a39c -[NSDistantObject methodSignatureForSelector:] + 268 8 com.apple.Foundation 0x92969f04 -[NSObject(NSForwardInvocation) forward::] +...

llvm can output C code, but that target has bitrotted severely over the last few months and nobody seems to be interested in fixing it. You may need to do some work there. Alternatively you could implement the PPC ABI that you need. There are several examples of supporting multiple ABIs on the same hardware, x86 being the most obvious. A lot of simple stuff will probably Just Work with the