slimming down ISE install

M

Mike Harrison

Guest
Just installed ISE webpack 13.3 on my laptop and things are getting a bit tight space-wise - a lot
of space (several gb) appears to be used by files for device families I'll never use, but removing
the dirs makes the software bork.

There's presumably a file/dir list somewhere telling it what to look for - has anyone figured out
where this is ?

Removing the EDK dir is the only thing I've found so far that appears not to break anything
 
Mike Harrison wrote:
Just installed ISE webpack 13.3 on my laptop and things are getting a bit tight space-wise - a lot
of space (several gb) appears to be used by files for device families I'll never use, but removing
the dirs makes the software bork.

There's presumably a file/dir list somewhere telling it what to look for - has anyone figured out
where this is ?

Removing the EDK dir is the only thing I've found so far that appears not to break anything
If you spend more than an hour for slimming down the installation, it is
cheaper to buy an external hard disk.

--
Frank Buss, http://www.frank-buss.de
piano and more: http://www.youtube.com/user/frankbuss
 
On Wed, 04 Jan 2012 13:06:42 -0000, Frank Buss <fb@frank-buss.de> wrote:

If you spend more than an hour for slimming down the installation, it is
cheaper to buy an external hard disk.
Agreed. I have both ISE and Quartus installed on a 16G pen drive. Under
Linux I just bind it to /opt and everything's happy. Surprisingly it
doesn't seem to hurt performance noticeably either.
 
Mike Harrison <mike@whitewing.co.uk> wrote:

Just installed ISE webpack 13.3 on my laptop and things are getting a
bit tight space-wise - a lot of space (several gb) appears to be
used by files for device families I'll never use, but removing the
dirs makes the software bork.
On the all-too-small SSD in my laptop, I have enabled the built-in
transparent folder compression in Windows for the Xilinx folder. This
reduces the size of the ISE 10.1 (old, I know) installation from 9.4GB
to 5.6GB. I expect something similar could be done on Linux.

I didn't measure the impact on performance, but since synthesis and P&R
are mainly CPU intensive, not disk I/O intensive, I've assumed it is not
significant.


Regards,

Laust
 

Welcome to EDABoard.com

Sponsor

Back
Top