On Mon, Oct 13, 2008 at 10:49 PM, Bruno Postle <[EMAIL PROTECTED]> wrote:
> 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? In case of distmake then this is most probably the case (I haven't tried distmake). In case of my project, I basically have to manage to run the remote copy of nona. The main constraint being here is the least possible modification to makefile (or existing source code, like hugin's). The project is my diploma thesis. The basic idea is that when a component (invocation of nona for example) needs to be instantiated, it is done so on a machine that satisfies certain conditions (for example sufficient and available CPU power). > Though surely you would be using a network filesystem? In which > case all files will be available. This is one scenario, which does not cover all possibilities. Example: Let there be network-reachable machines that donate their CPU to (not necessarily) anybody, and permit only certain set of programs to be executed (hugin being the one allowed). When a user with a less-powerfull machine wishes to compute his/her panorama he/she simply types 'make', and then, depending on the configuration, it takes places either on the localhost or on the available remote machines (preferrably). Tomas Klacko --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
