Page 9 of 9 FirstFirst ... 789
Results 81 to 85 of 85

Thread: Blizzard Still Has a World of Warcraft Linux Client

  1. #81
    Join Date
    May 2010
    Posts
    160

    Default

    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?

  2. #82
    Join Date
    Nov 2010
    Posts
    24

    Default

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

  3. #83
    Join Date
    Jun 2006
    Posts
    3,046

    Default

    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.

  4. #84
    Join Date
    Nov 2010
    Posts
    101

    Default

    Quote 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

  5. #85
    Join Date
    Jun 2008
    Location
    Perth, Scotland
    Posts
    435

    Default

    Quote 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.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •