date:20100527

Re: [MacRuby-devel] [MacRuby] #713: Growl is broken on MacRuby 0.6

2010-05-27 Thread MacRuby

#713: Growl is broken on MacRuby 0.6
--+-
 Reporter:  ylp...@…  |   Owner:  lsansone...@…
 Type:  defect|  Status:  new  
 Priority:  blocker   |   Milestone:  MacRuby 0.6  
Component:  MacRuby   |Keywords:  growl
--+-

Comment(by ylp...@…):

 Thanks, Jakub! Growl indeed works when used via the Growl.framework:
 {{{
 # Requires the Growl framework
 (http://growl.googlecode.com/files/Growl-1.2.1-Framework.tbz)
 # to be present on the load path.
 framework "Growl.framework"

 def registrationDictionaryForGrowl
   { TicketVersion: 1,  AllNotifications: ["hello"],
 DefaultNotifications: ["hello"],  ApplicationId: 'growl_test'}
 end

 GrowlApplicationBridge.setGrowlDelegate(self)
 GrowlApplicationBridge.notifyWithTitle("hello",
description: "hello",
notificationName: "hello",
iconData: nil,
priority: 0,
isSticky: false,
clickContext: nil)
 }}}

 However, the demos are still broken.

-- 
Ticket URL: 
MacRuby 

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

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Louis-Philippe

So far, I got my c++ sdk in a framework (without objc wrapper) I can call it
from objective-c...
but macruby is not happy with it, importing it with 'framework
"./MYSDK.framework"', I get:

RuntimeError: framework at path `./MYSDK.framework' cannot be loaded: Error
Domain=NSCocoaErrorDomain Code=3585 UserInfo=0x2002b5080 "The bundle
“MYSDK.framework” couldn’t be loaded because it doesn’t contain a version
for the current architecture."
(dlopen_preflight(/PATH/MYSDK.framework/MYSDK): no suitable image found.
 Did find:
/PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
from /PATH/(irb):2:in `'

2010/5/26 Thibault Martin-Lagardette 

> Hi!
>
> That's exactly what I was going to recommend.
> MacRuby is able to interact with Obj-C, so you can write an Obj-C++ wrapper
> (.mm files) around your SDK, and then use it with MacRuby :-)
>
> Any of you two, if you manage / managed to do it, please do not hesitate
> sharing the recipe to the world :-).
>
> --
> Thibault Martin-Lagardette
>
>
>
> On May 26, 2010, at 11:31, Gregoire LEJEUNE wrote:
>
> > I do it with a C lib (but it must be the same with C++). First I
> > create a ObjC class over my C lib. Then i can use my ObjC class within
> > MacRuby.
> >
> > Greg
> >
> > 2010/5/26 Louis-Philippe :
> >> Hi folks,
> >> I need to work with a c++ sdk in my code.
> >> Is this possible within macruby?
> >> I tried loading the files all sorts of way and making a bundle with it
> and
> >> got no luck at this point...
> >> thanks!
> >> L-P
> >> ___
> >> MacRuby-devel mailing list
> >> MacRuby-devel@lists.macosforge.org
> >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> >>
> >>
> > ___
> > MacRuby-devel mailing list
> > MacRuby-devel@lists.macosforge.org
> > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Joel Reymont

Louis-Philippe,

On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:

> Did find:
>   /PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
>   from /PATH/(irb):2:in `'

Can you paste the output from the following?

uname -a

file ATH/MYSDK.framework/MYSDK

file `which macruby`

Thanks, Joel

---
http://twitter.com/wagerlabs

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

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Louis-Philippe

uname -a:
Darwin modullpmacbook.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26
11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386

./MYSDK (from the MYSDK.framework)
-bash: ./R3DSDK: No such file or directory

which macruby:
/usr/local/bin/macruby

by the way, I tried it in a MacRuby cocoa app inside of xcode, but the error
sample I pasted above is from a macirb execution


2010/5/27 Joel Reymont 

> Louis-Philippe,
>
> On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:
>
> > Did find:
> >   /PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
> >   from /PATH/(irb):2:in `'
>
> Can you paste the output from the following?
>
> uname -a
>
> file ATH/MYSDK.framework/MYSDK
>
> file `which macruby`
>
>Thanks, Joel
>
> ---
> http://twitter.com/wagerlabs
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Joel Reymont


On May 27, 2010, at 3:48 PM, Louis-Philippe wrote:

> ./MYSDK (from the MYSDK.framework)
> -bash: ./R3DSDK: No such file or directory

file PATH/MYSDK.framework/MYSDK

Run the file command on MYSDK

> which macruby:
> /usr/local/bin/macruby

Not `which macruby` but run the file command on macruby itself, i.e.

file `which macruby`

---
http://twitter.com/wagerlabs

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

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Louis-Philippe

sorry, the second one really is:

./MYSDK (from the MYSDK.framework)
-bash: ./MYSDK: cannot execute binary file

2010/5/27 Louis-Philippe 

> uname -a:
> Darwin modullpmacbook.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26
> 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
>
> ./MYSDK (from the MYSDK.framework)
> -bash: ./R3DSDK: No such file or directory
>
> which macruby:
> /usr/local/bin/macruby
>
> by the way, I tried it in a MacRuby cocoa app inside of xcode, but the
> error sample I pasted above is from a macirb execution
>
>
> 2010/5/27 Joel Reymont 
>
> Louis-Philippe,
>>
>> On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:
>>
>> > Did find:
>> >   /PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
>> >   from /PATH/(irb):2:in `'
>>
>> Can you paste the output from the following?
>>
>> uname -a
>>
>> file ATH/MYSDK.framework/MYSDK
>>
>> file `which macruby`
>>
>>Thanks, Joel
>>
>> ---
>> http://twitter.com/wagerlabs
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Louis-Philippe

file PATH/MYSDK.framework/MYSDK
./MYSDK: Mach-O dynamically linked shared library i386

file `which macruby`:
/usr/local/bin/macruby: Mach-O universal binary with 2 architectures
/usr/local/bin/macruby (for architecture i386): Mach-O executable i386
/usr/local/bin/macruby (for architecture x86_64): Mach-O 64-bit executable
x86_64


2010/5/27 Louis-Philippe 

> sorry, the second one really is:
>
> ./MYSDK (from the MYSDK.framework)
> -bash: ./MYSDK: cannot execute binary file
>
> 2010/5/27 Louis-Philippe 
>
> uname -a:
>> Darwin modullpmacbook.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb
>> 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
>>
>> ./MYSDK (from the MYSDK.framework)
>> -bash: ./R3DSDK: No such file or directory
>>
>> which macruby:
>> /usr/local/bin/macruby
>>
>> by the way, I tried it in a MacRuby cocoa app inside of xcode, but the
>> error sample I pasted above is from a macirb execution
>>
>>
>> 2010/5/27 Joel Reymont 
>>
>> Louis-Philippe,
>>>
>>> On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:
>>>
>>> > Did find:
>>> >   /PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
>>> >   from /PATH/(irb):2:in `'
>>>
>>> Can you paste the output from the following?
>>>
>>> uname -a
>>>
>>> file ATH/MYSDK.framework/MYSDK
>>>
>>> file `which macruby`
>>>
>>>Thanks, Joel
>>>
>>> ---
>>> http://twitter.com/wagerlabs
>>>
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>
>>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Jordan Breeding

Try building your framework as both i386 and x86_64.

On May 27, 2010, at 10:00, Louis-Philippe wrote:

> file PATH/MYSDK.framework/MYSDK
> ./MYSDK: Mach-O dynamically linked shared library i386
> 
> file `which macruby`:
> /usr/local/bin/macruby: Mach-O universal binary with 2 architectures
> /usr/local/bin/macruby (for architecture i386):   Mach-O executable i386
> /usr/local/bin/macruby (for architecture x86_64): Mach-O 64-bit 
> executable x86_64
> 
> 
> 2010/5/27 Louis-Philippe 
> sorry, the second one really is:
> 
> ./MYSDK (from the MYSDK.framework)
> -bash: ./MYSDK: cannot execute binary file
> 
> 2010/5/27 Louis-Philippe 
> 
> uname -a:
> Darwin modullpmacbook.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26 
> 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
> 
> ./MYSDK (from the MYSDK.framework)
> -bash: ./R3DSDK: No such file or directory
> 
> which macruby:
> /usr/local/bin/macruby
> 
> by the way, I tried it in a MacRuby cocoa app inside of xcode, but the error 
> sample I pasted above is from a macirb execution
> 
> 
> 2010/5/27 Joel Reymont 
> 
> Louis-Philippe,
> 
> On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:
> 
> > Did find:
> >   /PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
> >   from /PATH/(irb):2:in `'
> 
> Can you paste the output from the following?
> 
> uname -a
> 
> file ATH/MYSDK.framework/MYSDK
> 
> file `which macruby`
> 
>Thanks, Joel
> 
> ---
> http://twitter.com/wagerlabs
> 
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> 
> 
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel



smime.p7s
Description: S/MIME cryptographic signature
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Louis-Philippe

it only builds for i386...
getting errors when trying to build for x86_64...
thats why I tried as I tested to build only for i386...

2010/5/27 Jordan Breeding 

> Try building your framework as both i386 and x86_64.
>
> On May 27, 2010, at 10:00, Louis-Philippe wrote:
>
> file PATH/MYSDK.framework/MYSDK
> ./MYSDK: Mach-O dynamically linked shared library i386
>
> file `which macruby`:
> /usr/local/bin/macruby: Mach-O universal binary with 2 architectures
> /usr/local/bin/macruby (for architecture i386): Mach-O executable i386
> /usr/local/bin/macruby (for architecture x86_64): Mach-O 64-bit executable
> x86_64
>
>
> 2010/5/27 Louis-Philippe 
>
>> sorry, the second one really is:
>>
>> ./MYSDK (from the MYSDK.framework)
>> -bash: ./MYSDK: cannot execute binary file
>>
>> 2010/5/27 Louis-Philippe 
>>
>> uname -a:
>>> Darwin modullpmacbook.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb
>>> 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
>>>
>>> ./MYSDK (from the MYSDK.framework)
>>> -bash: ./R3DSDK: No such file or directory
>>>
>>> which macruby:
>>> /usr/local/bin/macruby
>>>
>>> by the way, I tried it in a MacRuby cocoa app inside of xcode, but the
>>> error sample I pasted above is from a macirb execution
>>>
>>>
>>> 2010/5/27 Joel Reymont 
>>>
>>> Louis-Philippe,

 On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:

 > Did find:
 >   /PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
 >   from /PATH/(irb):2:in `'

 Can you paste the output from the following?

 uname -a

 file ATH/MYSDK.framework/MYSDK

 file `which macruby`

Thanks, Joel

 ---
 http://twitter.com/wagerlabs

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

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

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Jordan Breeding

Then you could force macruby/macirb to run as i386:

`arch -arch i386 macirb`

On May 27, 2010, at 10:13, Louis-Philippe wrote:

> it only builds for i386...
> getting errors when trying to build for x86_64...
> thats why I tried as I tested to build only for i386...
> 
> 2010/5/27 Jordan Breeding 
> Try building your framework as both i386 and x86_64.
> 
> On May 27, 2010, at 10:00, Louis-Philippe wrote:
> 
>> file PATH/MYSDK.framework/MYSDK
>> ./MYSDK: Mach-O dynamically linked shared library i386
>> 
>> file `which macruby`:
>> /usr/local/bin/macruby: Mach-O universal binary with 2 architectures
>> /usr/local/bin/macruby (for architecture i386):  Mach-O executable i386
>> /usr/local/bin/macruby (for architecture x86_64):Mach-O 64-bit 
>> executable x86_64
>> 
>> 
>> 2010/5/27 Louis-Philippe 
>> sorry, the second one really is:
>> 
>> ./MYSDK (from the MYSDK.framework)
>> -bash: ./MYSDK: cannot execute binary file
>> 
>> 2010/5/27 Louis-Philippe 
>> 
>> uname -a:
>> Darwin modullpmacbook.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26 
>> 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
>> 
>> ./MYSDK (from the MYSDK.framework)
>> -bash: ./R3DSDK: No such file or directory
>> 
>> which macruby:
>> /usr/local/bin/macruby
>> 
>> by the way, I tried it in a MacRuby cocoa app inside of xcode, but the error 
>> sample I pasted above is from a macirb execution
>> 
>> 
>> 2010/5/27 Joel Reymont 
>> 
>> Louis-Philippe,
>> 
>> On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:
>> 
>> > Did find:
>> >   /PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
>> >   from /PATH/(irb):2:in `'
>> 
>> Can you paste the output from the following?
>> 
>> uname -a
>> 
>> file ATH/MYSDK.framework/MYSDK
>> 
>> file `which macruby`
>> 
>>Thanks, Joel
>> 
>> ---
>> http://twitter.com/wagerlabs
>> 
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>> 
>> 
>> 
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> 
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> 
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel



smime.p7s
Description: S/MIME cryptographic signature
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Louis-Philippe

Thanks!
ok... I sorted some of the issues out... I was able to make a x86_64
framework out of the SDK by including the proper exports symbols (using nm
with the -arch flag).

so now it loads fine with the framework method...
but I cant access the c++ namespace:
"NameError: uninitialized constant MYSDK"

2010/5/27 Jordan Breeding 

> Then you could force macruby/macirb to run as i386:
>
> `arch -arch i386 macirb`
>
> On May 27, 2010, at 10:13, Louis-Philippe wrote:
>
> it only builds for i386...
> getting errors when trying to build for x86_64...
> thats why I tried as I tested to build only for i386...
>
> 2010/5/27 Jordan Breeding 
>
>> Try building your framework as both i386 and x86_64.
>>
>> On May 27, 2010, at 10:00, Louis-Philippe wrote:
>>
>> file PATH/MYSDK.framework/MYSDK
>> ./MYSDK: Mach-O dynamically linked shared library i386
>>
>> file `which macruby`:
>> /usr/local/bin/macruby: Mach-O universal binary with 2 architectures
>> /usr/local/bin/macruby (for architecture i386): Mach-O executable i386
>> /usr/local/bin/macruby (for architecture x86_64): Mach-O 64-bit
>> executable x86_64
>>
>>
>> 2010/5/27 Louis-Philippe 
>>
>>> sorry, the second one really is:
>>>
>>> ./MYSDK (from the MYSDK.framework)
>>> -bash: ./MYSDK: cannot execute binary file
>>>
>>> 2010/5/27 Louis-Philippe 
>>>
>>> uname -a:
 Darwin modullpmacbook.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb
 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386

 ./MYSDK (from the MYSDK.framework)
 -bash: ./R3DSDK: No such file or directory

 which macruby:
 /usr/local/bin/macruby

 by the way, I tried it in a MacRuby cocoa app inside of xcode, but the
 error sample I pasted above is from a macirb execution


 2010/5/27 Joel Reymont 

 Louis-Philippe,
>
> On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:
>
> > Did find:
> >   /PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
> >   from /PATH/(irb):2:in `'
>
> Can you paste the output from the following?
>
> uname -a
>
> file ATH/MYSDK.framework/MYSDK
>
> file `which macruby`
>
>Thanks, Joel
>
> ---
> http://twitter.com/wagerlabs
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>


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

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Jordan Breeding

You might have to make a bridge support file and include it in your framework.

Something like this (although this is specific to running inside my Xcode 
project build):

printf "Building BridgeSupport files...\n\n"

BRIDGE_SUPPORT_DIR="Resources/BridgeSupport"
BRIDGE_SUPPORT_FILE="${BRIDGE_SUPPORT_DIR}/${TARGET_NAME}.bridgesupport"

if [[ "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${TARGET_NAME}" -nt 
"${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_FILE}" ]]; then
  if [[ ! -d "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_DIR}" ]]; 
then
mkdir -p "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_DIR}"
  fi
  gen_bridge_metadata --64-bit --framework 
