Hi Ben,
Everything in asyn is currently programmed in C except asynPortDriver, which is programmed in C++. It is asynPortDriver that will not build on vxWorks 5.4.2. You could probably just comment out asynPortDriver in the Makefile for what you need asyn for on vxWorks. It is crashing the compiler on the new version of asynPortDriver on this statement:
#include <stdexcept>
That is used many places in base, which builds OK on vxWorks, so I am not sure why it is crashing in asynPortDriver.
The asyn device support for arrays, (devAsynInt8Array, devAsynInt16Array, devAsynIn32Array, devAsynFloat32Array, devAsynFloat64Array) are currently written in C with a giant 4-page macro because they only differ in data types, etc. It is not pretty. That is a natural thing to rewrite using C++ template functions. But in trying to that it also crashed on vxWorks 5.4.2.
Mark
________________________________________
From: [email protected] [[email protected]] on behalf of Benjamin Franksen [[email protected]]
Sent: Monday, February 13, 2012 7:47 AM
To: [email protected]
Subject: Re: asyn and vxWorks 5.4.2 and earlier
On Friday, February 10, 2012, Mark Rivers wrote:
> John Hammonds and I have been doing some improvements to asyn that
> involve using C++ template functions and C++ exceptions.
I thought asyn was programmed in C, not C++?
> We have found
> a serious problem with the vxWorks cross-compilers running under Linux
> with vxWorks 5.4.2 (and presumably earlier versions as well). The
> cross-compilers crash on valid C++ code. This problem does not occur on
> vxWorks 5.5.2, nor on Linux, Windows, etc.
>
> My question to the community: will it be a serious problem if the next
> release of asyn cannot be built on vxWorks 5.4.2 and earlier? Are there
> sites that would plan to upgrade asyn but continue to use vxWorks 5.4.2
> or earlier?
Yes, we are still using 5.4.2 and we have not yet decided whether to upgrade
VxWorks or rather switch to RTEMS. We may decide this year, but it is not
clear how long it will take use to complete the upgrade/switch, once the
decision is made. I would not be happy if it turns out we can no longer
compile new versions of asyn, especially since many modules depend on it
(e.g. most of the stuff in synApps).
Cheers
Ben
________________________________
Helmholtz-Zentrum Berlin für Materialien und Energie GmbH
Mitglied der Hermann von Helmholtz-Gemeinschaft Deutscher Forschungszentren e.V.
Aufsichtsrat: Vorsitzender Prof. Dr. Dr. h.c. mult. Joachim Treusch, stv. Vorsitzende Dr. Beatrix Vierkorn-Rudolph
Geschäftsführerin: Prof. Dr. Anke Rita Kaysser-Pyzalla
Sitz Berlin, AG Charlottenburg, 89 HRB 5583
Postadresse:
Hahn-Meitner-Platz 1
D-14109 Berlin
http://www.helmholtz-berlin.de
- References:
- asyn and vxWorks 5.4.2 and earlier Mark Rivers
- Re: asyn and vxWorks 5.4.2 and earlier Benjamin Franksen
- Navigate by Date:
- Prev:
Re: asyn and vxWorks 5.4.2 and earlier Benjamin Franksen
- Next:
Re: cothread time stamp problem Shen, Guobao
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: asyn and vxWorks 5.4.2 and earlier Benjamin Franksen
- Next:
How to set the parameters of the mrmEvrSetupVME or mrmEvgSetupVME Zhu, Lixin
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|