Difference between revisions of "Building HDDM support software"
From GlueXWiki
m |
|||
| Line 8: | Line 8: | ||
* objection to standard solution: package creep | * objection to standard solution: package creep | ||
** everyone would need the software to build this | ** everyone would need the software to build this | ||
| − | ** what | + | ** what is needed? |
| − | ** | + | *** yum install perl-XML-Xerces |
| + | *** yum install xalan-c | ||
* schema is authority | * schema is authority | ||
** outside world sees w3c standard | ** outside world sees w3c standard | ||
| − | ** schema can be richer | + | ** schema can be richer than hddm |
| − | *** | + | ** hddm much easier to work with |
| + | *** introduces merging problem | ||
*** current schema does not take advantage of this | *** current schema does not take advantage of this | ||
*** cross that bridge when we come to it | *** cross that bridge when we come to it | ||
Revision as of 14:10, 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 is needed?
- yum install perl-XML-Xerces
- yum install xalan-c
- schema is authority
- outside world sees w3c standard
- schema can be richer than hddm
- hddm much easier to work with
- introduces merging problem
- current schema does not take advantage of this
- cross that bridge when we come to it
