[MacPorts] #36560: Use hfsCompression

MacPorts noreply at macports.org
Mon Jan 26 08:15:50 PST 2015


#36560: Use hfsCompression
--------------------------+----------------------
  Reporter:  mfeiri@…     |      Owner:  mfeiri@…
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  base         |    Version:  2.1.99
Resolution:               |   Keywords:  haspatch
      Port:               |
--------------------------+----------------------

Comment (by rjvbertin@…):

 Replying to [comment:24 ryandesign@…]:
 > I suppose modern Macs have many CPU cores and parallel builds often
 cannot
 > build everything in parallel, leaving some cores free some of the time,
 so
 > using hfscompression might not use that much more real time. But I guess

 Exactly.


 > we're only talking about hfscompressing the files that came out of the
 > source tarball, not all the object files getting compiled, so it will
 only
 > shrink the size of a built work directory a small amount.

 In any case, HFS doesn't have transparent compression. So unless/until
 clang is redesigned to write its output leveraging compression (and it
 could just as well use any other form of compression for that), the build
 directory will not be compressed.

 There would be a lot to say to compress the build directory. I often leave
 it and thus the object files around because they appear to be required for
 debugging or even getting a sensible backtrace (with line numbers). And of
 course it allows incremental builds, which speeds up port development
 considerably.

 I'm currently looking at how much one can gain by post-hoc build directory
 compression by creating a (slightly compressed) tarball and then untarring
 it with --hfsCompression (the Qt 5.4.0 out-of-source build directory is a
 brute 26Gb, giving a 5.5Gb .tar.gz2 archive ... and 5.6Gb extracted to a
 hfsCompressed directory :))
 I did get this error: `build/qtbase/src/corelib/global/qconfig.cpp: Cannot
 restore xattr:com.apple.decmpfs` so I going to have to spend another 45min
 or so checking if everything was extracted ...

-- 
Ticket URL: <https://trac.macports.org/ticket/36560#comment:26>
MacPorts <https://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list