Quartus tcl can't load package when root directory changed
Hello!
I'm trying to automate builds on a virtual windows machine/ Bamboo build server. All our dev tools (IDEs, GCC, Segger tools, etc.) are installed in a 'toolchain' folder during the build, and then I have a batch file that runs the makefile, the quartus shell script to generate .pof files, etc. All works as expected on my local machine, but I'm having a heck of a time getting it to build on Bamboo. I seem really close (tool installs, makefile runs, etc.), but the .tcl scripts hit an error where, for example, the fitter breaks by not being able to find the 'report' module when doing the line "load_package report".
The problem seems to be that the quartus path is not the default C:\IntelFPGA_lite... etc. , but rather a different (and relative) toolchain folder ( %CURRENT_DIR%\..\..\toolchain\quartus\20.1\quartus\bin64 for example). I can recreate the error on my local machine by pointing my Quartus directory and QUARTUS_ROOTDIR to the toolchain folder; the errors don't happen if that folder is the default C:\IntelFPGA_lite\20.1\quartus\20.1 path.
I do set the environmental variable for QUARTUS_ROOTDIR, and I confirm that my code does change that. Everything seems to be found and triggered correctly, except that it can't find/ load the packages.
Is there something I'm missing that Quartus needs to not be in the default installation spot? If we absolutely have to, we can install Quartus on the build server, but we'd rather not.
Thanks! Scott