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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: procServ softIOC server - V2.5.0 released |
From: | Ralph Lange <[email protected]> |
To: | "J. Lewis Muir" <[email protected]>, Benjamin Franksen <[email protected]> |
Cc: | [email protected] |
Date: | Fri, 04 Dec 2009 09:15:37 -0500 |
So the idea was to build procServ on a cygwin system, distribute the EXE, and run it on any system that has the cygwin DLL.
As far as I understand, CMake would not solve the fork() et al. issue and require CMake to be installed for the build instead of cygwin. As I assume cygwin to be more common on Windows systems than CMake, I don't see the immediate advantage of a build system switch.
Ralph On Thu 03 Dec 2009 18:44:07 J. Lewis Muir wrote:
On 12/3/09 4:51 PM, Benjamin Franksen wrote:On Donnerstag, 3. Dezember 2009, Ralph Lange wrote:Hmmm. Autotools need a unix-like (bourne-) shell. On windows this means you'll have to have some unix emulation installed (cygwin, whatever).The major milestone at the horizon is getting it to run on Windows machines, to finally get reasonable remote access and logging for all these embedded Windows soft IOCs running in Scopes, LabViews systems and such. So switching to the autotools framework was really just a firststep ...Cheers BenOr maybe the procServ build system could be switched to CMake: http://www.cmake.org/ Lewis