Announcement

Collapse
No announcement yet.

Blizzard Still Has a World of Warcraft Linux Client

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

  • #81
    Seems that someone was actually able to run extremely old Linux apps recently http://www.complang.tuwien.ac.at/ant...atibility.html

    It could be the fact that none of the libraries use that c++ library mentioned before, but I still think this proves something...

    even though you can have multiple versions of a library installed, I guess you cant have an app that has a library that depends on libstdc++5, and another one that depends on libstdc++6?

    Comment


    • #82
      Staticly link it and distribute as a tarball or install script like the nvidia drivers, what can possibly go wrong

      Comment


      • #83
        A couple of things... It's easier (and more robust...) to do an RPATH spec or a loader script that does LD_PRELOAD or LD_LIBRARY_PATH to handle inconsistencies. Statically linked, you have to send out a new binary if there's an ABI (as opposed to an API...) issue with the kernel. There was one transition that there were problems with. With .so's in a ./libs directory, there's a slim chance you might be able to fix the problem in the field with a small file inclusion or removing a pre-packaged .so.

        Comment


        • #84
          Originally posted by Svartalf View Post
          A couple of things... It's easier (and more robust...) to do an RPATH spec or a loader script that does LD_PRELOAD or LD_LIBRARY_PATH to handle inconsistencies. Statically linked, you have to send out a new binary if there's an ABI (as opposed to an API...) issue with the kernel. There was one transition that there were problems with. With .so's in a ./libs directory, there's a slim chance you might be able to fix the problem in the field with a small file inclusion or removing a pre-packaged .so.
          And they can consult people like Svartalf who actually work in the business of distributing games on Linux. Nothing's stopping them

          Comment


          • #85
            Originally posted by Svartalf View Post
            A couple of things... It's easier (and more robust...) to do an RPATH spec or a loader script that does LD_PRELOAD or LD_LIBRARY_PATH to handle inconsistencies. Statically linked, you have to send out a new binary if there's an ABI (as opposed to an API...) issue with the kernel. There was one transition that there were problems with. With .so's in a ./libs directory, there's a slim chance you might be able to fix the problem in the field with a small file inclusion or removing a pre-packaged .so.
            My thoughts exactly. Many games in the Humble Indie Bundle followed this approach and it worked well.

            Comment

            Working...
            X