OpenMPT with WINE bundled (Linux x64)

[sk1re]

I bundeld OpenMPT with WINE and all of WINE's required dependencies - it should run on all Linux x64 Distros. 
OpenMPT 1.27.01.00 / WINE 2.19
Download:
http://www.mediafire.com/file/glulk6u2sk33goe/OpenMPT_Linux_x64_r01.zip ~123MB

There is no installation needed, just unzip and run the script "Run_OpenMPT.sh".
It will make a folder in your Home Directory: "~/.wine64-OpenMPT" so it does not interfere with an existing WINE (~/.wine) installation(if there is one).
I tested this with Lubuntu, Debian and Arch Linux.

best regards,
-sk1re

[Saga Musix]

I'm not a big fan of such bundles*. First off, I somehow doubt it would run on *all* x64 distros - second these kind of bundles become outdated very quickly. Wine already offers up-to-date package repositories for example for Ubuntu and derivatives which are very simple to add to the system. Once that is installed, it's of course also very simple to just install OpenMPT.

*From my experience with other projects, they will not get updated anymore after a while, leaving people running old buggy software. OpenMPT has an automatic update check but I guess Wine does not.

[sk1re]

I personally like to have my apps portable. My script "Run_OpenMPT.sh" is based on "AppImage". https://www.appimage.org/
In Windows the dependencies are the *.dll files, Linux uses *.so. AppImage combines the Linux executable with the required .so files.
I looked into the AppImage source code and found that it works with LD_LIBRARY_PATH environment variable.
So it really should run on every Linux x64 Disto. I could not make an AppImage because it didn't let me start WINE with the "mptrack.exe" inside the *.AppImage file so i made this script.

Here are some other AppImages you can try:
https://bintray.com/probono/AppImages
Some applications like OpenShot, Krita also offer their own AppImages.

There is a solution for updating WINE or any other App with AppImage:
https://github.com/AppImage/AppImageKit/blob/master/AppImageUpdate.AppDir/README.md

[Saga Musix]

That seems like a good use-case for the package. As I mentioned my main gripe would be out-of-date versions, which I guess that latter link can solve. The problem is really when someone puts up a package like this and then just doesn't update it anymore, yet people keep using it because it's simpler than compiling it themselves. So maybe a simple (if that's possible ) how-to guide for how people can do this themselves might be more practical.

[manx]

I would consider actual distribution-native packages of OpenMPT to be more useful. They would of course need to depend on the Wine version provided by a given distribution and integrate nicely.

I am not a huge fan of application-specific cross-distribution packaging that has come into fashion recently. In any case, if the script to generate the package you provided (not in particular only the script that actually runs openmpt, or the generated package itself) is reasonably simple and reliable, if think we might actually be able to include it in the OpenMPT source tree in the contrib directory. There are use cases that it solves.

I honestly do not like step-by-step guides as Saga Musix recommended. All (or at least most of) what should be required to build such packages can easily be automated by a script. Such a script, if written cleanly and clearly,  is also a self-documenting step-by-step guide just by itself.

Other than that, I agree with Saga Musix. Providing such bundles tend to get out of date very quickly and require even more things users have to consider to update their software.

[Saga Musix]

Other than that, I agree with Saga Musix. Providing such bundles tend to get out of date very quickly and require even more things users have to consider to update their software.

Case in point, an OpenMPT update has just been released. But of course this is a minor problem if users don't disable the automatic update notifications in OpenMPT.

[sk1re]

I don't have a script which automatically generates the Wine-OpenMPT package.
Here are the steps to make this package:

1) Compile Wine64 with "./configure --prefix=/home/yourpath/andlocation/ --enable-win64" / and then "make & make install" https://wiki.winehq.org/Building_Wine
2) Gather the required *.so files with this script https://github.com/AppImage/AppImages/blob/master/functions.sh (copy_deps) and copy them to "/home/yourpath/andlocation/libx64"
3) Remove conflicting files also with the functions.sh script (delete_blacklisted)
4) copy the script "Run_OpenMPT.sh" to "/home/yourpath/andlocation/" and copy latest OpenMPT to "/home/yourpath/andlocation/OpenMPT"
5) run the script "Run_OpenMPT.sh".
I did all of this in a Virtual Machine (Qemu or Virtualbox).

You do not have to do all these steps every time because OpenMPT can be updated very easy by just copying the latest OpenMPT into the ./OpenMPT folder of my package. And Wine could be updated every few months. 

[Saga Musix]

Seems simple enough to easily set up by oneself.

[sk1re]

I updated OpenMPT Tracker to version 1.27.05.00 and WINE 3.1 for Linux x64.
http://www.mediafire.com/file/3hzi01w8lsnuncn/OpenMPT_Linux_x64_r02.zip ~143MB

I did the same with WINE 3.1 and "Zynewave Podium Free v3.2.1" DAW.
http://www.mediafire.com/file/2s8dd2z2j3l4ulj/ZynewavePodium_Linux_64_r02.zip ~128,5MB
https://zynewave.com/

[diigitae]

can you explain me how make it with the new version

[diigitae]

i'm on linux librazik 64bits

[diigitae]

i don't manage to do another topic on the forum any chance that opent mpt was port nantive on linux

[Saga Musix]

Eventually, yes. Don't expect it will be done very soon though. It's a whole lot of work, probably years worth of spare-time effort.

[diigitae]

  i understand

[diigitae]

https://github.com/jpcima/AppImage-OpenMPT/releases an appimage up to date by jpcima