NewsArchive
05-03-2012, 02:25 AM
Hi Friedrich,
I just noticed something weird. I use a #copy file action in all my scripts
to copy my installs to a product folder on my server so I can have easy
access to them from anywhere on the LAN.
I've recently built a "template" to use with new products and instead of
hard coding the destination I used:
T:\Installs\_Icetips\[IT_PRODNAME]\[EXENAME]
Both IT_PRODNAME and EXENAME come from Build Automator and they work
perfectly anywhere else in the install as far as I can tell (I use the
IT_PRODNAME in several places)
But when I use the compiler variables in the #copy file they don't seem to
work. No errors are logged and the compile looks like everything is good,
but it hasn't copied the file. If I set the IT_PRODNAME to the product name
(which I pass into it from BA) and compile it in SB7, it copies the file.
I'm not exactly sure where the problem is and I'm not getting any errors
from SB. It's not a big deal, I just need to set this variable in the
script but I'd like to be able to figure out what is going wrong.
I.e. If the product I'm compiling is YYY:
If IT_PRODNAME contains XXX in the SB script (Compiler Variables section)
and I pass YYY to it via the command line #copy will not work. Using
#MsgBox shows that IT_PRODNAME does correctly contain YYY and everything
else using IT_PRODNAME produces the correct results. It is used in 26
places in this script and it would completely fall apart if it wasn't
right<g>
If IT_PRODNAME contains YYY in the SB script it will work.
#copy is set to execute at the end of the script.
Funny thing is that it does NOT copy the files to the (incorrect) XXX folder
either, I tried that.
Any ideas?
--
Arnór Baldvinsson - Icetips Alta LLC
Port Angeles, Washington
www.icetips.com - www.buildautomator.com - www.altawebworks.com
Icetips product subscriptions at http://www.icetips.com/subscribe.php
I just noticed something weird. I use a #copy file action in all my scripts
to copy my installs to a product folder on my server so I can have easy
access to them from anywhere on the LAN.
I've recently built a "template" to use with new products and instead of
hard coding the destination I used:
T:\Installs\_Icetips\[IT_PRODNAME]\[EXENAME]
Both IT_PRODNAME and EXENAME come from Build Automator and they work
perfectly anywhere else in the install as far as I can tell (I use the
IT_PRODNAME in several places)
But when I use the compiler variables in the #copy file they don't seem to
work. No errors are logged and the compile looks like everything is good,
but it hasn't copied the file. If I set the IT_PRODNAME to the product name
(which I pass into it from BA) and compile it in SB7, it copies the file.
I'm not exactly sure where the problem is and I'm not getting any errors
from SB. It's not a big deal, I just need to set this variable in the
script but I'd like to be able to figure out what is going wrong.
I.e. If the product I'm compiling is YYY:
If IT_PRODNAME contains XXX in the SB script (Compiler Variables section)
and I pass YYY to it via the command line #copy will not work. Using
#MsgBox shows that IT_PRODNAME does correctly contain YYY and everything
else using IT_PRODNAME produces the correct results. It is used in 26
places in this script and it would completely fall apart if it wasn't
right<g>
If IT_PRODNAME contains YYY in the SB script it will work.
#copy is set to execute at the end of the script.
Funny thing is that it does NOT copy the files to the (incorrect) XXX folder
either, I tried that.
Any ideas?
--
Arnór Baldvinsson - Icetips Alta LLC
Port Angeles, Washington
www.icetips.com - www.buildautomator.com - www.altawebworks.com
Icetips product subscriptions at http://www.icetips.com/subscribe.php