Cross-development with network filesystem

If you're using a network filesystem, let's assume you've already set up the filesystem on both ends.

For information on setting this up, see “TCP/IP with network filesystem” in the Sample Buildfiles appendix in Building Embedded Systems.

Using a network filesystem is a rich cross-development method, because you have access to remotely mounted filesystems. This is useful for a number of reasons:

• Your embedded system requires only a network connection; no disks (and disk controllers) are required.
• You can access all the shipped and custom-developed QNX Neutrino utilities—they don't need to be present on your (limited) embedded system.
• Multiple developers can share the same filesystem server.

For a network filesystem, you'll need to ensure that the shell's PATH environment variable includes the path to your executable via the network-mounted filesystem, or that you specify the full path to the executable. At this point, you can just type the name of the executable at the target's command-line prompt (if you're running a shell on the target):

hello