[Lsb-infrastructure] [Bug 2957] New: build_env/headers should support rebuild of all stuff related to particular header

[bugzilla-daemon at linux-foundation.org]

http://bugs.linuxbase.org/show_bug.cgi?id=2957

           Summary: build_env/headers should support rebuild of all stuff
                    related to particular header
           Product: Infrastructure
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Database
        AssignedTo: mats at freestandards.org
        ReportedBy: silakov at ispras.ru
         QAContact: lsb-infrastructure at freestandards.org


Created an attachment (id=1694)
 --> (http://bugs.linuxbase.org/attachment.cgi?id=1694)
Patch for build_env/headers/makefile

During different fixes and improvements, we often perform db data modifications
that require regeneration of particular header. However, while it is easy to
regenerate the header itself, build_env/headers/makefile doesn't provide a way
to regenerate all corresponding *defs files, and complete regeneration takes
significant time.

The patch attached will add a new target - "%.h-defs". If one invokes "make" to
make such a target (e.g., `make time.h-defs` or `make GL/gl.h-defs`), all
appropriate *defs files will be regenerated unconditionally, as well as the
header itself.

Implementation is probably not very graceful, since it reinvokes the 'make'
utility explicitly. However, I've found it to be rather tricky to implement
this using 'usual' dependencies (more particularly, it's not easy to deal with
slashes in our targets, since "make" is too smart in this area and we already
have some tricks with LSB versions, architecture names and slashes).

If someone can suggest more beautiful name for the target (i.e., something
instead of adding '-defs' suffix to the header name), feel free to update the
patch:)

-- 
Configure bugmail: http://bugs.linuxbase.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.