Regarding Andrews point:
> It does if you realise that the binaries he is using were copied from APS's
> /usr/local/epics/extensions/bin/solaris directory, where they were compiled
> against X11R5 rather than openwin. I can't build BURT here because it won't
> compile using g++.
What is the official Epics policy on C++? Some of the bigger labs seem
to be getting heavily into C++ and talking to Jeff the other day the
new portable channel access server will not work without C++. However,
I get the feeling that there is also a lot of us out here who haven't
been able to use any of these new tools since we don't have the `right'
C++ compiler.
I understand the Epics policy with C is that we use the compiler
supplied by the OS vendor - but that is made much easier by there being
an ANSI standard. With C++ I get the feeling there is still a bit of
variation between compilers since the standard hasn't been cast in
stone yet. This variation may be an argument for g++, but I understand
that also doesn't work.
So, can someone in the know please:
1. Let me know whether I have to go and buy a SunSoft C++ compiler for
Solaris.
2. List all the Epics software that uses, or is dependent on, C++, and
what range of hardware, operating system and compiler it has been
tested on.
Thanks
Nick Rees
Joint Astronomy Centre Ph: +1 (808) 961-3756
660 N. Aohoku Place Fax: +1 (808) 961-6516
Hilo, HI. 96720 Internet: [email protected]
- Navigate by Date:
- Prev:
Re: Field type Jeff Hill
- Next:
Re: macro substitution William Lupton
- 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: Field type Jeff Hill
- Next:
Re: Policy on C++ compilers Jeff Hill
- 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
|