EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: Re: CSS - how to prepare site specific version
From: "Kasemir, Kay" <[email protected]>
To: Vítek Michal <[email protected]>, "[email protected]" <[email protected]>
Date: Wed, 3 Apr 2013 11:36:26 -0400
Hello Mike:

On 4/3/13 11:06 , "Vítek Michal" <[email protected]> wrote:
>What I still do not understand is where I can get the plugins. The
>css_book suggest to use CSS source codes of side specific build and to
>use "user selection" of plugins included in this build. The thing is that
>I would like to use a combination of plugins for which I would need to
>combine source codes of all three main bulits available and combine them
>somehow. Thus I am wondering if there is some way how to get source code
>with all available plugins to reduce time spend on the building process
>and to minimize risk of problems during compilation... Any suggestion?
If you want to get the source for everything, you simply get a copy of the
source repository:

git clone https://github.com/ControlSystemStudio/cs-studio.git

Takes about 3 minutes, and you have everything including the history.
Then you look at one of the products/<site name>/* products for one that
might be close to what you want, and go from there.
What's confusing in that approach: You get a ton of plugins, some very
site specific, some with compiler errors because nobody uses them any
more. Maybe even plugins with the same name in the 'main' section of the
repository and under products/<site name> because a site needed certain
changes in there. So if you simply 'import' everything into Eclipse to
look at it, you'd be overwhelmed (or at least I am).
What I do: Import the products that I want into my Eclipse workspace, then
import the features and plugins needed by those products. This step is
tedious.

-Kay





References:
RE: CSS - how to prepare site specific version Vítek Michal

Navigate by Date:
Prev: RE: CSS - how to prepare site specific version Vítek Michal
Next: Error building EPICSQt Lucas Jose Monteiro Carvalho
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: CSS - how to prepare site specific version Vítek Michal
Next: Error building EPICSQt Lucas Jose Monteiro Carvalho
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·