Archive: 2.0b4 huge tempfile during makensis
2.0b4 huge tempfile during makensis
I am using 2.0b4 to make a large installer (~500 MB). I notice that makensis appears to be writing the entire uncompressed archive into a temp file before it finally writes out the final bzipped installer.
Can't the final file just be written out without any temp file being needed?
Is there some option I am unintentionally using that is forcing this behavior?
Furthermore, it is doing the same thing during the install. I install on the D drive but the C drive gets a huge temp file created on in during the install. Ouch -- to install 500 MB of files on one drive I need 500 MB on TWO drives?
That's solid compression. On the compiler side it collects everything it needs as one block and then compresses it along with the headers. On the installer side it's there so it won't have to start over if it needs to extract a file that was already uncompresses in the solid block. You can edit config.h and recompile bzip2 or lzma exeheads without solid compression or just use zlib if you want to avoid this.
Is it possible for you to do the above and make it avaliable to the less technically ept of us please?
I'd like a nonsolid lzma if thats possible.
When NSIS 2 goes final. I don't want to create private builds everytime something changes.
Is there anyone here willing to do a once off compile for me? I am happy with beta5, and this is the only feature I really need.
It'd be much appreciated.