Re: [MacRuby-devel] [MacRuby] #174: Allow embedding of arbitrary versions of MacRuby

2008-12-08 Thread MacRuby 
#174: Allow embedding of arbitrary versions of MacRuby
+---
 Reporter:  [EMAIL PROTECTED]  |   Owner:  [EMAIL PROTECTED]

 Type:  defect  |  Status:  new  
 Priority:  major   |   Milestone:   
Component:  MacRuby |Keywords:   
+---

Comment(by [EMAIL PROTECTED]):

 For me the Xcode target has never embedded the metadata. By default it
 seems to add itself to the list of targets, there it does nothing I can
 observe. If I try and drag it under the Application target itself the
 script generates an error because it won't go after the compile sources
 build phase.

 >I don't think that modifying the BridgeSupport parser to look for
 BridgeSupport files inside the framework is a good idea, because it
 violates the BridgeSupport load path that we discussed a year ago with the
 PyObjC guys.

 And then in the very next sentence you say the problem is temporary. So,
 given that, why not adopt this approach temporarily? It may not be what
 you discussed with the PyObjC folks but it's the best solution for your
 users. How are PyObjC even going to know if you add MR itself at the front
 of the load path? Why do they care?

 m/

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #174: Allow embedding of arbitrary versions of MacRuby

2008-12-08 Thread MacRuby 
#174: Allow embedding of arbitrary versions of MacRuby
+---
 Reporter:  [EMAIL PROTECTED]  |   Owner:  [EMAIL PROTECTED]

 Type:  defect  |  Status:  new  
 Priority:  major   |   Milestone:   
Component:  MacRuby |Keywords:   
+---

