Experimental Physics and
Industrial Control System

Evgeniy Tikhomolov <[email protected]> · Wed, 27 Feb 2008 11:14:53 -0800

Thanks to all for clarification!
I could build 3.14.9 with free version of MS Visual Studio 2008 Express
Edition. However, it doesn't have MFC support, which I need.

MFC in MS Visual Studio 2008 Professional Edition uses some kernel32.dll
function which doesn't exist for Windows 2000, which my users have.
Finally, MS Visual Studio 2005 Professional Edition did the job both for
EPICS build and my MFC application. (with no forgetting about the
manifest files for deployment :)).

Evgeniy

Mark Rivers wrote:

Here's from the Wikipedia article on Visual C++
*****************************

Visual C++ 6.0, (commonly known as VC6) which included MFC 6.0, was

released in 1998. The release was somewhat controversial since it did

not include an expected update to MFC. Visual C++ 6.0 is still quite

popular and often used to maintain legacy projects. There are however

issues with this version under Windows XP, especially under the

debugging mode (ex: the values of static variables do not display). The

debugging issues can be solved with a patch called the "Visual C++ 6.0

Processor Pack" downloadable from

http://msdn2.microsoft.com/en-us/vstudio/aa718349.aspx; curiously, this

page stresses that Users must also be running Windows 98, Windows NT

4.0, or Windows 2000., though these requirements probably are the

minimum, which means that any computer with these version of Windows or

later will run the patch. 
Visual C++ .NET 2002 (known also as Visual C++ 7.0), which included MFC

7.0, was released in 2002 with support for link time code generation and

debugging runtime checks, .NET 1.0 and Visual C# and managed C++

extensions for .NET. The new user interface used many of the hot keys

and conventions of Visual Basic, which accounted from some of its

unpopularity among C++ developers. 
Visual C++ .NET 2003 (known also as Visual C++ 7.1), which included MFC

7.1, was released in 2003 along with .NET 1.1 and was a major upgrade to

Visual C++ .NET 2002. It was considered a patch to Visual C++ .NET 2002

and shipped for minimal cost to owners of that version. This is the last

version to support Windows 95 as a target.
eMbedded Visual C++ was used to develop for the Windows CE operating

system. eMbedded Visual C++ was replaced as a separate development

environment by Microsoft Visual Studio 2005. 
Visual C++ 2005 (known also as Visual C++ 8.0), which included MFC 8.0,

was released in November 2005. This version supports .NET 2.0 and

dropped managed C++ for C++/CLI. It also introduced OpenMP. With Visual

C++ 2005, Microsoft also introduced Team Foundation Server. Visual C++

8.0 has problems compiling MFC Appwizard projects that were created

using Visual Studio 6.0 so maintenance of legacy projects can be

continued with the original IDE if rewriting was not feasible. 
Visual C++ 2008 (known also as Visual C++ 9.0), was released in November

2007. This version supports .NET 3.5, and it is currently the latest

stable release.
******************************
I am compiling EPICS 3.14.8.2 on Visual C++ .NET 2003 (VC++ 7.1) with no
problems.
Mark

-----Original Message-----

From: [email protected]
[mailto:[email protected]] On Behalf Of Jeff Hill

Sent: Thursday, January 31, 2008 4:31 PM

To: 'Evgeniy Tikhomolov'; [email protected]

Subject: RE: Building EPICS base 3.14.9 on Windows

Initial indications are that this compiler behavior points to
a compiler

bug. I am not, for example, experiencing that problem with
Microsoft Visual

Studio 2005 Version 8.0.50727.867, nor with sun pro, and also
not with any

version of the GNU compiler that I have tried. Your 7.0
version originates

in 2002, is probably three major releases behind the current
version. If

possible please try a more recent release from Microsoft. I
have not yet

tried Microsoft Visual Studio 2008 BTW. 
If this behavior WRT MS Visual C++ 7.0 changed in a point
release that is

certainly an unfortunate result, but at this point in time it
is probably

preferable for you to move up to a more standards compliant
compiler rather

than risk introducing new code as a workaround into a mature release.
Jeff

-----Original Message-----

From: [email protected]

[mailto:[email protected]]

On Behalf Of Evgeniy Tikhomolov
Sent: Thursday, January 31, 2008 1:53 PM
To: [email protected]
Subject: Building EPICS base 3.14.9 on Windows
I can't build EPICS base 3.14.9 on Windows using MS Visual C++  .NET
compiler 7.0
HOST_ARCH=WIN32
Error message:
make[3]: Entering directory
`/cygdrive/w/Epics/base-3.14.9/src/ca/O.win32-x86'
cl /nologo /EHsc /GR -c             /D_CRT_SECURE_NO_DEPRECATE
/D_CRT_NONSTDC_NO_DEPRECATE /D__STDC__=0  /Ox /GL  /W3 /w44355
/MD    -I. -I.. -I..\\..\\..\\include\\os\\WIN32
-I..\\..\\..\\include        /Tp ..\\casw.cpp
casw.cpp
..\..\..\include\osiWireFormat.h(72) : error C2146: syntax error :
missing ',' before identifier 'T'
..\..\..\include\osiWireFormat.h(72) : error C2065: 'T' : undeclared
identifier
..\..\..\include\osiWireFormat.h(72) : error C2687: cannot define a
nested UDT of a template class out of line
..\..\..\include\osiWireFormat.h(72) : fatal error C1903: unable to
recover from previous error(s); stopping compilation
make[3]: Leaving directory
`/cygdrive/w/Epics/base-3.14.9/src/ca/O.win32-x86'
make[2]: Leaving directory `/cygdrive/w/Epics/base-3.14.9/src/ca'
make[1]: Leaving directory `/cygdrive/w/Epics/base-3.14.9/src'
make: Leaving directory `/cygdrive/w/Epics/base-3.14.9'
Evgeniy Tikhomolov

TRIUMF

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System