Experimental Physics and
Industrial Control System

"Ernest L. Williams Jr." <[email protected]> · Tue, 10 Apr 2007 09:54:54 -0400

Hi Andrew,

Sorry to bring up the following issue again:

I suppose there will be some sites that move into vxWorks 6.x but still
have vxWorks 5.5 targets as well.  What recommendation do you have to
handle this?  We could have to separate versions of EPICS BASE.
Does no good to change the VXWORKS version number in the config files as
it will simply overwrite libraries for vxWorks 6 or 5 depending on which
one you built first.

Of course, on my teststand I am only doing vxWorks 6.  When we migrate
to production we will have both vxWorks 5 and 6.

Problems with vxWorks build with new config file structure:
> (1) Can't build for vxWorks 5.5.X and vxWorks 6.X
> This is not good. Since our production environment includes both.
> So, vxWorks-ppc604 gets overwritten by second build of EPICS BASE
> against a different version of vxWorks.  I am sure that other sites
that
> move to vxWorks 6 will experience this.
> 
> I think we should have the config files contain vxWorks major version
> and BSP name like before.  Looks like you allow RTEMS to do this?
> For example, we are starting to use the altivec support on the
MVME5110
> but the MVME5100 does not have altivec support. 
> We could have vxWorks-ppc604_altivec, I guess.  Another example is
using
> the BSP/target name to discover whether we have a UNIVERSE or Tsi148
> interface for a DMA driver that we may write.  Having, the scheme that
> we used last time just turns into a bit more compile time and disk
> space, right?

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System