Sb_project_script

[NewsArchive]

Friedrich - thanks for the new compiler variable.

However, I am using it in a copy command. As this contains the full pathname
it is failing as the script generates something like:

Copy .... to C:\Test\Development\Release\v1.1\c:\text\keep\v1.1 \whatever.sb6

It does not like the c:\.. part I am assuming. What I have NOT checked is
that the fact that the file is still open could cause an issue.

What I would ideally like is the compiler variable to just contain the
script name and not the full pathname.

Many thanks

John Fligg

[NewsArchive]

Hi John,

> Friedrich - thanks for the new compiler variable.
>
> However, I am using it in a copy command. As this contains the full
> pathname
> it is failing as the script generates something like:
>
> Copy .... to
> C:\Test\Development\Release\v1.1\c:\text\keep\v1.1 \whatever.sb6
>
> It does not like the c:\.. part I am assuming. What I have NOT checked is
> that the fact that the file is still open could cause an issue.
>
> What I would ideally like is the compiler variable to just contain the
> script name and not the full pathname.

Hmm, works fine here.

Compiler reports this:

Compilation Time: 1.13 sec.
Date/Time: 10/13/2007 -- 5:28:59PM

------------------------------- Compilation
finished -------------------------------

Process post compilation tasks...
Copying... C:\Documents and Settings\Friedrich Linder\My
Documents\SetupBuilder 6 Projects\Your Project Name-48.sb6 to
c:\test\testme.sb6
OK

I am using this (see attached screenshot).

Friedrich

[NewsArchive]

But you are not using the new compiler variable.

My destination is:

c:\Ambrit\Development\Farrier\Releases\v[PRODUCTVER]\[SB_PROJECT_SCRIPT]

John

[NewsArchive]

BTW Just in case you wonder what I am doing - it is that I copy my installer
executable to a version folder. I also want to copy my setup project to the
same version folder.

John

[NewsArchive]

Hi John,

Yes, I am using [SB_PROJECT_SCRIPT] as Source. So you need a compiler
variable with just the project file (e.g. whatever.sb6), right?

Friedrich

[NewsArchive]

I think so Friedrich.

I too am using the variable as the source. It seems it is the use of it in
the destination that may be causing the problem, so a shortened version
would be good.

Thanks

John

[NewsArchive]

Just to confirm - if I use

......[PRODUCTVER]\whatever.sb6

instead of

.....[PRODUCTVER]\[SB_PROJECT_SCRIPT]

then it works fine and the fact that the file is already open is not a
factor. So clearly the full pathname for the project name in the DESTINATION
is the cause of the problem.

Many thanks Friedrich

John

[NewsArchive]

Hi John,

Okay, no problem. I'll add it.

Yes, the [SB_PROJECT_SCRIPT] compiler variable holds a fully qualified path
name value. It can only be used as Source, not as Target.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.6
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Thank you Friedrich. Much appreciated.

It just one more thing to help in the quest to build a generic installer
script for multiple projects.

John

[NewsArchive]

Hi John,

> Thank you Friedrich. Much appreciated.
>
> It just one more thing to help in the quest to build a generic installer
> script for multiple projects.

Yes, absolutely!

Friedrich