Migration from vsvc 6

  • Thread starter Thread starter RG
  • Start date Start date
R

RG

I am looking to migrate a makefile/vsvc6/RTC sdk project to vs .net 2003.
Can someone tell me how I could accomplish this?

Thanks in advance
 
RG said:
I am looking to migrate a makefile/vsvc6/RTC sdk project to vs .net
2003. Can someone tell me how I could accomplish this?
Click to expand...

Just do it. A makefile based project should be nearly 100% compatible at
the project level. I'm assuming by your wording that you don't have a VC6
project file (.dsp), but are using nmake directly.

If you do have a .dsp file (VC6 project), just open it in VC7.1 and it will
be converted.

If you're using libraries like ATL or MFC, you may need to make changes to
your code to accomodate changes in the libraries.

If you're using 3rd party libraries, you'll likely need to get VC7.1
versions of those libraries, unless they expose only pure C-based APIs.

If your code did anything with C++ templates in VC6, you'll probably have to
make changes to bring your code up to (a higher level of ) standard
conformance. The most common issue is the use of the typename keyword when
referencing dependent types within the definition of a template - a usage
which VC6 didn't support at all and which VC7.1 (correctly) insists on.

If you have more specific questions, please post back!

-cd
 
Thanks a lot for your help and interest. Your assumption is correct. It
is not a dsp project. It is a straight makefile project with manifest and
rc files. The problem is, having all the program, header, and whatever
other files, how I do I create a project or do I bring the files into the
environment.

By the way, this is a sample microsoft platform sdk code.

I tried to use nmake. Received the following error,

Microsoft (R) Program Maintenance Utility Version 7.00.8882
Copyright (C) Microsoft Corp 1988-2000. All rights reserved.

cl -Zi -Od -DDEBUG -c -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -GS
-D_X
86_=1 -DWIN32 -D_WIN32 -W3 -D_WINNT -D_WIN32_WINNT=0x0500 -D_WIN32_IE=0x0500
-D
WINVER=0x0500 -DUNICODE -D_UNICODE /EHsc /GX /MT /Fo"WIN2000_DEBUG\\"
/Fd"WIN20
00_DEBUG\\" rtcav.cpp
'cl' is not recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: 'cl' : return code '0x1'
Stop.

I suppose cl is the compiler program?
 
RG said:
Thanks a lot for your help and interest. Your assumption is correct.
It is not a dsp project. It is a straight makefile project with
manifest and rc files. The problem is, having all the program,
header, and whatever other files, how I do I create a project or do
I bring the files into the environment.
Click to expand...

By hand. There's no tool or function to import a makefile (just like there
wasn't in VC6). You'll have to dissect the makefile, learn how everything's
configured and built, and configure an IDE project file to match. Usually
it take little more than dumping all the .cpp files into a project, setting
the INCLUDE directories for the project, and possibly adding a predefined
macro or two.
By the way, this is a sample microsoft platform sdk code.

I tried to use nmake. Received the following error,

Microsoft (R) Program Maintenance Utility Version 7.00.8882
Copyright (C) Microsoft Corp 1988-2000. All rights reserved.

cl -Zi -Od -DDEBUG -c -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl
-nologo -GS -D_X
86_=1 -DWIN32 -D_WIN32 -W3 -D_WINNT -D_WIN32_WINNT=0x0500
-D_WIN32_IE=0x0500 -D
WINVER=0x0500 -DUNICODE -D_UNICODE /EHsc /GX /MT /Fo"WIN2000_DEBUG\\"
/Fd"WIN20
00_DEBUG\\" rtcav.cpp
'cl' is not recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: 'cl' : return code '0x1'
Stop.

I suppose cl is the compiler program?
Click to expand...

Yes. This error means that the VC7.1 tools were not on the PATH. Make sure
that you're doing this from a "Visual Studio .NET 2003 Command Prompt" - a
shortcut was installed in your start menu. That will open a command prompt
with all the right include, library and executable paths set correctly.

-cd
 
Back
Top