You are here > Forums > General discussion > [question] how-to create .pol from source / compile fr

The forum

[question] how-to create .pol from source / compile

New topic  - Reply
Author Replies
fekir Wednesday 21 September 2011 at 17:45 - [Quote]

Rank: Member

I was searching for a tutorial for compiling wine and running it from source.
If I "simply" do ./configure && make i obtain a directory that 200mb.

I noticed that the .pol packages are ca 75mb heavy, so I was asking myself how you do it, and it is possible to run wine from the pol package without having wine installed...

if i do make clean my directory occupies ca 125mb and I can't run wine from source...

thanks to everyone!
Quentin PÂRIS Wednesday 21 September 2011 at 22:20 - [Quote]

Rank: Admin

Admin

You can build wine like this :

./configure --prefix=/
make
make install DESTDIR="$HOME/.PlayOnLinux/wine/linux-x86/version-name"
fekir Friday 23 September 2011 at 22:09 - [Quote]

Rank: Member

thank you, I'll try
fekir Sunday 25 September 2011 at 12:48 - [Quote]

Rank: Member

if I want to remove the installed package I just need to remove "$HOME/.PlayOnLinux/wine/linux-x86/version-name" , right?
Quentin PÂRIS Sunday 25 September 2011 at 12:58 - [Quote]

Rank: Admin

Admin

yep
fekir Sunday 25 September 2011 at 14:03 - [Quote]

Rank: Member

ok, now I'm compiling, I'll check after "make install" how much space it'll take.

Because I have more than one user on my laptop I would like to "install" different versions of wine (and after it some windows-programs) under /opt, so i thought I could do

./configure --prefix=/
make
make install DESTDIR="/opt/wine-version"

or is it

./configure --prefix=/opt/wine-version
make
make install

better? are there any difference?

thank you very much Tinou
Quentin PÂRIS Sunday 25 September 2011 at 14:47 - [Quote]

Rank: Admin

Admin

I think that the second one is better, but with the first one, you can choose where to install after building
fekir Sunday 25 September 2011 at 19:34 - [Quote]

Rank: Member

Ok, thanks

Now I've tried to install the package as you wrote before, I do not have Playonlinux installed so the only thing under the directory .Playonlinux is the wine version i just installed and it is ca 200mb big, if I download a .pol file and unzip it it's only 90mb big, ca. the half; am I doing something wrong? Are there some files that you have removed? Or how is it possible?
fekir Sunday 25 September 2011 at 21:09 - [Quote]

Rank: Member

doing some more research I've noticed that in my /lib/wine directory I have 177mb of things in ca. 600 files, in the /lib/wine directory of the unzipped .pol file I have 68mb of things in ca. 550 files...

edit: using meld I can view the differences between the two directories, is it somehow possible to save in a text file the result so that I can post it here?

And, (this would be the last question) what do you think would be the best way for doing a package for different wine versions that installs them in /opt and creates a link in bin?

For example I would like to run from the terminal "wine1.1.38" and the 1.1.38 wine versions under opt would be called...

I only managed to do packages with checkinstall, but I don't know how to insert the link in bin and add the needed dependencies for running wine (I think I'll need the same dependencies of the normal wine package...

again: thank you very much for all the help you gave me!

Edited by fekir

Quentin PÂRIS Sunday 25 September 2011 at 22:18 - [Quote]

Rank: Admin

Admin

Yep, it's normal. Our building server also clean the build and remove developement files

A symbolic link should work yes
fekir Sunday 25 September 2011 at 22:28 - [Quote]

Rank: Member

Quote from Tinou:

Our building server also clean the build and remove developement files

Ah, ok, does it exists some sort of guide/documentation that explains what I could clean?

Quote from Tinou:

A symbolic link should work yes

Again: do you know where I could learn from? Some sort of guide/documentation?
Until now I only used checkinstall for making packages, I have no idea how I could modify one (adding a symlink and where to write the dependencies...)
Il n'y a rien à voir ici