Page 1 of 1

Relative paths for source files ?

Posted: Sun Feb 10, 2008 7:24 pm
by dcreel
Hi,

We need to set up the paths within our Install Aware project so they are relative.

We are wanting to automate our setup with miabuild, and we have a different path structure on our build machine in comparison to our dev machines.

We've tried to change some of the paths over to relative paths, but the install aware compiler complains.

So, how would we use relative paths ?

...And if we can't how do we go about using compiler variables for these paths. Is there some simple explanation for how these work ? So far all we've been able to find, via googling, is a message on this forum where someone says it works for them. We need a bit more information.

Thanks & Regards
David

Posted: Tue Feb 12, 2008 6:11 pm
by Alex_Ronquillo
A compiler variable receives its value at build time and can be used as constant value. You can use compiler variables anywhere, including those places where it says variables not allowed. Compiler variables are dereferenced in the following way:

#COMPVAR#

Posted: Tue Feb 19, 2008 9:40 am
by rlaemmler
Alex_Ronquillo wrote:A compiler variable receives its value at build time and can be used as constant value. You can use compiler variables anywhere, including those places where it says variables not allowed. Compiler variables are dereferenced in the following way:

#COMPVAR#
I have the same problem but don't seem to get it work with compiler variables. Can you explain a little further please.

Also, why did you guys NOT include such a fundamental feature to allow relative paths? I would highly appreciate to see this in your next version of InstallAware.

Reto

Posted: Fri Feb 22, 2008 10:58 am
by Chris Miller
How are you specifying the relative paths? I have a project that I am working on now where the IA files are in a scripts folder and the installable bits are in a bin folder that is in the same folder as the scripts folder. I can specify the path to the installables like this:

..\\bin\\myfile.exe

It compiles without any complaints. This is with IA 7.5.

That makes it easy to version the script to a release version of the project. Plus I can test on my dev box and build the QA ready version from our build box.

Posted: Fri Feb 22, 2008 2:22 pm
by Chris Miller
I have to qualify my last post. The "Install files" command works just fine with relative paths, but the "Install Service" command doesn't.

If you use a relative path with "Install Service", it will compile with out any errors, but it fail when at install time with an error about a blank path.