Browse code

fix missing TOP_DIR which can break sourcing

There were a couple of places where TOP_DIR is missing when we do a
source of content in tools. Given that working directory can change
quite often during devstack, we need to always be explicit here.

Change-Id: I14b5699637d7f5db745bccf116f440cdcbaa8d91

Sean Dague authored on 2015/02/20 20:10:48
Showing 2 changed files
... ...
@@ -18,7 +18,7 @@ function stack_install_service {
18 18
     if type install_${service} >/dev/null 2>&1; then
19 19
         if [[ -n ${PROJECT_VENV[$service]:-} ]]; then
20 20
             rm -rf ${PROJECT_VENV[$service]}
21
-            source tools/build_venv.sh ${PROJECT_VENV[$service]}
21
+            source $TOP_DIR/tools/build_venv.sh ${PROJECT_VENV[$service]}
22 22
             export PIP_VIRTUAL_ENV=${PROJECT_VENV[$service]:-}
23 23
         fi
24 24
         install_${service}
... ...
@@ -685,7 +685,7 @@ fi
685 685
 
686 686
 # Pre-build some problematic wheels
687 687
 if [[ ! -d ${WHEELHOUSE:-} ]]; then
688
-    source tools/build_wheels.sh
688
+    source $TOP_DIR/tools/build_wheels.sh
689 689
 fi
690 690
 
691 691