** Changed in: hugin
Status: Incomplete = Fix Committed
** Changed in: hugin
Milestone: None = 2011.0beta3
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/696646
Title:
Windows:
Our assumption is that 'make' is using the wrong shell for some reason,
i.e. it is told to use cmd.exe but uses the cygwin sh.exe instead.
I tested with different makefile:
First the current implementation used by hugin (SHELL variable quoted for
shell):
SHELL=c:/windows/system32/cmd.exe
would it make sense to use a BAT file to start Hugin instead of starting
the actual binary?
that BAT file would do what Jean-Jacques just mentions, i.e. set the
path clean and then start the actual Hugin binary.
moreover: can the Hugin binary be prevented from starting if a
particular
There are lots of good reasons why a user would want to keep their
environment, resetting it shouldn't be necessary.
Our assumption is that 'make' is using the wrong shell for some reason,
i.e. it is told to use cmd.exe but uses the cygwin sh.exe instead.
Alternatively it could be that Hugin is
my understanding is that such a script would only change the environment
for Hugin, not the global environment.
I recall from the time I was using Windows that I had two different
icons to access the console. one was the standard one, in windows. The
other one was installed by MSVC express
Same for me:
===
System information
===
/usr/bin/sh: -c: line 1: syntax error near unexpected token `(6'
/usr/bin/sh: -c: line 1: `echo Operating System:
Have you tried the proposed solution?
Remove the directory which contains a sh.exe (or maybe bash.exe) from your PATH
variable.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/696646
Title:
7 matches
Mail list logo
