blob: 9623e937d44380a9bb48cc0317a10ba63c79d80a [file] [log] [blame]
xdc-G03 (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.5? product releases in
which all targets are 64-bit.
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-G??
# unzip build.zip from the last released tree
unzip ../xdc-G??/build.zip
# make sure the user email and name are your eclipse credentials
git merge origin/xdccore-G-dr
# build the tree using LSF to force older GLIBC to be used when
# linking Linux executables
SM-MAKE .clean
SM-MAKE .all-files >& Make.log
# update README
emacs README
git commit -a -m xdc-G??
# release the tree
greltree -m "something brief and meaningful"
o to make both the UNIX and PC sides, from a Linux workstation, go to the
top directory of the tree and type:
SM-MAKE .all-files
To clean the tree, type:
SM-MAKE .clean
o to build only packages in src/packages from scratch:
SM-MAKE .xdc-packages
o to build bundles:
SM-MAKE .bundles
o to run regressions:
SM-MAKE .regress
==============================================================
ADDITIONS
DELETIONS
CHANGES
xdc.runtime Log-related and Assert-related module config parameter are assigned
the value NOGEN, when the modules Log and Assert are not used.
That value signalizes to the code that generates config C file that
the constants corresponding to these config parameters should not
be generated.
core for parameters whose value is encoded, we now check if the value
is NOGEN. Previously only parameters that re not encoded could use
NOGEN to prevent the generation of the corresponding constants
MRS