[NSIS-Bugs] [ nsis-Bugs-1065273 ] Relative OutFile path bug/confusion

[SourceForge.net <no...@so...>]

Bugs item #1065273, was opened at 2004-11-12 16:13
Message generated for change (Comment added) made by csexton
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373085&aid=1065273&group_id=22049

Category: General
Group: 2.0 Series
Status: Open
Resolution: None
Priority: 5
Submitted By: Chris Sexton (csexton)
Assigned to: Nobody/Anonymous (nobody)
Summary: Relative OutFile path bug/confusion

Initial Comment:
When I call NSIS executable and give it a path to a .nsi 
file, any relative path I put in the script for the OutFile 
is taken as relative to the location of the .nsi file and 
not relative to the working directory I am executing the 
NSIS from.

Example:

- take a script called test.nsi
- and the following directory structure (dirs shown in 
brackets [])

    [build]
       |_ [installer]
       |_ [script]
              |_ test.nsi 

- what I want is to run makeNSIS from the [build] 
directory, instructing it to compile [script]\test.nsi and 
make the output go to [installer]\install.exe
- so, into test.nsi I add the line (note a relative path)
    OutFile "installer\install.exe"
- and I compile:

cd build
makensis.exe script\test.nsi

- I was expecting this to work as I intended, but what I 
got was:

Output: "D:\build\script\installer\install.exe"
Can't open output file
Error - aborting creation process

As you can see it assumed the relative 
path "installer\install.exe" was relative to the location of 
the script "script\test.nsi" rather than the parent 
dir "build" which was the working directory where I 
executed makensis.exe

So, as I see it, either:

1) There is a bug and when the value for outfile is 
relative it should be made to work relative to the 
working directory of the compiler, or
2) The documentation of OutFile needs to be extended 
to point out that when OutFile is set to a relative path 
this is relative to the script regardless of where the 
compiler is executed from. 

Personally, (1) sounds much more intuitive and more 
consistent with other command line programs. 

If not (1) then can you explain what the reason is 
please?

Thanks

P.S. NSIS truly is an excellent project - many thanks for 
everything you do - keep up the good work!

----------------------------------------------------------------------

>Comment By: Chris Sexton (csexton)
Date: 2004-11-12 17:11

Message:
Logged In: YES 
user_id=362942

Apologies, just found the /nocd command line flag

I would still recommend that the documentation for OutFile 
should be made more explicit about relative and absolute 
values for OutFile, and also that relative is relative to either 
the working directory or the .nsi script depending on whether 
the /nocd flag is specified

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373085&aid=1065273&group_id=22049