Relative path for File Bag?

[AndrewC]

I had a project that was built for InstallAware 9 R3 that used a relative path for a File Bag: ..\ABC\*.*

When I tried running that project under InstallAware X3, I got "Error! No files matching wildcard pattern ..\ABC\*.*"

If I substitute an absolute path the project compiles, but due to the way we structure our installs I'd prefer it if I could use a relative path there. Is this no longer supported? Do I have to use a different base for the path? In the past it seemed like the base for the path was the location of the project file.

[FrancescoT]

Dear Andrew,

as reported by the File Bag documentation, the command wants "The full path, including wildcards, to the files to include with the setup".
You may use a custom compiler variable, but in any case, this must point to the full path.

Hope this helps you.

Regards

[AndrewC]

Thanks for the reply. The issue is that I was previously able to use a relative path (back in InstallAware 9R2) -- is that no longer supported?

[FrancescoT]

Unfortunately, as I said, only "full paths" are allowed.

Regards