"${TARGET_BUILD_DIR}/${WRAPPER_NAME}" -o 
"${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_FILE}"
fi

On May 27, 2010, at 10:31, Louis-Philippe wrote:

> Thanks!
> ok... I sorted some of the issues out... I was able to make a x86_64 
> framework out of the SDK by including the proper exports symbols (using nm 
> with the -arch flag).
> 
> so now it loads fine with the framework method...
> but I cant access the c++ namespace:
> "NameError: uninitialized constant MYSDK"
> 
> 2010/5/27 Jordan Breeding 
> Then you could force macruby/macirb to run as i386:
> 
> `arch -arch i386 macirb`
> 
> On May 27, 2010, at 10:13, Louis-Philippe wrote:
> 
>> it only builds for i386...
>> getting errors when trying to build for x86_64...
>> thats why I tried as I tested to build only for i386...
>> 
>> 2010/5/27 Jordan Breeding 
>> Try building your framework as both i386 and x86_64.
>> 
>> On May 27, 2010, at 10:00, Louis-Philippe wrote:
>> 
>>> file PATH/MYSDK.framework/MYSDK
>>> ./MYSDK: Mach-O dynamically linked shared library i386
>>> 
>>> file `which macruby`:
>>> /usr/local/bin/macruby: Mach-O universal binary with 2 architectures
>>> /usr/local/bin/macruby (for architecture i386): Mach-O executable i386
>>> /usr/local/bin/macruby (for architecture x86_64):   Mach-O 64-bit 
>>> executable x86_64
>>> 
>>> 
>>> 2010/5/27 Louis-Philippe 
>>> sorry, the second one really is:
>>> 
>>> ./MYSDK (from the MYSDK.framework)
>>> -bash: ./MYSDK: cannot execute binary file
>>> 
>>> 2010/5/27 Louis-Philippe 
>>> 
>>> uname -a:
>>> Darwin modullpmacbook.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26 
>>> 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
>>> 
>>> ./MYSDK (from the MYSDK.framework)
>>> -bash: ./R3DSDK: No such file or directory
>>> 
>>> which macruby:
>>> /usr/local/bin/macruby
>>> 
>>> by the way, I tried it in a MacRuby cocoa app inside of xcode, but the 
>>> error sample I pasted above is from a macirb execution
>>> 
>>> 
>>> 2010/5/27 Joel Reymont 
>>> 
>>> Louis-Philippe,
>>> 
>>> On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:
>>> 
>>> > Did find:
>>> >   /PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
>>> >   from /PATH/(irb):2:in `'
>>> 
>>> Can you paste the output from the following?
>>> 
>>> uname -a
>>> 
>>> file ATH/MYSDK.framework/MYSDK
>>> 
>>> file `which macruby`
>>> 
>>>Thanks, Joel
>>> 
>>> ---
>>> http://twitter.com/wagerlabs
>>> 
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>> 
>>> 
>>> 
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>> 
>> 
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>> 
>> 
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> 
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> 
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel



smime.p7s
Description: S/MIME cryptographic signature
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Louis-Philippe

any idea why gen_bridge_metadata does spit this:

gen_bridge_metadata --64-bit -f ./MYSDK.framework -o MYSDK.bridgesupport
./MYSDK.framework/Headers/MYSDK.h:21:18: error: string: No such file or
directory
/usr/bin/cpp-4.2 returned 1 exit status
line was: /usr/bin/cpp-4.2 -D__APPLE_CPP__ -include
/usr/include/AvailabilityMacros.h -F"."
"./MYSDK.framework/Headers/MYSDK.h" 2>/tmp/.cpp.err
Usage: gen_bridge_metadata [options] 
Use the `-h' flag or consult gen_bridge_metadata(1) for help.

it's referring to this line in the SDK header:
#include 

and the SDK uses std::string all over the place...
why is it complaining like this?


2010/5/27 Jordan Breeding 

> You might have to make a bridge support file and include it in your
> framework.
>
> Something like this (although this is specific to running inside my Xcode
> project build):
>
> printf "Building BridgeSupport files...\n\n"
>
> BRIDGE_SUPPORT_DIR="Resources/BridgeSupport"
> BRIDGE_SUPPORT_FILE="${BRIDGE_SUPPORT_DIR}/${TARGET_NAME}.bridgesupport"
>
> if [[ "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${TARGET_NAME}" -nt
> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_FILE}" ]]; then
>   if [[ ! -d "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_DIR}"
> ]]; then
> mkdir -p "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_DIR}"
>   fi
>   gen_bridge_metadata --64-bit --framework
> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}" -o
> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_FILE}"
> fi
>
> On May 27, 2010, at 10:31, Louis-Philippe wrote:
>
> Thanks!
> ok... I sorted some of the issues out... I was able to make a x86_64
> framework out of the SDK by including the proper exports symbols (using nm
> with the -arch flag).
>
> so now it loads fine with the framework method...
> but I cant access the c++ namespace:
> "NameError: uninitialized constant MYSDK"
>
> 2010/5/27 Jordan Breeding 
>
>> Then you could force macruby/macirb to run as i386:
>>
>> `arch -arch i386 macirb`
>>
>> On May 27, 2010, at 10:13, Louis-Philippe wrote:
>>
>> it only builds for i386...
>> getting errors when trying to build for x86_64...
>> thats why I tried as I tested to build only for i386...
>>
>> 2010/5/27 Jordan Breeding 
>>
>>> Try building your framework as both i386 and x86_64.
>>>
>>> On May 27, 2010, at 10:00, Louis-Philippe wrote:
>>>
>>> file PATH/MYSDK.framework/MYSDK
>>> ./MYSDK: Mach-O dynamically linked shared library i386
>>>
>>> file `which macruby`:
>>> /usr/local/bin/macruby: Mach-O universal binary with 2 architectures
>>> /usr/local/bin/macruby (for architecture i386): Mach-O executable i386
>>> /usr/local/bin/macruby (for architecture x86_64): Mach-O 64-bit
>>> executable x86_64
>>>
>>>
>>> 2010/5/27 Louis-Philippe 
>>>
 sorry, the second one really is:

 ./MYSDK (from the MYSDK.framework)
 -bash: ./MYSDK: cannot execute binary file

 2010/5/27 Louis-Philippe 

 uname -a:
