pdrApp notes

Last update: 13-Aug-2001 13:18:59 -0700

Package status:

Package	Tags									Pending Tasks	Who
Package	Release			Release	Rel	Rel	Release			Pending Tasks	Who
pdrApp	v3r2	p1	p2	v3r3	v4	v4r1	v6	v6r1	v6r2
GuiSvc	v2r1			v2r1	v2r1		v2r3
analysis	v3			v3	v3		v3r1
merit	v3			v3r1	v3r1	v3r2	v3r4
idents	v2			v2	v2		v2r1	v2r2
xml	v3			v3	v3		v3r1
flux	v4			v4r1	v4r1		v4r10
FluxSvc	v2r1			v2r2	v2r3		v2r8	v2r9
data	v4			v4	v4
GlastEvent	v2r1			v2r2	v2r2	v2r3	v2r4			Needs lat, lon in event header. Must update MCEvent class.	Toby
instrument	v3r1		p2	v3r2	v3r3		v3r7
GlastSvc	v2r1			v2r1	v2r1		v2r2				Toby
glastmedia	v4r1		p2	v4r2	v4r3		x
GismoGenerator	v2r1		p2	v2r2	v2r3	v2r4	v3r5		v4		Toby
ntupleWriterSvc	v1			v1r1	v1r2	v1r5	v1r6				Heather
trigger	v1			v1r1	v1r2		v1r5
GlastDigi	v0r5			v0r5	v0r5		v1			(Why use GaudiAud and RootHistConv?)
TkrRecon	v1r6	p1	p2	v1r7	v2	v2r1	v2r5		v2r6
CalRecon	v1r9		p2	v1r10	v2	v2r1	v2r3
acdRecon	v1r1	p1		v1r2	v2		v2r2	v2r3		recon display	Heather
gismosys								v5r2
reconRootData								v2
digiRootData								v2r6
glastRootIO								v1r5

Notes:

The subsequent Release columns are "patches": incremental releases with the given package. Append the p1 etc. to the release tag. (Note that pdrApp v3r2p2 is actually a branch tag to allow the head to be modified independently.)
Next is the tag that will be applied for the next release shown. This column represents the development version, corresponding to the HEAD of the given packages. This is the way packages are checked out in the c:\common\pdr_dev area on the UW TS.

Enabling Win32 (non-debug)

The VCMT "Release" radio button changes the CMT tag from Win32 to Win32Debug. This did not work, since the CMT tag "VisualC" was not set by the tag. We have made, and retagged, this small correction to GaudiPolicy.

While we were at it, we modified and retagged several other requirements files, to correct an initial mistake. We no longer use the pattern package_Llinkopts: all such have been replaced by package_linkopts, resolving (now) to the same library link instructions. Also, the package_include pattern now generates an include_dirs macro.

Using release mode.

The current release package have been compiled in both modes, with binaries in the Win32 and Win32Debug folders. To do this, it is necessary to setup packages: the VS files and setup.bat are either, not both. But for execution, the only setup.bat file that counts is the one in the execution package, e.g. pdrApp.