| View previous topic :: View next topic |
| Author |
Message |
Gremo
Guru
Joined: 27 Feb 2006
Posts: 450
|
 Posted: Wed Jun 07, 2006 11:31 am Post subject: kdeenablefinal use flag? |
 |
|
ciao,
ho visto che tutte le applicazioni hanno questa use flag, sul sito di portage leggo:
| Code: |
Makes kde ebuilds use the enable-final flag, yielding big compilation speedups at the cost of very heavy mem usage
|
cosa vuol dire? che ci mette poco a compilare e consuma + memoria (in esecuzione o durante la compilazione?)? |
|
| Back to top |
|
 |
knefas
l33t
Joined: 21 Dec 2003
Posts: 828
|
| Posted: Wed Jun 07, 2006 11:43 am Post subject: |
|
|
Questo e' quello che fa
| Quote: | Concatenates all .cpp files into one big .all_cpp.cpp file, and compiles it in one go, instead of compiling each .cpp file on its own. This makes the whole compilation much faster, and often leads to better optimised code, but it also requires much more memory. And it often results in compilation errors when headers included by different source files clash one with the other, or when using c static functions with the same name in different source files.
This is a good thing to do at packaging time, but of course not for developers, since a change in one file means recompiling everything. |
Traduzione: sbatte tutti i sorgenti in un unico grande file, e lo compila in una botta, invece di compilare ogni sorgente uno a uno. |
|
| Back to top |
|
|
Gremo
Guru
Joined: 27 Feb 2006
Posts: 450
|
| Posted: Wed Jun 07, 2006 11:46 am Post subject: |
|
|
| knefas wrote: | Questo e' quello che fa
| Quote: | Concatenates all .cpp files into one big .all_cpp.cpp file, and compiles it in one go, instead of compiling each .cpp file on its own. This makes the whole compilation much faster, and often leads to better optimised code, but it also requires much more memory. And it often results in compilation errors when headers included by different source files clash one with the other, or when using c static functions with the same name in different source files.
This is a good thing to do at packaging time, but of course not for developers, since a change in one file means recompiling everything. |
Traduzione: sbatte tutti i sorgenti in un unico grande file, e lo compila in una botta, invece di compilare ogni sorgente uno a uno. |
ma sull'uso di memoria (il quando) non ho capito...
cmq sembra essere una buona cosa? |
|
| Back to top |
|
|
Scen
Retired Dev
Joined: 29 Jul 2003
Posts: 2470
Location: Padova, Italy
|
| Posted: Wed Jun 07, 2006 11:57 am Post subject: |
|
|
Usa più memoria poichè il (o i) file che vengono compilati hanno dimensioni maggiori (è come se aprissi un'immagine di 5M invece che una di 500K, la memoria occupata è maggiore nel primo caso).
Se vuoi ridurre i tempi di compilazione dei pacchetti kde, ti cinsiglio di abilitarla, io la uso da tempo e non ho nessun tipo di problema!
_________________
I was born in a deep forest/I wish I could live here all my life/I am made from stones and roots/My home, these woods and roads
All my life I loved this sound/Of the woods all around/Eagles flies where the winds blows free
Journey is my destiny |
|
| Back to top |
|
|
bender86
Guru
Joined: 18 Mar 2005
Posts: 484
|
| Posted: Wed Jun 07, 2006 1:01 pm Post subject: |
|
|
| Usa più memoria solo durante la compilazione. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Forum italiano (Italian)