> Darwin modullpmacbook.local 10.3.0 Darwin Kernel Version 10.3.0: Fri
> Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
>
> ./MYSDK (from the MYSDK.framework)
> -bash: ./R3DSDK: No such file or directory
>
> which macruby:
> /usr/local/bin/macruby
>
> by the way, I tried it in a MacRuby cocoa app inside of xcode, but the
> error sample I pasted above is from a macirb execution
>
>
> 2010/5/27 Joel Reymont 
>
> Louis-Philippe,
>>
>> On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:
>>
>> > Did find:
>> >   /PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
>> >   from /PATH/(irb):2:in `'
>>
>> Can you paste the output from the following?
>>
>> uname -a
>>
>> file ATH/MYSDK.framework/MYSDK
>>
>> file `which macruby`
>>
>>Thanks, Joel
>>
>> ---
>> http://twitter.com/wagerlabs
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
>

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

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Jordan Breeding

Don't know, the only times I have used that method the header file itself is 
just straight C, the implementation hides all of the C++ in my case. Maybe 
gen_bridge_metadata doesn't handle C++.

On May 27, 2010, at 11:49, Louis-Philippe wrote:

> any idea why gen_bridge_metadata does spit this:
> 
> gen_bridge_metadata --64-bit -f ./MYSDK.framework -o MYSDK.bridgesupport
> ./MYSDK.framework/Headers/MYSDK.h:21:18: error: string: No such file or 
> directory
> /usr/bin/cpp-4.2 returned 1 exit status
> line was: /usr/bin/cpp-4.2 -D__APPLE_CPP__ -include 
> /usr/include/AvailabilityMacros.h -F"."   "./MYSDK.framework/Headers/MYSDK.h" 
> 2>/tmp/.cpp.err
> Usage: gen_bridge_metadata [options] 
> Use the `-h' flag or consult gen_bridge_metadata(1) for help.
> 
> it's referring to this line in the SDK header:
> #include 
> 
> and the SDK uses std::string all over the place...
> why is it complaining like this?
> 
> 
> 2010/5/27 Jordan Breeding 
> You might have to make a bridge support file and include it in your framework.
> 
> Something like this (although this is specific to running inside my Xcode 
> project build):
> 
> printf "Building BridgeSupport files...\n\n"
> 
> BRIDGE_SUPPORT_DIR="Resources/BridgeSupport"
> BRIDGE_SUPPORT_FILE="${BRIDGE_SUPPORT_DIR}/${TARGET_NAME}.bridgesupport"
> 
> if [[ "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${TARGET_NAME}" -nt 
> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_FILE}" ]]; then
>   if [[ ! -d "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_DIR}" ]]; 
> then
> mkdir -p "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_DIR}"
>   fi
>   gen_bridge_metadata --64-bit --framework 
> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}" -o 
> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_FILE}"
> fi
> 
> On May 27, 2010, at 10:31, Louis-Philippe wrote:
> 
>> Thanks!
>> ok... I sorted some of the issues out... I was able to make a x86_64 
>> framework out of the SDK by including the proper exports symbols (using nm 
>> with the -arch flag).
>> 
>> so now it loads fine with the framework method...
>> but I cant access the c++ namespace:
>> "NameError: uninitialized constant MYSDK"
>> 
>> 2010/5/27 Jordan Breeding 
>> Then you could force macruby/macirb to run as i386:
>> 
>> `arch -arch i386 macirb`
>> 
>> On May 27, 2010, at 10:13, Louis-Philippe wrote:
>> 
>>> it only builds for i386...
>>> getting errors when trying to build for x86_64...
>>> thats why I tried as I tested to build only for i386...
>>> 
>>> 2010/5/27 Jordan Breeding 
>>> Try building your framework as both i386 and x86_64.
>>> 
>>> On May 27, 2010, at 10:00, Louis-Philippe wrote:
>>> 
 file PATH/MYSDK.framework/MYSDK
 ./MYSDK: Mach-O dynamically linked shared library i386
 
 file `which macruby`:
 /usr/local/bin/macruby: Mach-O universal binary with 2 architectures
 /usr/local/bin/macruby (for architecture i386):Mach-O executable i386
 /usr/local/bin/macruby (for architecture x86_64):  Mach-O 64-bit 
 executable x86_64
 
 
 2010/5/27 Louis-Philippe 
 sorry, the second one really is:
 
 ./MYSDK (from the MYSDK.framework)
 -bash: ./MYSDK: cannot execute binary file
 
 2010/5/27 Louis-Philippe 
 
 uname -a:
 Darwin modullpmacbook.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 
 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
 
 ./MYSDK (from the MYSDK.framework)
 -bash: ./R3DSDK: No such file or directory
 
 which macruby:
 /usr/local/bin/macruby
 
 by the way, I tried it in a MacRuby cocoa app inside of xcode, but the 
 error sample I pasted above is from a macirb execution
 
 
 2010/5/27 Joel Reymont 
 
 Louis-Philippe,
 
 On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:
 
 > Did find:
 >   /PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
 >   from /PATH/(irb):2:in `'
 
 Can you paste the output from the following?
 
 uname -a
 
 file ATH/MYSDK.framework/MYSDK
 
 file `which macruby`
 
Thanks, Joel
 
 ---
 http://twitter.com/wagerlabs
 
 ___
 MacRuby-devel mailing list
 MacRuby-devel@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
 
 
 
 ___
 MacRuby-devel mailing list
 MacRuby-devel@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>> 
>>> 
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>> 
>>> 
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>> 
>>

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Louis-Philippe

I see on the BridgeSupport support to redirect all request to Laurent...
so here it is...

Laurent,
Is it desperate to keep trying every options of gen_bridge_metadata?
will it swallow my c++ framework at some point?

thanks

2010/5/27 Jordan Breeding 

> Don't know, the only times I have used that method the header file itself
> is just straight C, the implementation hides all of the C++ in my case.
> Maybe gen_bridge_metadata doesn't handle C++.
>
> On May 27, 2010, at 11:49, Louis-Philippe wrote:
>
> any idea why gen_bridge_metadata does spit this:
>
> gen_bridge_metadata --64-bit -f ./MYSDK.framework -o MYSDK.bridgesupport
> ./MYSDK.framework/Headers/MYSDK.h:21:18: error: string: No such file or
> directory
> /usr/bin/cpp-4.2 returned 1 exit status
> line was: /usr/bin/cpp-4.2 -D__APPLE_CPP__ -include
> /usr/include/AvailabilityMacros.h -F"."
> "./MYSDK.framework/Headers/MYSDK.h" 2>/tmp/.cpp.err
> Usage: gen_bridge_metadata [options] 
> Use the `-h' flag or consult gen_bridge_metadata(1) for help.
>
> it's referring to this line in the SDK header:
> #include 
>
> and the SDK uses std::string all over the place...
> why is it complaining like this?
>
>
> 2010/5/27 Jordan Breeding 
>
>> You might have to make a bridge support file and include it in your
>> framework.
>>
>> Something like this (although this is specific to running inside my Xcode
>> project build):
>>
>> printf "Building BridgeSupport files...\n\n"
>>
>> BRIDGE_SUPPORT_DIR="Resources/BridgeSupport"
>> BRIDGE_SUPPORT_FILE="${BRIDGE_SUPPORT_DIR}/${TARGET_NAME}.bridgesupport"
>>
>> if [[ "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${TARGET_NAME}" -nt
>> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_FILE}" ]]; then
>>   if [[ ! -d "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_DIR}"
>> ]]; then
>> mkdir -p "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_DIR}"
>>   fi
>>   gen_bridge_metadata --64-bit --framework
>> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}" -o
>> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_FILE}"
>> fi
>>
>> On May 27, 2010, at 10:31, Louis-Philippe wrote:
>>
>> Thanks!
>> ok... I sorted some of the issues out... I was able to make a x86_64
>> framework out of the SDK by including the proper exports symbols (using nm
>> with the -arch flag).
>>
>> so now it loads fine with the framework method...
>> but I cant access the c++ namespace:
>> "NameError: uninitialized constant MYSDK"
>>
>> 2010/5/27 Jordan Breeding 
>>
>>> Then you could force macruby/macirb to run as i386:
>>>
>>> `arch -arch i386 macirb`
>>>
>>> On May 27, 2010, at 10:13, Louis-Philippe wrote:
>>>
>>> it only builds for i386...
>>> getting errors when trying to build for x86_64...
>>> thats why I tried as I tested to build only for i386...
>>>
>>> 2010/5/27 Jordan Breeding 
>>>
 Try building your framework as both i386 and x86_64.

 On May 27, 2010, at 10:00, Louis-Philippe wrote:

 file PATH/MYSDK.framework/MYSDK
 ./MYSDK: Mach-O dynamically linked shared library i386

 file `which macruby`:
 /usr/local/bin/macruby: Mach-O universal binary with 2 architectures
 /usr/local/bin/macruby (for architecture i386): Mach-O executable i386
 /usr/local/bin/macruby (for architecture x86_64): Mach-O 64-bit
 executable x86_64


 2010/5/27 Louis-Philippe 

> sorry, the second one really is:
>
> ./MYSDK (from the MYSDK.framework)
> -bash: ./MYSDK: cannot execute binary file
>
> 2010/5/27 Louis-Philippe 
>
> uname -a:
>> Darwin modullpmacbook.local 10.3.0 Darwin Kernel Version 10.3.0: Fri
>> Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
>>
>> ./MYSDK (from the MYSDK.framework)
>> -bash: ./R3DSDK: No such file or directory
>>
>> which macruby:
>> /usr/local/bin/macruby
>>
>> by the way, I tried it in a MacRuby cocoa app inside of xcode, but the
>> error sample I pasted above is from a macirb execution
>>
>>
>> 2010/5/27 Joel Reymont 
>>
>> Louis-Philippe,
>>>
>>> On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:
>>>
>>> > Did find:
>>> >   /PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
>>> >   from /PATH/(irb):2:in `'
>>>
>>> Can you paste the output from the following?
>>>
>>> uname -a
>>>
>>> file ATH/MYSDK.framework/MYSDK
>>>
>>> file `which macruby`
>>>
>>>Thanks, Joel
>>>
>>> ---
>>> http://twitter.com/wagerlabs
>>>
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>
>>
>
 ___
 MacRuby-devel mailing list
 MacRuby-devel@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel



 ___

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Laurent Sansonetti

Hi Louis-Philippe,

BridgeSupport doesn't support C++. It only exposes C and Objective-C symbols.

In your C++ library, what is MYSDK exactly? If it isn't an Objective-C class, 
it won't be accessible from MacRuby.

In order to use your C++ code in MacRuby, the best way is to wrap the calls you 
need in Objective-C APIs. You can then access them from MacRuby at no cost. And 
a bridgesupport file won't be needed.

Laurent

On May 27, 2010, at 12:48 PM, Louis-Philippe wrote:

> I see on the BridgeSupport support to redirect all request to Laurent...
> so here it is...
> 
> Laurent,
> Is it desperate to keep trying every options of gen_bridge_metadata?
> will it swallow my c++ framework at some point?
> 
> thanks
> 
> 2010/5/27 Jordan Breeding 
> Don't know, the only times I have used that method the header file itself is 
> just straight C, the implementation hides all of the C++ in my case. Maybe 
> gen_bridge_metadata doesn't handle C++.
> 
> On May 27, 2010, at 11:49, Louis-Philippe wrote:
> 
>> any idea why gen_bridge_metadata does spit this:
>> 
>> gen_bridge_metadata --64-bit -f ./MYSDK.framework -o MYSDK.bridgesupport
>> ./MYSDK.framework/Headers/MYSDK.h:21:18: error: string: No such file or 
>> directory
>> /usr/bin/cpp-4.2 returned 1 exit status
>> line was: /usr/bin/cpp-4.2 -D__APPLE_CPP__ -include 
>> /usr/include/AvailabilityMacros.h -F"."   
>> "./MYSDK.framework/Headers/MYSDK.h" 2>/tmp/.cpp.err
>> Usage: gen_bridge_metadata [options] 
>> Use the `-h' flag or consult gen_bridge_metadata(1) for help.
>> 
>> it's referring to this line in the SDK header:
>> #include 
>> 
>> and the SDK uses std::string all over the place...
>> why is it complaining like this?
>> 
>> 
>> 2010/5/27 Jordan Breeding 
>> You might have to make a bridge support file and include it in your 
>> framework.
>> 
>> Something like this (although this is specific to running inside my Xcode 
>> project build):
>> 
>> printf "Building BridgeSupport files...\n\n"
>> 
>> BRIDGE_SUPPORT_DIR="Resources/BridgeSupport"
>> BRIDGE_SUPPORT_FILE="${BRIDGE_SUPPORT_DIR}/${TARGET_NAME}.bridgesupport"
>> 
>> if [[ "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${TARGET_NAME}" -nt 
>> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_FILE}" ]]; then
>>   if [[ ! -d "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_DIR}" ]]; 
>> then
>> mkdir -p "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_DIR}"
>>   fi
>>   gen_bridge_metadata --64-bit --framework 
>> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}" -o 
>> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_FILE}"
>> fi
>> 
>> On May 27, 2010, at 10:31, Louis-Philippe wrote:
>> 
>>> Thanks!
>>> ok... I sorted some of the issues out... I was able to make a x86_64 
>>> framework out of the SDK by including the proper exports symbols (using nm 
>>> with the -arch flag).
>>> 
>>> so now it loads fine with the framework method...
>>> but I cant access the c++ namespace:
>>> "NameError: uninitialized constant MYSDK"
>>> 
>>> 2010/5/27 Jordan Breeding 
>>> Then you could force macruby/macirb to run as i386:
>>> 
>>> `arch -arch i386 macirb`
>>> 
>>> On May 27, 2010, at 10:13, Louis-Philippe wrote:
>>> 
 it only builds for i386...
 getting errors when trying to build for x86_64...
 thats why I tried as I tested to build only for i386...
 
 2010/5/27 Jordan Breeding 
 Try building your framework as both i386 and x86_64.
 
 On May 27, 2010, at 10:00, Louis-Philippe wrote:
 
