Cleanup after compile

[dima1236]

Hey Guys,
I have just finished compiling wine, i noticed that after it is finished the disk space usage grow by 1gb, since wine itself uses only ~20-30mb i guess the other disk space is being used by some temp files that were used for the compile process ?

How can i clean them and get my 1gb space back ?


Thanks a lot,
Dima.

[Nagarjuna]

Hey, Dima. Welcome to the forums.

Is this estimated size also counting the dependencies or just WINE it's self (source+binaries)? And just to clarify, I'm guessing you compiled WINE from source, instead of using your distributions package manager? Also, I'm curious as to which distribution you are using.

According to WINE FAQ:

You need approximately 125 megabytes of free hard drive space to store and
compile the source code. Wine also needs about 18 megs in your /tmp
directory.

As far as other software, you will need the following to compile Wine:
- gcc
- Xlibpm

To run Wine, you will need the following:
- The compiled Wine binary
- A properly configured wine.conf and wine.sym
- An installed and working X Window system
- Some MS Windows programs to test

[dima1236]

Hi,
Thank you for the reply,
I am running debian lenny 64bit, and i compiled wine 1.2.2 from source, not sure how they write it requires only 125mb when it required more then 1gb (didn't have enough space at first time)



Dima.

[reed9]

As you surmised, the compiling process does create a lot of files which can eat up space. Usually, when you read a program takes up a certain amount of space, that's just referring to the installed binary.

With WINE, for example, if I look at the Arch package, it shows the compressed package as 13 MB and the installed (uncompressed) size as 111.2 MB.

You can clean up much of the cruft by entering your build directory and doing

make clean