There are probably a LOT of people using Windows that, like I normally do,
make changes or corrections to local copies of Epics configurations . . . .
and then do it again and again and again on other systems when a fresh
deployment of everything is grabbed or someone uses a different version of a
Microsoft compiler.
Since Base is up on Github, would that be the preferred location to be
submit such changes? ('cause I would like expected and accepted warning
messages to go away as much as the next person.)
-----Original Message-----
From: Johnson, Andrew N. [mailto:[email protected]]
Sent: Thursday, April 20, 2017 11:50 AM
To: Engbretson, Mark S. <[email protected]>; [email protected]
Subject: Re: EPICS V4 Windows build warning messages.
Hi Mark,
On 04/19/2017 03:42 PM, Mark S. Engbretson wrote:
Although shouldn't this solution be merged into Epics base so that it
goes away for everyone in the future?
Done (committed to the 3.14 branch from where it will get merged into the
other branches). Thanks for pushing for that.
The linux builds of much of the Epics code compiles clean. The window
compilers . . . . not so much so.
None of the core developers have much love of working on Windows, so as an
EPICS platform it may be a somewhat neglected child. If someone with
suitable expertise wanted to help clean up the code-base I don't think we
would refuse any offers of help.
- Andrew
--
Arguing for surveillance because you have nothing to hide is no different
than making the claim, "I don't care about freedom of speech because I have
nothing to say." -- Edward Snowdon
