| stuartc |
Mardi 13 Aoüt 2013 à 10:26
|
stuartc
|
I've recently been enjoying experimenting with custom builds of Wine, applying patches etc.
I've noticed that the pre-packaged versions of Wine (that PoL provide) have a whole hoard of linked libraries in the libs folder, versus building Wine by hand you only get libwine.so.
Is this something that is done by hand by the PoL guys, or is there something I can do myself?
I'd really like to have all the required libs bundled inside the --prefix path I choose.
Any advice would be helpful.
|
| Ronin DUSETTE |
Mercredi 14 Aoüt 2013 à 18:13
|
Ronin DUSETTE
|
Its automatically done via our server. As for the libs, thats not really how it works. The folders in the POL builds are just the main binaries needed, so for instance, if you ./configure, make depend, make, make install, it will compile it and you can drag those folders our of your custom build. When I would build a version to test, I would build a 32 bit chroot, and do it there. The key that I forgot a lot was to have the dependencies for the build. So, with sudo apt-get build-dep wine, it will pull everything you need to build wine. Then, when you configure your source, you can use the prefix option to tell it where to install to, and you will have your custom build of Wine that can be used in a POL wineprefix.
|
| petch |
Mercredi 14 Aoüt 2013 à 19:33
|
petch
|
PoL Wine packages rely on system libraries as much as possible, but some libraries may not be commonly available on all distros, or not the right versions, in which case they'd better be bundled in the packages. I think those extra libs are added to the packages after compilation. They're a subset of the dependencies of Wine, just copied from the build server distribution (hence Debian). Again, only MulX or Tinou can provide an authoritative answer on what happens exactly ;)
|
| stuartc |
Jeudi 15 Aoüt 2013 à 14:38
|
stuartc
|
Thanks guys, that helps.
There seems to be an almost exhaustive list (in one shape or another) of i386 lib deps on the WineOn64bit wiki page: http://wiki.winehq.org/WineOn64bit
I guess I'll need to play with the build system to see if I copy those required libs into the compiled prefix they will be used without having to rebuild with different arguments.
|
| booman |
Lundi 19 Aoüt 2013 à 20:28
|
booman
|
I tried compiling my first patched version of Wine and found that a BUNCH of dependencies were missing. When I tried to apt-get install them... they were not found. I ended up requesting a patched Wine version from PlayOnLinux devs. But I still wonder how to install those dependencies so I could compile myself. I honestly just wanted to test a patch before requesting it in the Wine Manager.
|
| stuartc |
Mardi 20 Aoüt 2013 à 16:00
|
stuartc
|
Its automatically done via our server.
Still not sure how though... Unfortunately I'm a noob with C build systems. If you end up making some headway, it would be great to know what you come up with! :) |
| Ronin DUSETTE |
Mercredi 21 Aoüt 2013 à 19:07
|
Ronin DUSETTE
|
All you have to do is put in a Feature Request in our Bug section with the following: version and architecture of wine to use link to patch to be applied what the patch does/fixes steps taken to compile (dependencies you needed, make depend or just make, etc) name of final compiled wine version to be used or, if you know how to use github, PlayOnLinux is on there, and you can file it there. Its much simpler if you are not used to github and creating pull requests to just file a feature request on our bug site with the above information. Its an automated process, BUT, one of the lead devs has to push the changes through to the server, which can take a while. Put in the request, and be patient, and it will surely be build and added to our list of Wine versions in POL. :)
|
| booman |
Mercredi 21 Aoüt 2013 à 19:17
|
booman
|
Thanks DJ, I don't mind doing a request, actually thats what I did to get Crysis running... Finally! But the "geek" in me still wanted to try compiling and patching myself too.
|