> file PATH/MYSDK.framework/MYSDK
> ./MYSDK: Mach-O dynamically linked shared library i386
> 
> file `which macruby`:
> /usr/local/bin/macruby: Mach-O universal binary with 2 architectures
> /usr/local/bin/macruby (for architecture i386):   Mach-O executable i386
> /usr/local/bin/macruby (for architecture x86_64): Mach-O 64-bit 
> executable x86_64
> 
> 
> 2010/5/27 Louis-Philippe 
> sorry, the second one really is:
> 
> ./MYSDK (from the MYSDK.framework)
> -bash: ./MYSDK: cannot execute binary file
> 
> 2010/5/27 Louis-Philippe 
> 
> uname -a:
> Darwin modullpmacbook.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 
> 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
> 
> ./MYSDK (from the MYSDK.framework)
> -bash: ./R3DSDK: No such file or directory
> 
> which macruby:
> /usr/local/bin/macruby
> 
> by the way, I tried it in a MacRuby cocoa app inside of xcode, but the 
> error sample I pasted above is from a macirb execution
> 
> 
> 2010/5/27 Joel Reymont 
> 
> Louis-Philippe,
> 
> On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:
> 
> > Did find:
> >   /PATH/MYSDK.framework/MYSDK: mach-o, but wrong architecture)
> >   from /PATH/(irb):2:in `'
> 
> Can you paste the output from the following?
> 
> uname -a
> 
> file ATH/MYSDK.framework/MYSDK
> 
> file `which macruby`
> 
>

Re: [MacRuby-devel] [NEW FILE] add string performance tests

2010-05-27 Thread Laurent Sansonetti

Hi Jordan,

The perf suite is far to be completed but we will definitely cover most String 
methods there at some point. In the meantime, your tests have some side effects 
I'm afraid (literal strings in loops are object creations).

Laurent

On May 26, 2010, at 9:09 PM, Jordan Breeding wrote:

> Right now MacRuby is really quite slow for string operations, I noticed it a 
> while back when doing large amounts of string creation, characters swapping, 
> and pushing/popping strings into/out of a priority queue.
> 
> The attached file is a string performance test and here is a run on my 15" 
> Core i7 MBP with ruby 1.9.1, jruby, and MacRuby:
> 
> Nameruby 1.9.1p378  MacRuby version jruby 1.5.0.RC1   
>   
> 
> array:<<0.7510821.1686931.29  
>   
> array:new   0.3949971.9176010.277000  
>   
> array:[]0.3244540.7550540.472000  
>   
> array:[]=   1.6918400.7652250.822000  
>   
> hash:new1.5015954.5635490.444000  
>   
> hash:[] 0.6127011.0515020.589000  
>   
> hash:[]=2.0123671.1358560.902000  
>   
> ivar:get0.2154240.3448731.087000  
>   
> ivar:set1.3494660.2439091.902000  
>   
> ivar:attr_writer1.2458944.5874880.655000  
>   
> ivar:attr_reader1.0457792.7553030.482000  
>   
> loop:upto   1.2115985.2151690.874000  
>   
> loop:times  1.2107815.2150540.876000  
>   
> loop:while  0.5993300.1570190.937000  
>   
> loop:for1.4421540.8118751.132000  
>   
> method:args 0.7282480.6820971.434000  
>   
> method:noarg0.8224630.5783830.837000  
>   
> method:splat0.4786101.8057600.227000  
>   
> method:empty0.8074050.5278511.062000  
>   
> method:opt  1.0271462.5797150.944000  
>   
> misc:ao_bench   7.8380538.5299543.248000  
>   
> misc:sudoku 1.7401962.1725812.461000  
>   
> misc:tak1.2773990.1555341.563000  
>   
> misc:mandelbrot 2.9563190.1245880.854000  
>   
> misc:fib3.8271940.5749004.935000  
>   
> misc:ack1.0491000.1162991.217000  
>   
> proc:call+splat 0.3183461.1196650.191000  
>   
> proc:call+args  2.4771121.1008482.995000  
>   
> proc:call+noarg 2.4962781.0719533.507000  
>   
> string:store swap   0.1537840.4792020.033000  
>   
> string:<<   0.481788143.615735  0.099000  
>   
> string:new  0.2769541.5747150.207000  
>   
> string:[]   0.4281821.8992330.072000  
>   
> string:tuple swap   0.1813180.7217780.045000  
>   
> yield:noarg 0.7832810.7202541.269000  
>   
> yield:splat 0.1592190.9657130.094000  
>   
> yield:less_arity0.1924180.8438670.345000  
>   
> yield:same_arity0.9378230.7633441.547000  
>   
> yield:more_arity0.1925160.8481790.421000
> 
> Jordan
> 
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

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

Re: [MacRuby-devel] [NEW FILE] add string performance tests

2010-05-27 Thread Jordan Breeding

Good point, what if I change to appending binary info?

str << 1

vs.

str << "1"

On May 27, 2010, at 15:37, Laurent Sansonetti wrote:

> Hi Jordan,
> 
> The perf suite is far to be completed but we will definitely cover most 
> String methods there at some point. In the meantime, your tests have some 
> side effects I'm afraid (literal strings in loops are object creations).
> 
> Laurent
> 
> On May 26, 2010, at 9:09 PM, Jordan Breeding wrote:
> 
>> Right now MacRuby is really quite slow for string operations, I noticed it a 
>> while back when doing large amounts of string creation, characters swapping, 
>> and pushing/popping strings into/out of a priority queue.
>> 
>> The attached file is a string performance test and here is a run on my 15" 
>> Core i7 MBP with ruby 1.9.1, jruby, and MacRuby:
>> 
>> Nameruby 1.9.1p378  MacRuby version jruby 1.5.0.RC1  
>>
>> 
>> array:<<0.7510821.1686931.29 
>>
>> array:new   0.3949971.9176010.277000 
>>
>> array:[]0.3244540.7550540.472000 
>>
>> array:[]=   1.6918400.7652250.822000 
>>
>> hash:new1.5015954.5635490.444000 
>>
>> hash:[] 0.6127011.0515020.589000 
>>
>> hash:[]=2.0123671.1358560.902000 
>>
>> ivar:get0.2154240.3448731.087000 
>>
>> ivar:set1.3494660.2439091.902000 
>>
>> ivar:attr_writer1.2458944.5874880.655000 
>>
>> ivar:attr_reader1.0457792.7553030.482000 
>>
>> loop:upto   1.2115985.2151690.874000 
>>
>> loop:times  1.2107815.2150540.876000 
>>
>> loop:while  0.5993300.1570190.937000 
>>
>> loop:for1.4421540.8118751.132000 
>>
>> method:args 0.7282480.6820971.434000 
>>
>> method:noarg0.8224630.5783830.837000 
>>
>> method:splat0.4786101.8057600.227000 
>>
>> method:empty0.8074050.5278511.062000 
>>
>> method:opt  1.0271462.5797150.944000 
>>
>> misc:ao_bench   7.8380538.5299543.248000 
>>
>> misc:sudoku 1.7401962.1725812.461000 
>>
>> misc:tak1.2773990.1555341.563000 
>>
>> misc:mandelbrot 2.9563190.1245880.854000 
>>
>> misc:fib3.8271940.5749004.935000 
>>
>> misc:ack1.0491000.1162991.217000 
>>
>> proc:call+splat 0.3183461.1196650.191000 
>>
>> proc:call+args  2.4771121.1008482.995000 
>>
>> proc:call+noarg 2.4962781.0719533.507000 
>>
>> string:store swap   0.1537840.4792020.033000 
>>
>> string:<<   0.481788143.615735  0.099000 
>>
>> string:new  0.2769541.5747150.207000 
>>
>> string:[]   0.4281821.8992330.072000 
>>
>> string:tuple swap   0.1813180.7217780.045000 
>>
>> yield:noarg 0.7832810.7202541.269000 
>>
>> yield:splat 0.1592190.9657130.094000 
>>
>> yield:less_arity0.1924180.8438670.345000 
>>
>> yield:same_arity0.9378230.7633441.547000 
>>
>> yield:more_arity0.1925160.8481790.421000
>> 
>> Jordan
>> 
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel



smime.p7s
Description: S/MIME cryptographic signature
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listin

Re: [MacRuby-devel] c++ lib

2010-05-27 Thread Louis-Philippe

Thanks Laurent!
MYSDK is a c++ SDK... 4 c++ headers and a c++ binary archive (.a)
I will work out my Objective-C wrapper then!

2010/5/27 Laurent Sansonetti 

> Hi Louis-Philippe,
>
> BridgeSupport doesn't support C++. It only exposes C and Objective-C
> symbols.
>
> In your C++ library, what is MYSDK exactly? If it isn't an Objective-C
> class, it won't be accessible from MacRuby.
>
> In order to use your C++ code in MacRuby, the best way is to wrap the calls
> you need in Objective-C APIs. You can then access them from MacRuby at no
> cost. And a bridgesupport file won't be needed.
>
> Laurent
>
> On May 27, 2010, at 12:48 PM, Louis-Philippe wrote:
>
> I see on the BridgeSupport support to redirect all request to Laurent...
> so here it is...
>
> Laurent,
> Is it desperate to keep trying every options of gen_bridge_metadata?
> will it swallow my c++ framework at some point?
>
> thanks
>
> 2010/5/27 Jordan Breeding 
>
>> Don't know, the only times I have used that method the header file itself
>> is just straight C, the implementation hides all of the C++ in my case.
>> Maybe gen_bridge_metadata doesn't handle C++.
>>
>> On May 27, 2010, at 11:49, Louis-Philippe wrote:
>>
>> any idea why gen_bridge_metadata does spit this:
>>
>> gen_bridge_metadata --64-bit -f ./MYSDK.framework -o MYSDK.bridgesupport
>> ./MYSDK.framework/Headers/MYSDK.h:21:18: error: string: No such file or
>> directory
>> /usr/bin/cpp-4.2 returned 1 exit status
>> line was: /usr/bin/cpp-4.2 -D__APPLE_CPP__ -include
>> /usr/include/AvailabilityMacros.h -F"."
>> "./MYSDK.framework/Headers/MYSDK.h" 2>/tmp/.cpp.err
>> Usage: gen_bridge_metadata [options] 
>> Use the `-h' flag or consult gen_bridge_metadata(1) for help.
>>
>> it's referring to this line in the SDK header:
>> #include 
>>
>> and the SDK uses std::string all over the place...
>> why is it complaining like this?
>>
>>
>> 2010/5/27 Jordan Breeding 
>>
>>> You might have to make a bridge support file and include it in your
>>> framework.
>>>
>>> Something like this (although this is specific to running inside my Xcode
>>> project build):
>>>
>>> printf "Building BridgeSupport files...\n\n"
>>>
>>> BRIDGE_SUPPORT_DIR="Resources/BridgeSupport"
>>> BRIDGE_SUPPORT_FILE="${BRIDGE_SUPPORT_DIR}/${TARGET_NAME}.bridgesupport"
>>>
>>> if [[ "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${TARGET_NAME}" -nt
>>> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_FILE}" ]]; then
>>>   if [[ ! -d "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_DIR}"
>>> ]]; then
>>> mkdir -p "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_DIR}"
>>>   fi
>>>   gen_bridge_metadata --64-bit --framework
>>> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}" -o
>>> "${TARGET_BUILD_DIR}/${WRAPPER_NAME}/${BRIDGE_SUPPORT_FILE}"
>>> fi
>>>
>>> On May 27, 2010, at 10:31, Louis-Philippe wrote:
>>>
>>> Thanks!
>>> ok... I sorted some of the issues out... I was able to make a x86_64
>>> framework out of the SDK by including the proper exports symbols (using nm
>>> with the -arch flag).
>>>
>>> so now it loads fine with the framework method...
>>> but I cant access the c++ namespace:
>>> "NameError: uninitialized constant MYSDK"
>>>
>>> 2010/5/27 Jordan Breeding 
>>>
 Then you could force macruby/macirb to run as i386:

 `arch -arch i386 macirb`

 On May 27, 2010, at 10:13, Louis-Philippe wrote:

 it only builds for i386...
 getting errors when trying to build for x86_64...
 thats why I tried as I tested to build only for i386...

 2010/5/27 Jordan Breeding 

