README

             xdc-H07 (corevers:16.0.2.0; B:200,G:200,R:200)

                       eXpanDed C Tools (XDCtools)

    This tree contains the RTSC build and configuration engines for
    target content. The tree is used in XDCtools 3.60 product releases where
    we implemented some changes that allow for smaller config C files.

Librarian repo creation
-----------------------
    The xdc.git repo was created to "track" the repo maintained at 
    eclipse.org and was created as follows:
        git clone --bare ssh://git.eclipse.org/gitroot/rtsc/org.eclipse.rtsc.xdccore.git xdc.git
	cd xdc.git
        git config remote.origin.fetch "+refs/heads/*:refs/heads/*"

BUILD

    o setup ssh to enable "git" from xlibrary as "dr" (if necessary) 
	cd ~xlibrary/.ssh
	cp -f config-dr config

    o fetch the latest changes from the Eclipse git server
	cd xdc.git
	git fetch

    o Build this tree from Linux using standard SM-MAKE
 
        # clone the tree and merge/review user content
        ggentree -u sascha@ti.com xdc.git/
        cd xdc-H??

	# unzip build.zip from the last released tree
	unzip ../xdc-H??/build.zip

        # make sure the user email and name are your eclipse credentials 
        git merge origin/xdccore-H-dr

        # build the tree on Linux
        SM-MAKE .clean
        SM-MAKE .all-files >& Make.log 

        # update README 
        emacs README
        git commit -a -m xdc-H??

        # release the tree
        greltree -m "something brief and meaningful"

    o to build only packages in src/packages from scratch:

    	SM-MAKE .xdc-packages

    o to build bundles:

    	SM-MAKE .bundles


==============================================================

ADDITIONS

DELETIONS

CHANGES

xdc.runtime Text.nameStatic was not used at all because we couldn't separate
	    the case when a name wasn't given to an instance and the case when
	    Text.charTab was not loaded. At the time the names are allocated
	    to Text.charTab we already know that Text.charTab is not loaded so
	    we don't bother adding instance names to Text.charTab. This change
	    will separate the case where the name is NULL and Text.charTab is
	    loaded, and that's when we know NULL means the instance does not
	    have a name. The case when the name is NULL and Text.charTab is not
	    loaded is still ambiguous. The message will say that the instance
	    is static, which is true, but we can't tell if the name is given to
	    the instance. Anything further than this would require a special
	    value for the case of the name not being NULL, but Text.charTab is
	    not loaded. However, this doesn't seem to be worthy of much
	    attention because no one ever noticed that Text.nameStatic was not
	    working at all.

	    added FMEA document to docs

core	    Module_state section names for clang are changed to start with
	    ".data:"

*	    more MISRA changes
 
MRS