Re: [Boost-bugs] [Boost C++ Libraries] #7576: bjam/qt4: Allow extra flags for rcc

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #7576: bjam/qt4: Allow extra flags for rcc
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-11-21 10:49:34

#7576: bjam/qt4: Allow extra flags for rcc
---------------------------------------+------------------------------------
  Reporter:  frank.richter@…           |       Owner:  vladimir_prus
      Type:  Feature Requests          |      Status:  new          
 Milestone:  To Be Determined          |   Component:  build        
   Version:  Boost 1.51.0              |    Severity:  Optimization 
Resolution:                            |    Keywords:               
---------------------------------------+------------------------------------

Comment (by frank.richter@…):

 Example, easy:
 {{{
 project my-qt-project :
                 requirements
                 <rccflags>"-compress 9 -threshold 10"
             ;
 }}}
 ...enables more aggressive resource compression.

 Documentation: what about:
 {{{
 --- qt4.jam.org 2012-10-26 10:43:46.602132564 +0200
 +++ qt4.jam     2012-11-21 11:43:14.794037086 +0100
 @@ -35,6 +35,21 @@
  #
  # This is consistent with Qt guidelines:
  # http://doc.trolltech.com/4.0/moc.html

 +#
 +# The .qrc processing utility supports various command line option (see
 +# http://qt-project.org/doc/qt-4.8/rcc.html for a complete list). The
 +# module provides default arguments for the "output file" and
 +# "initialization function name" options. Other options can be set
 through
 +# the <rccflags> build property. E.g. if you wish the compression
 settings
 +# to be more aggressive than the defaults, you can apply them too all
 .qrc
 +# files like this:
 +#
 +#   project my-qt-project :
 +#               requirements
 +#               <rccflags>"-compress 9 -threshold 10"
 +#           ;
 +#
 +# Of course, this property can also be specified on individual targets.

  import modules ;
  import feature ;
 }}}

 Tests: can do (probably) — just didn't really write any test at all for
 bjam yet.

 Looking back at the change, it might be better to put `$(OPTIONS)` _after_
 `-name $(>:B)`, as that would allow the user to override the default
 initialization function name – useful in case multiple `.qrc` files with
 the same name occur in a project. Or perhaps only if tastes differ. (Note
 the documentation snippet above is does not consider this alteration.)

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/7576#comment:2>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.