EPICS Home

Experimental Physics and Industrial Control System


 
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: libraries required by CA client application
From: "Russ Berg" <[email protected]>
To: "Jeff Hill" <[email protected]>, "sunxy" <[email protected]>, <[email protected]>
Date: Tue, 8 Jun 2004 10:33:29 -0600
Hi all, I use cppBuilder (win2k) a fair bit for operator screens, to
link in the ca stuff all I did was compile the win32-x86 EPICS base
using MSV6, then create borland compatible 'lib' files of com.dll and
ca.dll by using 'impdef' and 'implib' (both come with builder). Add the
resulting ca.lib and com.lib to your project and include 'cadef.h' in
your source and you are ready to make ca calls. I have tested a little
with Kylix and was able to make it work with the gnu compiled libraries.

-Russ

-----Original Message-----
From: Jeff Hill [mailto:[email protected]] 
Sent: Tuesday, June 08, 2004 9:39 AM
To: 'sunxy'; [email protected]
Subject: RE: libraries required by CA client application



Hello Sun Xiaoying,

Your Linux application that uses the CA client library to
put/get/monitor will need to link with libca and libCom. These libraries
are located in <EPICS base>/lib/linux-x86. The Borland specific options
that will be required by kylix (C++ builder) will be different than the
options used by the EPICS make files which are GNU based by default on
Linux. If you run a Borland based EPICS build on windows and watch the
compile/link lines this may be helpful when choosing the build options
for your kylix C++ Builder environment on Linux (I don't know that this
will help, but it might be a place to start).

PS: You have identified an omission (a vast gaping hole perhaps) in the
channel access documentation. I have attached an updated CA reference
manual which has a small addition which starts to address the problem.

PPS: Note that there are some significant bugs in the EPICS R3.14.5 CA
client library which have been fixed in R3.14.6.

Jeff

> -----Original Message-----
> From: sunxy [mailto:[email protected]]
> Sent: Tuesday, June 08, 2004 12:43 AM
> To: [email protected]
> Subject:
> 
> Dear everybody:
> 
>    I am a graduate student from SSRF. I want to develop a simple 
> application which will have functions of put,get and monitor channels 
> in IOC, and store the data to SQL Server7.0 database. I have installed

> EPICS Base R3.14.5 in a PC/Linux and my developing environment is C++ 
> Builder in another PC/WIN2000 server.
>    Because I am a novice to EPICS, may I ask which libraries should be

> integrated to C++ Builder environment? If somebody have the 
> experience, I would appreciate if I could share it and codes for 
> reference.
> 
>  Thanks
> 
>  Sun Xiaoying
> 
> > Shanghai Institute of Applied Physics
> > Chinese Academy of Sciences
> > P. O. Box 800-204, Shanghai 201800, P. R. China
> > Tel: +86-21-59554887


Navigate by Date:
Prev: Re: Modbus/ASCII or Modbus/RTU (serial) Paul Sichta
Next: Oracle Slow Archiver Vladimir Sirotenko
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Modbus/ASCII or Modbus/RTU (serial) Heron, M (Mark)
Next: Oracle Slow Archiver Vladimir Sirotenko
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024