On the road for the next couple of weeks so I'm a little limited in my ability to answer questions
On Friday, November 20, 2015, Erich Steinböck <[email protected]> wrote: > I'm seeing quite a few Rexx Error Message files in trunk, and a lot of > them state, that they are being built automatically, e. g. > > > - interpreter\platform\unix\rexx.cat file is generated by build > process > - interpreter\messages\errnums.xml > - interpreter\messages\gencat.inp file is generated by build > process > - interpreter\messages\RexxErrorCodes.h FILE WAS GENERATED BY > genrxmsg > - interpreter\messages\RexxMessageNumbers.h file is generated by > build process > - interpreter\messages\rexxmsg.xml When this file is updated, cmake > will update the various header files used for error messages > - main\trunk\api\oorexxerrors.h FILE WAS GENERATED BY genrxmsg > > > How is cmake supposed to generate rexxmsg.xml? > This is the master error message file. It is not generated bur all other files are generated from the information it contains > Which part of build does/should build rexx.cat, gencat.inp, and > RexxMessageNumber.h? > These should be generated automatically any time rexxmsg.xml is changed > Where can we find the mentioned genrxmsg tool? > This does not exist any more. > In short: what's the correct procedure to update an error message text? > Change rexxmsg.xml, run the build, check in the new generated files. This requires a serves installation. > I'm thinking of changing the errnums.xml XML code so that it uses less > space within the rexxref, but I want to make sure it is up-to-date re all > the the other files. > This is done by changing the xslt style sheet used to generate the file > Erich >
------------------------------------------------------------------------------
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