> Try building your framework as both i386 and x86_64.
>
> On May 27, 2010, at 10:00, Louis-Philippe wrote:
>
> file PATH/MYSDK.framework/MYSDK
> ./MYSDK: Mach-O dynamically linked shared library i386
>
> file `which macruby`:
> /usr/local/bin/macruby: Mach-O universal binary with 2 architectures
> /usr/local/bin/macruby (for architecture i386): Mach-O executable i386
> /usr/local/bin/macruby (for architecture x86_64): Mach-O 64-bit
> executable x86_64
>
>
> 2010/5/27 Louis-Philippe 
>
>> sorry, the second one really is:
>>
>> ./MYSDK (from the MYSDK.framework)
>> -bash: ./MYSDK: cannot execute binary file
>>
>> 2010/5/27 Louis-Philippe 
>>
>> uname -a:
>>> Darwin modullpmacbook.local 10.3.0 Darwin Kernel Version 10.3.0: Fri
>>> Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
>>>
>>> ./MYSDK (from the MYSDK.framework)
>>> -bash: ./R3DSDK: No such file or directory
>>>
>>> which macruby:
>>> /usr/local/bin/macruby
>>>
>>> by the way, I tried it in a MacRuby cocoa app inside of xcode, but
>>> the error sample I pasted above is from a macirb execution
>>>
>>>
>>> 2010/5/27 Joel Reymont 
>>>
>>> Louis-Philippe,

 On May 27, 2010, at 3:25 PM, Louis-Philippe wrote:

 > Did find:
 >   /PATH/MYSDK.framework/MYSDK: mac

Re: [MacRuby-devel] [NEW FILE] add string performance tests

2010-05-27 Thread Laurent Sansonetti

I would recommend using strings, but you can assign them to local variables 
then reuse these.

a = 'a'
...
while...
str << a

There is no doubt we also need to optimize literal strings but this can be done 
in another (separate) test.

Laurent

On May 27, 2010, at 1:39 PM, Jordan Breeding wrote:

> Good point, what if I change to appending binary info?
> 
> str << 1
> 
> vs.
> 
> str << "1"
> 
> On May 27, 2010, at 15:37, Laurent Sansonetti wrote:
> 
>> Hi Jordan,
>> 
>> The perf suite is far to be completed but we will definitely cover most 
>> String methods there at some point. In the meantime, your tests have some 
>> side effects I'm afraid (literal strings in loops are object creations).
>> 
>> Laurent
>> 
>> On May 26, 2010, at 9:09 PM, Jordan Breeding wrote:
>> 
>>> Right now MacRuby is really quite slow for string operations, I noticed it 
>>> a while back when doing large amounts of string creation, characters 
>>> swapping, and pushing/popping strings into/out of a priority queue.
>>> 
>>> The attached file is a string performance test and here is a run on my 15" 
>>> Core i7 MBP with ruby 1.9.1, jruby, and MacRuby:
>>> 
>>> Nameruby 1.9.1p378  MacRuby version jruby 1.5.0.RC1 
>>> 
>>> 
>>> array:<<0.7510821.1686931.29
>>> 
>>> array:new   0.3949971.9176010.277000
>>> 
>>> array:[]0.3244540.7550540.472000
>>> 
>>> array:[]=   1.6918400.7652250.822000
>>> 
>>> hash:new1.5015954.5635490.444000
>>> 
>>> hash:[] 0.6127011.0515020.589000
>>> 
>>> hash:[]=2.0123671.1358560.902000
>>> 
>>> ivar:get0.2154240.3448731.087000
>>> 
>>> ivar:set1.3494660.2439091.902000
>>> 
>>> ivar:attr_writer1.2458944.5874880.655000
>>> 
>>> ivar:attr_reader1.0457792.7553030.482000
>>> 
>>> loop:upto   1.2115985.2151690.874000
>>> 
>>> loop:times  1.2107815.2150540.876000
>>> 
>>> loop:while  0.5993300.1570190.937000
>>> 
>>> loop:for1.4421540.8118751.132000
>>> 
>>> method:args 0.7282480.6820971.434000
>>> 
>>> method:noarg0.8224630.5783830.837000
>>> 
>>> method:splat0.4786101.8057600.227000
>>> 
>>> method:empty0.8074050.5278511.062000
>>> 
>>> method:opt  1.0271462.5797150.944000
>>> 
>>> misc:ao_bench   7.8380538.5299543.248000
>>> 
>>> misc:sudoku 1.7401962.1725812.461000
>>> 
>>> misc:tak1.2773990.1555341.563000
>>> 
>>> misc:mandelbrot 2.9563190.1245880.854000
>>> 
>>> misc:fib3.8271940.5749004.935000
>>> 
>>> misc:ack1.0491000.1162991.217000
>>> 
>>> proc:call+splat 0.3183461.1196650.191000
>>> 
>>> proc:call+args  2.4771121.1008482.995000
>>> 
>>> proc:call+noarg 2.4962781.0719533.507000
>>> 
>>> string:store swap   0.1537840.4792020.033000
>>> 
>>> string:<<   0.481788143.615735  0.099000
>>> 
>>> string:new  0.2769541.5747150.207000
>>> 
>>> string:[]   0.4281821.8992330.072000
>>> 
>>> string:tuple swap   0.1813180.7217780.045000
>>> 
>>> yield:noarg 0.7832810.7202541.269000
>>> 
>>> yield:splat 0.1592190.9657130.094000
>>> 
>>> yield:less_arity0.1924180.8438670.345000
>>> 
>>> yield:same_arity0.9378230.7633441.547000
>>> 
>>> yield:more_arity0.1925160.8481790.421000
>>> 
>>> Jordan
>>> 
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailm

Re: [MacRuby-devel] [MacRuby] #681: YAML::add_domain_type is undefined

2010-05-27 Thread MacRuby

#681: YAML::add_domain_type is undefined
+---
 Reporter:  dave.bald...@…  |Owner:  lsansone...@…
 Type:  defect  |   Status:  closed   
 Priority:  blocker |Milestone:   
Component:  MacRuby |   Resolution:  fixed
 Keywords:  yaml add_domain_type|  
