| legion_make FAQ
|
| 1. | | What does this command do? | [go] |
|
| 2. | | How can I get the compiled binaries back? | [go] |
|
| 3. | | Can I choose the remote host? | [go] |
|
| 4. | | Can I specify the remote host's architecture? | [go] |
|
| 5. | | Can I pass arguments to the remote make? | [go] |
|
| 6. | | I want to register the program with Legion, once it has compiled | [go] |
|
| 7. | | Some hints to make life easier | [go] |
What does this command do?
- This command compiles your program on a remote host. To be specific, it tars your current directory, copies it to a remote host, untars the copy, and executes a make command (if you don't want to run make, you can use the -e flag to specify a different executable command). The command is fully documented here.
How can I get the compiled binaries back?
- In the default setting, Legion will not copy anything out of the compiled directory. However, you can use one or more -OUT flags to tell Legion to copy files back to your local directory.
Can I choose the remote host?
- You can use the -h flag to specify which host should be used. If neither -h or -a are used, Legion will choose a random host.
Can I specify the remote host's architecture?
- You can use the -a flag to choose the architectur. If neither -h or -a are used, Legion will choose a random host.
Can I pass arguments to the remote make?
- Any arguments should be included in the [<arg1> <arg2> ... <argn>] parameter on the command line.
I want to register the program with Legion, once it has compiled
- You can do this by editing the directory's makefile.
Some hints to make life easier
- This command will tar everything in and below your current directory -- check that you are in the correct directory before you start.
- Be aware that if you do not specify an architecture or host, Legion will randomly choose a remote host.
|
