Announcement

Collapse
No announcement yet.

A New Project To Run Mac OS X Binaries On Linux

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #41
    Originally posted by LubosD View Post
    I got me to the point of thinking whether it wouldn't be better in long term to implement Cocoa on top of something stable like Qt
    Great, now you've summoned the dreaded FunkSTAR.

    Comment


    • #42
      Originally posted by TheBlackCat View Post
      Great, now you've summoned the dreaded FunkSTAR.
      Sorry, I don't understand this reference

      Comment


      • #43
        "Of course, such an endeavor needs human resources and I don't have these. "


        where there is a will there is a way, code it and they will come...


        go forth my minions and deliver me final cut, running as it were native, if you are sucessful you will get not 10 but 20 shiny euros.

        Comment


        • #44
          Originally posted by LubosD View Post
          There's more missing. GNUstep would first need a Quartz backend. And then you'd have to emulate Quartz under X11 somehow. It's easier to just use any of the X11-compatible GNUstep backends, because the official ABI is "Cocoa".

          My biggest worry though is the state of GNUstep. Once I started writing various tests, I started finding bugs immediately in stuff you'd expect to be stable and proven by now. It's quite bad, worse than I thought. Half of the OS X apps I've tested don't start because GNUstep can't even load the NIB (UI definition) file properly. I got me to the point of thinking whether it wouldn't be better in long term to implement Cocoa on top of something stable like Qt: that way we wouldn't have to worry about that many implementation details, slowly work through all the APIs and then replace GNUstep.

          Of course, such an endeavor needs human resources and I don't have these.
          It seems though as if the GNUstep project has done quite a lot of work. Even if it needs fixing up, would it not be less work than reimplementing it from scratch?

          It appears that Cocoa is a very nice API for writing desktop applications with. Completing GNUstep would presumably allow people to develop for Linux using Cocoa as a first-class citizen, in addition to providing binary compatibility for existing OS X applications. That sounds like a good thing to me.

          Comment


          • #45
            Originally posted by pjlahaie View Post
            PearPC would probably be a better place to start since it runs OS X, unlike SheepShaver which was (IIRC) a MacOS System 7-9 emulator.

            http://pearpc.sourceforge.net/
            like i said most people around here don't seem to remember the apple emulation history never mind actually used them in real life

            true pearpc will also add to the existing available tried and trusted code base, its not about an ether or case here but rather taking what's available taking its assembly code ,API's etc, for sure there needs to be lots of C to assembly routines written and extended from what already exists and adding to this latest emulation app (assuming he wants to actually make it good and usable) for the better longer term... or not...

            OC, ether way he now knows of their functional existence and can evaluate them and their core speed of code on modern day hardware and make use of that sheep "
            built-in PowerPC emulator for non-PowerPC systems" as an integrated base with any pear code that helps etc....
            Last edited by popper; 12-10-2012, 02:47 PM.

            Comment


            • #46
              Originally posted by popper View Post
              like i said [COLOR=#000000][I]most people around here don't seem to remember the apple emulation history never mind actually used them in real life
              I've used sheepshaver, pearPC and i (currently) virtualize MacOSX in VMware - big fricking deal... I think your comment really comes across as trying to publicly measure your e-penis more than anything... I know plenty of other users (not necessarily in this forum, but linux users nonetheless) whom are aware and/or have used such applications.

              true pearpc will also add to the existing available tried and trusted code base, its not about an ether or case here but rather taking what's available taking its assembly code ,API's etc, for sure there needs to be lots of C to assembly routines written and extended from what already exists and adding to this latest emulation app (assuming he wants to actually make it good and usable) for the better longer term... or not...
              PearPc is a powerPC emulator... I don't get the impression that this project is the same thing, in fact - it seems to be much more like Wine than anything else.... 2ndly, MacOSX has not supported PPC since Snow Leopard (and had been moving away from PPC since 10.5) and even snow leopard dropped 'rosetta' (for running PPC apps on an intel mac) from being installed by default. (with newer releases ie: 10.7/.8 not supporting PPC at all) ~ So why the hell would an app that is focusing on supporting MacOSX applications (which these days are all x86/64) be based around PPC code bases, when PPC has been dead for some time on the Mac??

              also, running PPC code on x86 is pretty slow. To me, it makes far more sense to shoot for x86 and Arm being as they both matter in the mac/apple world of software.

              Originally posted by popper View Post
              OC, ether way he now knows of their functional existence and can evaluate them and their core speed of code on modern day hardware and make use of that sheep "built-in PowerPC emulator for non-PowerPC systems" as an integrated base with any pear code that helps etc....
              I would say putting any effort into supporting PPC is pointless, if your plan is to support MacOSX binaries on intel/amd/x86/x86_64 hardware.
              Last edited by ninez; 12-10-2012, 03:47 PM.

              Comment


              • #47
                Originally posted by LubosD View Post
                Sorry, I don't understand this reference
                Let's hope you never have a need to. Just don't mention KDE or Qt around here if you can possibly avoid it.

                Comment


                • #48
                  Originally posted by TheBlackCat View Post
                  Let's hope you never have a need to. Just don't mention KDE or Qt around here if you can possibly avoid it.
                  Some forum user won't decide about what other users will talk.

                  Comment


                  • #49
                    Originally posted by JS987 View Post
                    Some forum user won't decide about what other users will talk.

                    Comment


                    • #50
                      Originally posted by Wingfeather View Post
                      It seems though as if the GNUstep project has done quite a lot of work. Even if it needs fixing up, would it not be less work than reimplementing it from scratch?
                      You're right. But then you see how slow their backends are, how it still doesn't even support short language names when looking for resources ("en" instead of "English"; "en" is default in original Cocoa), you find bugs even in the About dialog. An then you start doubting their work

                      Comment

                      Working...
                      X