Sometimes this bitbake class gets created and put in the ($TMPDIR}/classes directory by a project when the project is initially imported in Montavista DevRocket. The class appears to create a file for each .bb package with the same package name (but not .bb extension) with many of the typical variables the .bb file defines put in the created file in the format variable name = value. These created files are put in the ($TMPDIR}\export directory. It appears that a build works ok and produces the expected executable regardless of whether this exportvars.bbclass gets created or not. The project appears to be the top level project and when it is imported the bitbake files it references get parsed and if all these are available it produces this exportvars.bbclass. If not everything is available at that time it does not produce that .bbclass even when a refresh is done. My question is since the build appears to work either way, is this .bbclass for aid in debugging or why is is created. I'll try to post the exportvars.bbclass and a few of the files created in that export directory. Also I can't seem to find anything referencing that exportvars.bbclass but may not necessarily be looking in the right places. I attempted to gain access to Montavistas forum but received an e-mail from them to the effect I needed a support contract to get access (I'm doing some work many years after the initial dev completed so no longer have a support license)

the exportvars.bbclass contains the following

# This file is generated by DevRocket
# Do not modify or delete this file
EXPORTVARS ?= "PN PE PV PR SECTION PRIORITY HOMEPAGE SRC_URI LICENSE DESCRIPTION DEPENDS RDEPENDS FILE S B P WORKDIR PACKAGES PROVIDES RPROVIDES RRECOMMENDS"
EXPORTVARSDIR ?= "${TMPDIR}/export/"
EXPORTVARSFILE ?= "${EXPORTVARSDIR}/${PN}-${PV}"
EXPORTCOLLSFILE ?= "${EXPORTVARSDIR}/collections-mapping"


python () {

evrecpietype = set(bb.data.getVar("__inherit_cache",d,1))
evcollectioninfo = get_collection(d.getVar('FILE', 1), d)
bb.mkdirhier(bb.data.expand("${EXPORTVARSDIR}",d))

collfile = open(bb.data.expand("${EXPORTCOLLSFILE}",d), "a")
collfile.write('PN="%s",' % bb.data.getVar('PN', d, 1))
collfile.write('PE="%s",' % bb.data.getVar('PE', d, 1))
collfile.write('PV="%s",' % bb.data.getVar('PV', d, 1))
collfile.write('PR="%s",' % bb.data.getVar('PR', d, 1))
collfile.write('FILE="%s",' % bb.data.getVar('FILE', d, 1))
collfile.write('PACKAGES="%s",' % bb.data.getVar('PACKAGES', d, 1))
if evcollectioninfo:
collfile.write('COLLECTION="%s"\n' % evcollectioninfo["name"])
else:
collfile.write('COLLECTION="%s"\n' % "")
collfile.close()

evfile = open(bb.data.expand("${EXPORTVARSFILE}",d), "w")
if evcollectioninfo:
evfile.write('COLLECTION="%s"\n' % evcollectioninfo["name"])
else:
evfile.write('COLLECTION="%s"\n' % "")

for expvar in bb.data.getVar("EXPORTVARS",d,1).split(" "):
evfile.write('%s="%s"\n' % (expvar, bb.data.getVar(expvar,d,1)))
evfile.close()

}


and a file it created for one of the packages that it puts in the export directory is
cpio-2.5

COLLECTION="com.mvista.core"
PN="cpio"
PE="None"
PV="2.5"
PR="r4"
SECTION="console"
PRIORITY="optional"
HOMEPAGE="http://www.gnu.org/software/cpio/"
SRC_URI="ftp://ftp.gnu.org/gnu/cpio/cpio-2.5.tar.gz file://install.patch;patch=1"
LICENSE="GPL"
DESCRIPTION="GNU cpio is a program to manage archives of files."
DEPENDS="gnu-config-native libtool-cross autoconf-native automake-native libtool-native shasum-native coreutils-native virtual/i686-montavista-linux-gnu-gcc virtual/libc texinfo-native "
RDEPENDS=""
FILE="/export/share/DiuIntegrationPlatform/tmp/collections/core-1006170220/core/recipes/cpio/cpio_2.5.bb"
S="/export/share/DiuIntegrationPlatform/tmp/work/i686-mv-linux/cpio-2.5-r4/cpio-2.5"
B="/export/share/DiuIntegrationPlatform/tmp/work/i686-mv-linux/cpio-2.5-r4/cpio-2.5"
P="cpio-2.5"
WORKDIR="/export/share/DiuIntegrationPlatform/tmp/work/i686-mv-linux/cpio-2.5-r4"
PACKAGES="cpio-dbg cpio cpio-doc cpio-dev cpio-static cpio-locale"
PROVIDES="cpio-2.5 cpio-2.5-r4 cpio "
RPROVIDES=""
RRECOMMENDS="None"




Greg