Difference between revisions of "Building HDDM support software"

From GlueXWiki
Jump to: navigation, search
 
m
Line 4: Line 4:
 
** tools for building .c and .h are not generally created (expert-only operation)
 
** tools for building .c and .h are not generally created (expert-only operation)
 
** because of checkout order, makefile can fail
 
** because of checkout order, makefile can fail
* schema is authority
 
** outside world sees w3c standard
 
** schema can be richer
 
*** introduced merging problem
 
*** current schema does not take advantage of this
 
*** cross that bridge when we come to it
 
 
* standard solution: check out the authority, make the dependent file
 
* standard solution: check out the authority, make the dependent file
 
** need to build the tools to do this
 
** need to build the tools to do this
Line 16: Line 10:
 
** what perl module is needed?
 
** what perl module is needed?
 
** is it needed for hddm-xml?
 
** is it needed for hddm-xml?
 +
* schema is authority
 +
** outside world sees w3c standard
 +
** schema can be richer
 +
*** introduced merging problem
 +
*** current schema does not take advantage of this
 +
*** cross that bridge when we come to it

Revision as of 13:35, 11 February 2009

  • would like to avoid inconsistency between event.xsd and hddm_s.c, .h
    • .c and .h are made from the .xsd
    • currently both are checked in
    • tools for building .c and .h are not generally created (expert-only operation)
    • because of checkout order, makefile can fail
  • standard solution: check out the authority, make the dependent file
    • need to build the tools to do this
  • objection to standard solution: package creep
    • everyone would need the software to build this
    • what perl module is needed?
    • is it needed for hddm-xml?
  • schema is authority
    • outside world sees w3c standard
    • schema can be richer
      • introduced merging problem
      • current schema does not take advantage of this
      • cross that bridge when we come to it