+---
Changes (by pthom...@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Fixed in r4170.

-- 
Ticket URL: 
MacRuby 

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

Re: [MacRuby-devel] [MacRuby] #595: our YAML library does not honor #add_builtin_type

2010-05-27 Thread MacRuby

#595: our YAML library does not honor #add_builtin_type
---+
 Reporter:  lsansone...@…  |Owner:  neerac...@…
 Type:  defect |   Status:  closed 
 Priority:  blocker|Milestone: 
Component:  MacRuby|   Resolution:  fixed  
 Keywords: |  
---+
Changes (by pthom...@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Fixed in r4170.

-- 
Ticket URL: 
MacRuby 

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

Re: [MacRuby-devel] [NEW FILE] add string performance tests

2010-05-27 Thread Jordan Breeding

Let me know if there is anything else I should change.

perf_test('new') do
  i = 0
  while i < 10
b = "#{i}"
c = "#{i} #{i}"
d = "#{i} #{i} #{i}"
i += 1
  end
end

perf_test('<< variables') do
  i = 0
  a = ""
  a1 = "1"
  a2 = "2"
  a3 = "3"
  a4 = "4"
  a5 = "5"
  while i < 25000
a << a1; a << a2; a << a3; a << a4; a << a5
a << a5; a << a4; a << a3; a << a2; a << a1
a << a1; a << a2; a << a3; a << a4; a << a5
a << a5; a << a4; a << a3; a << a2; a << a1
i += 1
  end
end

perf_test('<< literals') do
  i = 0
  a = ""
  while i < 25000
a << "1"; a << "2"; a << "3"; a << "4"; a << "5"
a << "5"; a << "4"; a << "3"; a << "2"; a << "1"
a << "1"; a << "2"; a << "3"; a << "4"; a << "5"
a << "5"; a << "4"; a << "3"; a << "2"; a << "1"
i += 1
  end
end

perf_test('[]') do
  i = 0
  a = "12345"
  while i < 10
a[0]; a[1]; a[2]; a[3]; a[4]
a[0]; a[1]; a[2]; a[3]; a[4]
a[0]; a[1]; a[2]; a[3]; a[4]
a[0]; a[1]; a[2]; a[3]; a[4]
i += 1
  end
end

perf_test('tuple swap') do
  i = 0
  a = "12345"
  while i < 10
a[4], a[0] = a[0], a[4]
a[3], a[1] = a[1], a[3]
i += 1
  end
end

perf_test('store swap') do
  i = 0
  a = "12345"
  while i < 10
temp = a[0]
a[0] = a[4]
a[4] = temp
temp = a[1]
a[1] = a[3]
a[3] = temp
i += 1
  end
end


On May 27, 2010, at 15:47, Laurent Sansonetti wrote:

> I would recommend using strings, but you can assign them to local variables 
> then reuse these.
> 
> a = 'a'
> ...
> while...
> str << a
> 
> There is no doubt we also need to optimize literal strings but this can be 
> done in another (separate) test.
> 
> Laurent
> 
> On May 27, 2010, at 1:39 PM, Jordan Breeding wrote:
> 
>> Good point, what if I change to appending binary info?
>> 
>> str << 1
>> 
>> vs.
>> 
>> str << "1"
>> 
>> On May 27, 2010, at 15:37, Laurent Sansonetti wrote:
>> 
>>> Hi Jordan,
>>> 
>>> The perf suite is far to be completed but we will definitely cover most 
>>> String methods there at some point. In the meantime, your tests have some 
>>> side effects I'm afraid (literal strings in loops are object creations).
>>> 
>>> Laurent
>>> 
>>> On May 26, 2010, at 9:09 PM, Jordan Breeding wrote:
>>> 
 Right now MacRuby is really quite slow for string operations, I noticed it 
 a while back when doing large amounts of string creation, characters 
 swapping, and pushing/popping strings into/out of a priority queue.
 
 The attached file is a string performance test and here is a run on my 15" 
 Core i7 MBP with ruby 1.9.1, jruby, and MacRuby:
 
 Nameruby 1.9.1p378  MacRuby version jruby 
 1.5.0.RC1 
 
 array:<<0.7510821.1686931.29   
  
 array:new   0.3949971.9176010.277000   
  
 array:[]0.3244540.7550540.472000   
  
 array:[]=   1.6918400.7652250.822000   
  
 hash:new1.5015954.5635490.444000   
  
 hash:[] 0.6127011.0515020.589000   
  
 hash:[]=2.0123671.1358560.902000   
  
 ivar:get0.2154240.3448731.087000   
  
 ivar:set1.3494660.2439091.902000   
  
 ivar:attr_writer1.2458944.5874880.655000   
  
 ivar:attr_reader1.0457792.7553030.482000   
  
 loop:upto   1.2115985.2151690.874000   
  
 loop:times  1.2107815.2150540.876000   
  
 loop:while  0.5993300.1570190.937000   
  
 loop:for1.4421540.8118751.132000   
  
 method:args 0.7282480.6820971.434000   
  
 method:noarg0.8224630.5783830.837000   
  
 method:splat0.4786101.8057600.227000   
  
 method:empty0.8074050.5278511.062000   
  
 method:opt  1.0271462.5797150.944000   
  
 misc:ao_bench   7.8380538.5299543.248000   
  
 misc:sudoku 1.7401962.1725812.461000   
  
 misc:tak1.2773990.1555341.563000   
  
 misc:mandelbrot 2.9563190.1245880.854000

Re: [MacRuby-devel] [MacRuby] #477: Need GCD wrapper for dispatch_once

2010-05-27 Thread MacRuby

#477: Need GCD wrapper for dispatch_once
+---
 Reporter:  ernest.prabha...@…  |Owner:  lsansone...@…
 Type:  enhancement |   Status:  closed   
 Priority:  minor   |Milestone:   
Component:  MacRuby |   Resolution:  wontfix  
 Keywords:  |  
+---
Changes (by lsansone...@…):

  * status:  new => closed
  * resolution:  => wontfix
  * milestone:  MacRuby 0.5 =>


Comment:

 Looks like we won't do that.

-- 
Ticket URL: 
MacRuby 

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

Re: [MacRuby-devel] [MacRuby] #678: Installing jeweler makes macruby blow up.

2010-05-27 Thread MacRuby

#678: Installing jeweler makes macruby blow up.
---+
 Reporter:  t...@…  |Owner:  lsansone...@…  
  
 Type:  defect |   Status:  closed  
 
 Priority:  blocker|Milestone:  
 
Component:  MacRuby|   Resolution:  fixed   
 
 Keywords:  jeweler rubygems "abort trap"  |  
---+
Changes (by martinlagarde...@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Fixed with r4171 :-)

-- 
Ticket URL: 
MacRuby 

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

Re: [MacRuby-devel] [MacRuby] #664: MacRuby Crashes When Scheduling a Block to Run on the Main Thread from a Background Thread

2010-05-27 Thread MacRuby

#664: MacRuby Crashes When Scheduling a Block to Run on the Main Thread from a
Background Thread
-+--
 Reporter:  dy...@…  |   Owner:  lsansone...@…
 Type:  defect   |  Status:  new  
 Priority:  blocker  |   Milestone:   
Component:  MacRuby  |Keywords:   
-+--

Comment(by martinlagarde...@…):

 Could you try with a nightly instead of trunk? I can't seem to reproduce
 the problem with Laurent's code :-)

-- 
Ticket URL: 
MacRuby 

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

Re: [MacRuby-devel] [MacRuby] #664: MacRuby Crashes When Scheduling a Block to Run on the Main Thread from a Background Thread

2010-05-27 Thread MacRuby

#664: MacRuby Crashes When Scheduling a Block to Run on the Main Thread from a
Background Thread
-+--
 Reporter:  dy...@…  |   Owner:  lsansone...@…
 Type:  defect   |  Status:  new  
 Priority:  blocker  |   Milestone:   
Component:  MacRuby  |Keywords:   
-+--

Comment(by lsansone...@…):

 I think it's environmental (depends of your hardware). The bug is not
 fixed yet, afaik.

-- 
Ticket URL: 
MacRuby 

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

Re: [MacRuby-devel] [MacRuby] #713: Growl is broken on MacRuby 0.6

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] [NEW FILE] add string performance tests

Re: [MacRuby-devel] [NEW FILE] add string performance tests

Re: [MacRuby-devel] c++ lib

Re: [MacRuby-devel] [NEW FILE] add string performance tests

Re: [MacRuby-devel] [MacRuby] #681: YAML::add_domain_type is undefined

Re: [MacRuby-devel] [MacRuby] #595: our YAML library does not honor #add_builtin_type

Re: [MacRuby-devel] [NEW FILE] add string performance tests

Re: [MacRuby-devel] [MacRuby] #477: Need GCD wrapper for dispatch_once

Re: [MacRuby-devel] [MacRuby] #678: Installing jeweler makes macruby blow up.

Re: [MacRuby-devel] [MacRuby] #664: MacRuby Crashes When Scheduling a Block to Run on the Main Thread from a Background Thread

Re: [MacRuby-devel] [MacRuby] #664: MacRuby Crashes When Scheduling a Block to Run on the Main Thread from a Background Thread

27 matches

Site Navigation

Mail list logo

Footer information