Comment(by [EMAIL PROTECTED]):

 Replying to [comment:7 [EMAIL PROTECTED]:
 > {{{
 > For me the Xcode target has never embedded the metadata. By default it
 seems to add itself to the list of targets, there it does nothing I can
 observe. If I try and drag it under the Application target itself the
 script generates an error because it won't go after the compile sources
 build phase.
 > }}}
 >
 > Once you add the Xcode target you need to manually build it, like any
 other Xcode targets. It will not build by default (which is the idea).
 >

 This whole process seems to me to be systematically prone to error.

 > I am not planning to do any more changes since the current solution
 works. It's worthless to spend more time since this problem is temporary.
 >

 Very well. It is your decision as the owner of the project.

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #174: Allow embedding of arbitrary versions of MacRuby

2008-12-08 Thread MacRuby 
#174: Allow embedding of arbitrary versions of MacRuby
+---
 Reporter:  [EMAIL PROTECTED]  |   Owner:  [EMAIL PROTECTED]

 Type:  defect  |  Status:  new  
 Priority:  major   |   Milestone:   
Component:  MacRuby |Keywords:   
+---

Comment(by [EMAIL PROTECTED]):

 It also seems that the change from using BUILD_AS_EMBEDDABLE has broken
 something.

 http://pastie.org/private/7kgbttwif2q1sad1o6uva

 I wrote my own script run phase to embed the metadata (using your original
 shell script which I know works because that's what was using to generate
 Elysium 0.8.2 which did work for people) and Andy has confirmed it's
 there.

 I've now released two versions of Elysium which have been broken: 0.8.3
 didn't include the metadata, and 0.8.4 MacRuby seems not to be able to
 find itself.

 m.

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #174: Allow embedding of arbitrary versions of MacRuby

2008-12-08 Thread MacRuby 
#174: Allow embedding of arbitrary versions of MacRuby
+---
 Reporter:  [EMAIL PROTECTED]  |   Owner:  [EMAIL PROTECTED]

 Type:  defect  |  Status:  new  
 Priority:  major   |   Milestone:   
Component:  MacRuby |Keywords:   
+---

Comment(by [EMAIL PROTECTED]):

 Replying to [comment:7 [EMAIL PROTECTED]:
 > Did you verify with {{{otool(1)}}} that your binary links against the
 version of MacRuby inside the bundle?
 >

 Okay for some reason it is now linking against MacRuby in /Library. Why?
 It's never done that before.

 > This should really be discussed on the mailing list.

 Uh. You mean I shouldn't report problems here?

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #174: Allow embedding of arbitrary versions of MacRuby

2008-12-08 Thread MacRuby 
#174: Allow embedding of arbitrary versions of MacRuby
+---
 Reporter:  [EMAIL PROTECTED]  |   Owner:  [EMAIL PROTECTED]

 Type:  defect  |  Status:  new  
 Priority:  major   |   Milestone:   
Component:  MacRuby |Keywords:   
+---

Comment(by [EMAIL PROTECTED]):

 {{{
 For me the Xcode target has never embedded the metadata. By default it
 seems to add itself to the list of targets, there it does nothing I can
 observe. If I try and drag it under the Application target itself the
 script generates an error because it won't go after the compile sources
 build phase.
 }}}

 Once you add the Xcode target you need to manually build it, like any
 other Xcode targets. It will not build by default (which is the idea).

 {{{
 And then in the very next sentence you say the problem is temporary. So,
 given that, why not adopt this approach temporarily? It may not be what
 you discussed with the PyObjC folks but it's the best solution for your
 users. How are PyObjC even going to know if you add MR itself at the front
 of the load path? Why do they care?
 }}}

 I am not planning to do any more changes since the current solution works.
 It's worthless to spend more time since this problem is temporary.

 {{{
 It also seems that the change from using BUILD_AS_EMBEDDABLE has broken
 something.

 http://pastie.org/private/7kgbttwif2q1sad1o6uva

 I wrote my own script run phase to embed the metadata (using your original
 shell script which I know works because that's what was using to generate
 Elysium 0.8.2 which did work for people) and Andy has confirmed it's
 there.

 I've now released two versions of Elysium which have been broken: 0.8.3
 didn't include the metadata, and 0.8.4 MacRuby seems not to be able to
 find itself.
 }}}

 Did you verify with {{{otool(1)}}} that your binary links against the
 version of MacRuby inside the bundle?

 The current system works fine for me, I tested it on several apps and used
 these apps on pure Leopard systems.

 If it does not work for you please report me more information (if possible
 with a sample project or a version of Elysium).

 This should really be discussed on the mailing list.

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #61: ObjectSpace.each_object(Foo) doesn't yield subclasses

2008-12-08 Thread MacRuby 
#61: ObjectSpace.each_object(Foo) doesn't yield subclasses
---+
 Reporter:  [EMAIL PROTECTED]  |Owner:  [EMAIL PROTECTED]   
 
 Type:  defect |   Status:  closed   
 Priority:  blocker|Milestone:  MacRuby 0.2  
Component:  MacRuby|   Resolution:  fixed
 Keywords: |  
---+

Comment(by [EMAIL PROTECTED]):

 This seems to be broken again.

 {{{
 >> ObjectSpace.each_object(Module).map { |x| x.class }.uniq
 => [Module]
 >> ObjectSpace.each_object(Class).map { |x| x.class }.uniq
 => [Class, Module]
 >> ObjectSpace.each_object(Class).include? NSObject
 => false
 >> NSObject.is_a? Class
 => true
 }}}

 on MRI 1.9:

 {{{
 >> ObjectSpace.each_object(Module).map { |x| x.class }.uniq
 => [Module, Class]
 >> ObjectSpace.each_object(Class).map { |x| x.class }.uniq
 => [Class]
 }}}

 PS. I tried to reopen the ticket, but got "Warning: No permission to
 change ticket fields."
 Perhaps I should create a new one?

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #174: Allow embedding of arbitrary versions of MacRuby

2008-12-08 Thread Jordan K. Hubbard 

Guys?

This is a very suboptimal, to say nothing of weird, way to  
communicate, I hope you both realize. :)


- Jordan

On Dec 8, 2008, at 2:51 AM, MacRuby wrote:


#174: Allow embedding of arbitrary versions of MacRuby
 
+---

Reporter:  [EMAIL PROTECTED]  |   Owner:  [EMAIL PROTECTED]
Type:  defect  |  Status:  new
Priority:  major   |   Milestone:
Component:  MacRuby |Keywords:
 
+---


Comment(by [EMAIL PROTECTED]):

Replying to [comment:7 [EMAIL PROTECTED]:

Did you verify with {{{otool(1)}}} that your binary links against the

version of MacRuby inside the bundle?




Okay for some reason it is now linking against MacRuby in /Library.  
Why?

It's never done that before.


This should really be discussed on the mailing list.


Uh. You mean I shouldn't report problems here?

--
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel