Experimental Physics and
| |||||||||||||||
|
Rod, Dirk, I would implement 1 and 2. 1 is easier for development. Once you have implemented 1 then 2 is easy because you can copy locally on your arm system from nfs to local disk. I would use a symbolic link for iocBoot to switch between nfs and local disk. If you use automount for nfs, you don't even need to worry what happens to your nfs mounts when you run standalone and the server is not available. As long as you don't use the drive it will not be mounted. If your system supports the /net automount facility, it becomes very easy: just set the link to /net/servername/remotedir to boot from nfs. If 2 makes sense depends on the size of the local disk. With tiny flash drives it becomes difficult. With modern solid state drives or even real hard disks, it is not a problem. Normally I don't build on the local machine. But it depends. If it is large enough to have the compiler installed and you build locally, then your EPICS_HOST_ARCH is linux-arm* and it is not treated as a cross build. And you will automatically have caget etc. In src/catools/Makefile you find: LIBRARY_HOST += catools PROD_HOST += caget camonitor cainfo caput This builds caget etc only for the host, not for the cross targets. To build the tools for all cross Linux IOCs, you may try to add: LIBRARY_IOC_Linux += catools PROD_IOC_Linux += caget camonitor cainfo caput I don't know if that works. And I don't know if it is possible to enable this in one of the configure files instead of hacking in src. I guess that is is possible with some advanced Makefile programming. Dirk
| ||||||||||||||
ANJ, 27 Oct 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |