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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: Building 3.14.7 on win32-x86 with Visual C++ 6.0 |
From: | "Jeff Hill" <[email protected]> |
To: | <[email protected]>, <[email protected]> |
Date: | Mon, 14 Nov 2005 09:32:39 -0700 |
Hello Jinhyuk Choi ,
Of course the root cause of inconvience is that we are
using different versions
of visual visual C++. For example, I am using visual
studio.NET 2003 which has
better compliance with ANSI C++ standards compared to
visual C++ 6.0.
One of the changes proposed would actually prevent the
code from compiling with a
standards compliant compiler. For example with recent
versions of GNU g++ the
following result
occurs.
for (unsigned i=0; i<10;
i++);
for (i=0; i<10; i++);
/cygdrive/d/users/hill/epicsDvl/epics/base$
g++ tmp.cpp
Nevertheless, I have committed changes to CVS for R3.14.8 (availalable soon for testing via a nightly snbapshot) that should hopefully allow visual studio 6.0 to be used also.
> 1. No /GL, /w44355 options for cl
These command line switches, available only with the more recent compiler, do generate warnings if used with the older compiler.
One possible way to avoid the warnings would be to create a set of config files for host architecture win32-x86-MSVS6.0
> I wish this list can help to someone.
No doubt that they will.
Thanks very much for your assistance.
Jeff
-----Original
Message-----
From: ÃÖÁøÇõ [mailto:[email protected]] Sent: Friday, November 11, 2005 2:15 AM To: [email protected] Subject: Building 3.14.7 on win32-x86 with Visual C++ 6.0 Hi all, |