distribute a compiled wine version on linux

thebuck · Post by **thebuck** » Wed Sep 17, 2008 3:00 pm

hello,
i want to know what problems can appear if i compile wine on my opensuse 11 linux, and then i give it to other linux users with other distros of linux. will that work good, bad or perfectly, for others?
what can be a problem?

thx for your answers.

edit: im talking about a 32bit compiled wine version. 64 bit will cause major problems.

rockinup1231 · Post by **rockinup1231** » Thu Sep 18, 2008 9:03 am

Well, even if you are compiling a 32 bit copy, it won't work on a 64-bit machine.

If you fail to meet all the dependancies that Wine requires in order to compile them, when you run ./configure, it will tell you at the end if you are missing any necessary devel files.

A successful compilation of Wine will run like any pre-packaged copy made by the Wine developers, except it will run a bit faster on the machine it was compiled on than the pre-packaged ones. If you plan to compile and give the program to others though, they won't reap the same performance benefits.

Unless you plan to build a patched copy of Wine for others, I can't see why you'd want to anyway.

thebuck · Post by **thebuck** » Thu Sep 18, 2008 1:35 pm

rockinup1231 wrote:Well, even if you are compiling a 32 bit copy, it won't work on a 64-bit machine.

it wokrs fine, im having 32bit opensuse and 64 bit opensuse. i allready have a little survey, my patched wine is compiled on opensuse32bit.
it runs on my opensuse 64bit on debian32bit and on ubuntu32bit.
and yes i distribute a patched wine version because it is a little tricky to do and it makes others happy.

that performance lost, why is that so can you explain that to me please?

i seen that the shellscripts in wine/bin include some folders from the pc it was compiled once. but until now i never had problems with that differences.

vitamin · Post by **vitamin** » Thu Sep 18, 2008 2:04 pm

rockinup1231 wrote:Well, even if you are compiling a 32 bit copy, it won't work on a 64-bit machine.

Wrong. With all required 32-bit libraries installed it will work just fine. Besides you can't even compile Wine as 64-bit.

rockinup1231 wrote:A successful compilation of Wine will run like any pre-packaged copy made by the Wine developers, except it will run a bit faster on the machine it was compiled on than the pre-packaged ones. If you plan to compile and give the program to others though, they won't reap the same performance benefits.

Wrong again. Just compiling Wine (or any other program) yourself does not magically make it faster.

thebuck · Post by **thebuck** » Thu Sep 18, 2008 2:23 pm

so there is nothing i have to worrie when people using my self compiled wine binarys?

what about the law? what can i do wrong if i just release all for free?

vitamin · Post by **vitamin** » Thu Sep 18, 2008 3:18 pm

thebuck wrote:so there is nothing i have to worrie when people using my self compiled wine binarys?

Usually you need separate package for each distro, each distro version. If you proposing everyone to use your single Wine package - then it just won't work.

thebuck wrote:what about the law? what can i do wrong if i just release all for free?

You can do whatever you want with Wine, as long as you provide all the patches you applied to it. So anyone will be able to get official Wine, apply these patches and get exactly the same binary.

Gert van den Berg · Post by **Gert van den Berg** » Thu Sep 18, 2008 3:28 pm

On Thu, Sep 18, 2008 at 9:23 PM, thebuck <[email protected]> wrote:

so there is nothing i have to worrie when people using my self compiled binarys?

Some programs provide targets in the makefile to build packages, I did
not see any quickly in Wine's case... (Finding the scripts used to
generate the packages on WineHQ should help a lot...)

https://help.ubuntu.com/community/Build ... ild%20Wine
seems to include instructions on creating a debian package...

what about the law? what can i do wrong?

1. I'm not a lawyer...

You should distribute the source code of the modified version with
it... (With the LGPL it is not necessary to include independent
stuff's code (such as DLLs that is not derived from Wine's version,
etc))

You may probably not include Microsoft DLL's, other software with your
distribution... (In most cases...)

Gert