[tao-users] [ace-users] [installation] having problems building ACE/TAO for vxworks.

Johnny Willemsen jwillemsen at remedy.nl
Tue Jun 19 08:09:26 CDT 2007

Hi Jose,

We as Remedy IT do commercial support and port ACE/TAO to VxWorks, see
www.theaceorb.nl for our info. We do build and test daily and do get very
good results. Building and testing is sometimes hard, but we help our
customers in building things and running the regression tests. We do build
statically, that is used by the current sponsors, shared library is not
tested by us at this moment. Contact me directly to discuss VxWorks and how
we can assist with that.


Johnny Willemsen
Remedy IT
Postbus 101
2650 AC  Berkel en Rodenrijs
The Netherlands
www.theaceorb.nl / www.remedy.nl  

*** Integrated compile and test statistics see http://remedy.nl ***
*** Commercial service and support for ACE/TAO/CIAO             ***
*** See http://www.theaceorb.nl/en/support.html                 ***

> > Could somebody please help  me with some more detailed 
> > instructions on how to build ACE/TAO for VxWorks?
> You did not give any details on what exactly failed. If you 
> have further 
> questions please be sure to do so. But here are some suggestions:
> Do not bother with the autoconf-based build, since that does not work 
> for cross-compiling.
> You did a native build first to get gperf and tao_idl, right?
> I had decent luck building for VxWorks-6.3 and TAO-1.5.8 using the 
> classic from-source build technique. The results are not yet tested.
> In previous versions of TAO I was able to assign TAO_IDL and other 
> variables in my platform_macros.GNU to get the cross-compilation to 
> work, but for 1.5.8 I seemed to need to actually create the 
> soft links 
> in $ACE_ROOT/bin/ from the native build to the VxWorks directory.
> I sourced $WIND_BASE/windriver.bash before compiling. That got the 
> compilers in my path and defined a bunch of environment variables. In 
> previous versions of VxWorks I defined these variables for myself.
> I turned off RTP in platform_macros.GNU since that 
> configuration seemed 
> to want a few definitions that did not exist. I understand 
> that RTP is 
> the configuration that was used by Johnny Willemsen when 
> freshening the 
> VxWorks support recently.
> Much more of ACE and TAO build for VxWorks than did in the days of 
> TAO-1.2.1.
> I patch ACE and TAO to get singletons to work with multiple loadable 
> modules; the VxWorks loader does not respect weakly-defined 
> objects and 
> will create multiple instances of singletons if they are referenced 
> across modules. The patches involve using RTTI to register 
> singletons in 
> a non-templated manager object.
> I've enclosed my platform_macros.GNU and config.h files; be 
> sure to vet 
> them for your environment.
> hth
>                            - Tom
> -- 
> Thomas Lockhart
> Supervisor, Realtime Software Group
> Interferometry and Large Optical Systems
> Caltech/JPL

More information about the Ace-users mailing list