hugin-devs team mailing list archive

[Yuv <696646@xxxxxxxxxxxxxxxxxx>]

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 environment variable is not set?  if yes, then that BAT
script should set a variable environment such as 'set hugin_env=true'
and the Hugin binary should start only if hugin_env is set.

This would prevent much of the confusion from conflicting paths.

-- 
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: incorrect quoting in Makefile generation

Status in Hugin - Panorama Tools GUI:
  Incomplete

Bug description:
  Reported on Hugin-PTX http://groups.google.com/group/hugin-
  ptx/t/d33b5bc24aada66b

  HuginSetup_2010.4.0-64bit_Windows.exe on my Windows 7 x64. Everything work fine, until i try to
  create the pano. Then i got the following message:

  [...]

  ===========================================================================
  System information
  ===========================================================================
  /usr/bin/sh: -c: line 1: syntax error near unexpected token `(6'
  /usr/bin/sh: -c: line 1: `echo Operating System: Windows 7 (6.1 )'
  make: *** [info] Error 258 

  Makefile attached.  Obviously lacking quotes in the info target around
  line 211.