Related Google Groups threads:
1. Original complaint
2. Initial patch (untested, affects ISS scripts, not NSIS)
3. Specific thread for this issue
[1] https://groups.google.com/d/msg/hugin-ptx/E6EC4PCV2fE/ILHdbbFF5q0J
[2] https://groups.google.com/d/msg/hugin-ptx/E6EC4PCV2fE/7ymv4_kfaBgJ
[3] https
For convenience, I'm attaching the fix to this bug report as well.
--
Bart
** Patch added: "smartblend-fix.diff"
https://bugs.launchpad.net/hugin/+bug/787075/+attachment/2140776/+files/smartblend-fix.diff
--
You received this bug notification because you are a member of Hugin
Developers, wh
I also ran into this issue. Smartblend was mocking about a missing file
(this can be made visible by running 'make -f project.pto all' in a
console).
The fix was pretty easy: also chop off the '--' argument separator which
is apparently new in this version of Hugin.
Fix committed to hg. My first
> Just to add WHY the = sign is so problematic. When you say: make 'foo\=bar'
> make assigns the value "bar" to a variable named "foo\".
> See attached makefile, test with the above commandline.
That's what I figured, I was trying to find an escape character for the
'=' on the command line, but a
I've created a small test Makefile, to test various special chars for
filenames. Tested on Windows 7 x64 SP1.
>From the characters Bruno described as "impossible" due to the Makefile
format, I found only the '=' sign to pose a real problem if it should be
supported within a filename from the comma
5 matches
Mail list logo
