I've solved my problem, as you say the solution is not hard. But felt I should report the bug anyway as, I for one, found it surprising that a symlink is treated differently to a file. most other building systems don't do this.
$ mkdir -p tmp/folder $ cd tmp/ $ echo "all:" > folder/Makefile $ echo " pwd" >> folder/Makefile $ ln -s folder/Makefile $ make pwd /home/user/Desktop/tmp If you want to close the bug as invalid, thats fine, as long as I'm clear that its a "would be nice" type scenario > ----- Original Message ----- > From: Thomas Gaugler > Sent: 04/07/13 07:19 PM > To: D Haley, 704...@bugs.debian.org > Subject: Re: Bug#704828: nsis: CWD taken from symlink target, not symlink > itself > > If you build your .nsi script in the /home/user/project folder then it > is going to fail as well. > > makensis follows symbolic links. So if you put your .nsi file in the > parent folder then you would need to adapt the file references to this > new base (/home/user/project). > > In your example this means the following adaption: > --- > !insertmacro MUI_PAGE_LICENSE "folder/COPYING" > ---- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
