Re: Build EPICS for vxWorks 6.9 on windows-XP SP3

[Andrew Johnson <anj@aps.anl.gov>]

Hi,

On 07/01/2014 11:01 PM, "भावना नितिन मेढ़" wrote:
>  We are trying to port EPICS on VxWorks.
> 
>  Various information related to our setup are:
> 
>          EPICS base version : 3.14.12.4
>          VxWorks Version : 6.9
>          Workbench version : 3.3
>          Host Architecture : win32 on x86
>          Target Architecture: ppc-32
>          Target Board :  MVME-5500 with PowerPC 7447 processor
> 
> I would like to know what information goes in the file
> CONFIG_SITE.<host>.<target> i.e. in our case
> CONFIG_SITE.win32-x86.vxWorks-ppc32 and where do we specify GNU directory
> path? Also is MS Visual Studio 2010 needed when cross compiling for
> vxWorks?If somebody has already documented the various steps needed for
> the build, it will be of great help.

Look first at the CONFIG_SITE.Common.vxWorksCommon file because that may
be the only file you need to modify, and it has comments explaining what
the settings are. That is where you normally tell Base which versions of
the Wind River software you have and the location where you installed
that software. In your case the settings will probably be
    VXWORKS_VERSION = 6.9
    WORKBENCH_VERSION = 3.3
    UTILITIES_VERSION = 1.0
    WIND_BASE = C:\path\to\wind\river\installation

You would normally only need to put settings in a new
CONFIG_SITE.win32-x86.vxWorks-ppc32 file if you are sharing this
installation of Base between different architectures which must see
different values for the settings in the Common.vxWorksCommon file than
other hosts. Similarly you should set
    CROSS_COMPILER_TARGET_ARCHS = vxWorks-ppc32
in the <top>/configure/CONFIG_SITE if possible, but you can put that
setting in the CONFIG_SITE.win32-x86.Common file if this installation of
Base is also used on other host architectures which cannot build VxWorks
code.

Base builds have to compile software to runs on the build host at
build-time, which is why you *will* need one of the supported host
compilers; it doesn't have to be MS Visual Studio, MinGW should work
just as well but your EPICS_HOST_ARCH would need to be adjusted to match
if you use that instead. I would avoid Cygwin as it does tend to be
slower than the native tools, although it too ought to work.

I hope this gives you enough information to get started with. Please
keep any follow-up emails on the tech-talk list for others to reference
in the future.

- Andrew
-- 
Advertising may be described as the science of arresting the human
intelligence long enough to get money from it. -- Stephen Leacock