blob: 9a110c4ee2a6976b0d3c08aa6cd718c14276773f [file] [log] [blame]
xdc-H10 (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 there is a call to Registry from Text that is not going to be
executed if Registry is not used. There is no need for Text
to use Registry because it is responsibility of the code that
adds modules to Registry to ensure that Registry is used.
However, linker will still try to link Registry_findById and
that will bring in references to Registry data that would be
normally found in the config C file. To prevent that, a NOP
version of Registry_findById is added in the Text template.
This is not going to cause a multiple definition problem
because the linker does not have any reason to bring in
Registry.obj if Registry is not used.
core we don't need to generate macros that are used by Log and
Diags if these are not used in a configuration
MRS