This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Bart, Remy, All, On Monday 12 April 2010 14:28:37 Bart van der Meulen wrote: > The CT_PREFIX_DIR is already being saved and restored, about saving the > complete CT_BUILD_DIR I'm not sure. > > I think that saving the complete CT_BUILD_DIR is to much, for example > when I want to restart at the build at step gcc, I'm no longer > intressed > in the build directories of the companion libs, and binutils. They > have already been build successfully and are there installed installed > in the CT_PREFIX_DIR > (and thus restored). > > This means that if I save / restore the complete CT_BUILD_DIR they > build directories only take up space in the zip-file and time when > saving / restoring them. Yes you are right. Nonetheless, we need a better way to handle that. What about adding a helper function that checks whether the directory to save really exists, and conversely checks that a tarball exists before restoring? I'll handle that. Thanks for your comments. Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |