Skip to contentSkip to conversation

Out of tree build yocto dylan

DISCUSSION Volker Vogelhuber 2 participants 3 messages Oct 28, 2013 – Oct 29, 2013

lore
Share & tools
lore
#0 lore raw

I'm currently trying to have the TMPDIR moved out of the normal repository path under dylan.
If I set it to
TMPDIR = "${TOPDIR}/../../build/tmp"
some of the build recipes fail because of the dots (e.g. mkdir-p.pl in openssl and ti-dsp-link from the meta-ti repository). I fixed it by adding a require conf/gettmpdir.inc containing the following code:

def gettmpdir(d):

    return os.path.abspath(d.getVar("TOPDIR", True) + "/../../build/tmp");

and set the TMPDIR within the local.conf now to TMPDIR = "${@gettmpdir(d)}"
But I wonder if it wouldn't be a good idea to introduce a call to os.path.abspath on the TMPDIR in general.

#1 lore raw
Quoted 3 lines · Volker Vogelhuber

I'm currently trying to have the TMPDIR moved out of the normal repository path under dylan. If I set it to
TMPDIR = "${TOPDIR}/../../build/tmp"

Does it work better if you use an absolute path (you can use the same TMPDIR location, just specify it absolutely, instead of relatively)?

#2 lore raw
Quoted 8 lines · Trevor Woerner
Quoted 3 lines · Volker Vogelhuber

I'm currently trying to have the TMPDIR moved out of the normal repository path under dylan. If I set it to
TMPDIR = "${TOPDIR}/../../build/tmp"

Does it work better if you use an absolute path (you can use the same TMPDIR location, just specify it absolutely, instead of relatively)?

Sure it would work too, but I don't want to specify the path in an absolute way because we have the toolchain in a mercurial repository, and other developers may have checked out the toolchain in another path, so specifying it in an absolute way is no way to go.