On Mon 13-Oct-2008 at 21:41 +0200, Tomas Klacko wrote: > >>>- take the ~/.hugin configuration file and set NonaExe to myRemoteNona >> >> This won't work, the ~/.hugin file is only accessed by the GUI (it >> is a wxwidgets thing). > >~/.hugin stores the configuration for the wxwidgets? >(with some values being editable (like actualPath) >and some values being constants (like NonaExe))
Hugin shouldn't reset any changes you make manually to ~/.hugin, but this file is ignored by the command-line tools, it is only used by the GUI. pto2mk reads these lines in the .pto file when it creates the .pto.mk Makefile: #hugin_remapper nona So you could edit them rather than setting $NONA in the environment. Though I'm not sure why you need to execute nona remotely, surely you only need to run 'make' and this will run the remote copy of nona? >Example, makefile rule: >974-1-975-10001.tif: 975-1.jpg $(PROJECT_FILE) > $(NONA) $(NONA_LDR_REMAPPED_COMP) -r ldr -m TIFF_m -o >$(LDR_REMAPPED_PREFIX_SHELL) -i 1 $(PROJECT_FILE_SHELL) > But it will fail if 974-1.jpg is not present (nona will complain) This sounds like a bug in nona, there is no need to check for the existence of a file that isn't going to used. Though surely you would be using a network filesystem? In which case all files will be available. -- Bruno --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
