blob: 3dc45f723631efe54c21fd2fc2895950e791ffbe [file] [log] [blame]
xdc-H14 (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
xdc.runtime initial draft of xdc.runtime architecture
DELETIONS
CHANGES
core extern function declarations and function type casts were
causing Klocwork to emit MISRA.FUNC.UNNAMED.PARAMS because they
were missing argument names. Extern types now have argument names
and when the casts are generated, the names are added.
xdc.runtime removed another usage of the type Instance_State, and replaced it
with Object
if Core.noAssert is false, we need to load Assert, but if we do it
in Core.module$use, it's too early because SYS/BIOS still has a
chance to set it to true, and then we can't unload Assert. That
code is now in package.close(), which happens late in the
configuration.
Error also had a check for Core.noAssert because that was a
stand-in for a parameter that says that xdc.runtime is rebuilt in
a SYS/BIOS build. If xdc.runtime is not rebuilt, and the runtime
library is an older one then we need to load Log and Diags.
However, this check is redundant because if noAsserts is false,
the check in package.close() will load Assert, which then loads
Log and Diags.
MRS