EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <2021>  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <2021>  2022  2023  2024 
<== Date ==> <== Thread ==>
Subject: RE: Epics-base together with a demo IOC and Phoebus as a Windows installation package
From: Freddie Akeroyd - STFC UKRI via Core-talk <core-talk at aps.anl.gov>
To: "EPICS core-talk (core-talk at aps.anl.gov)" <core-talk at aps.anl.gov>
Date: Wed, 11 Aug 2021 19:13:28 +0000

Hi,

 

I've used WiX https://wixtoolset.org/ to build MSI packages for our EPICS iocs distribution and clients, but we have only ever deployed the client MSIs as our whole EPICS iocs MSI was a bit big and I never got round to breaking it down into separate dependencies (we currently robocopy a release tree). You can't totally escape initially editing a bit of XML, but you can use the "heat" harvest tool to generate most of what you need from an existing directory tree. I believe if you create a package that is capable of per-user installation then it does not require Administrator rights to install, but it is not something I have done to date.

 

There is also the newer MSIX package format https://docs.microsoft.com/en-us/windows/msix/overview (requires windows 10) and Microsoft recently released a new package manager for Windows https://devblogs.microsoft.com/commandline/windows-package-manager-1-0/ but I haven’t looked at either in any detail

 

Regards,

 

Freddie

 

From: Core-talk <core-talk-bounces at aps.anl.gov> On Behalf Of Ralph Lange via Core-talk
Sent: 11 August 2021 14:12
To: EPICS Core Talk <core-talk at aps.anl.gov>
Subject: Re: Epics-base together with a demo IOC and Phoebus as a Windows installation package

 

Welcome to the dark side.

 

For an overview read, the How-To docs for Windows are pretty good and up-to-date, covering the choices of tool stacks, compilers, linkage options: https://docs.epics-controls.org/projects/how-tos/en/latest/getting-started/installation-windows.html

 

As for Windows package managers, I can fully support the statements of Michael and Andrew: MSI is the worst, and Chocolatey is so good that Microsoft picked it up.

(Both need administrator rights, so for myself: not applicable.)

Maybe talk to Carsten Winkler at HZB/BESSY (author of LabCA): he is knowledgeable with both technologies, as far as I know.

 

If you think about a broader approach for developing and deploying EPICS based systems within the Fairmat initiative, I would do a one size larger round by doing a proper design: collect requirements (with the choices in mind that the read-me points out), have partners sign-off on those, do a design and convince them with a prototype. If you want to establish a standard, you need to involve your clients early on.

 

For deployment of Windows IOCs in a larger facility, Mark Rivers and Freddie Akeroyd would definitely be people to talk to. Beamlines are prototypes for platform diversity (isolation and robustness); ISIS migrated their Instrument controls to EPICS@Windows (scalability and consistency).

 

Cheers,

~Ralph

 

This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. 

References:
Epics-base together with a demo IOC and Phoebus as a Windows installation package Heinz Junkes via Core-talk
Re: Epics-base together with a demo IOC and Phoebus as a Windows installation package Johnson, Andrew N. via Core-talk
Re: Epics-base together with a demo IOC and Phoebus as a Windows installation package Ralph Lange via Core-talk
Navigate by Date:
Prev: Build failed in Jenkins: EPICS-7 #374 Jenkins EPICS PSI via Core-talk
Next: [Bug 1939568] Re: Writing to mbboDirect.VAL does not work any more in EPICS 7 Dirk Zimoch via Core-talk
Index: 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: Epics-base together with a demo IOC and Phoebus as a Windows installation package Ralph Lange via Core-talk
Next: Great Career Opportunity for Particle Accelerator Instrumentation Physicist/Engineer nickm--- via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <2021>  2022  2023  2024 
ANJ, 12 Aug 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·