Using vcbuild to compile/link files from MSVC.NET 7.1

[3doutpost]

(apologies for the new thread - for some reason google news doesn't
give me the option to reply to an earlier vcbuild.exe thread)

I'm trying to build a C++ project that was originally created in
MSVC.NET 7.1 by using MS C++ Toolkit 2003 and the vcbuild.exe helper
app.

I did have MSVC.NET installed already and went ahead and installed MC
C++ Toolkit 2003. The 4 examples compiled okay.

Then I tried to compile my app using vcbuild.exe along with both the
..vcproj file and the .sln file and it seemed to work perfectly.

So, I uninstalled MSVC.NET, reboot and now I can't get it to build.

When I start vcbuild.exe in the same place as before, all I see are a
few blank lines - no errors messages but the files are not compiled,
linked, cleaned or anything whichever command line options I chose.

I invoked the option to display the environment and it looks okay -
PATH/LIB/INCLUDE vars all point to the right place.

Any ideas guys?

Thanks in advance.

3D.

 

[Tarek Madkour [MSFT]]

(e-mail address removed) (3doutpost) wrote in

When I start vcbuild.exe in the same place as before, all I see
are a few blank lines - no errors messages but the files are not
compiled, linked, cleaned or anything whichever command line
options I chose.

When no messages show at all, it's probably because we could not
locate vcprojectui.dll. Make sure that vcbuild.exe has vcproject.dll
in the same folder and vcprojectui.dll in a "1033" subfolder and that
should work.

 

[3doutpost]

When I start vcbuild.exe in the same place as before, all I see

When no messages show at all, it's probably because we could not
locate vcprojectui.dll. Make sure that vcbuild.exe has vcproject.dll
in the same folder and vcprojectui.dll in a "1033" subfolder and that
should work.

i followed some instructions in an earlier message and put
vcspawn.exe, vcprojectengine.dll, vcprojectui.dll and the .vcstyle
files in the same directory as vcbuild.exe and i am able to compile
stuff - losing vcspawn.exe broke things again and losing the .vcstyle
files caused all kinds of warnings to appear.

my problem now is linkage - i've installed all of the platform sdk and
the .net framework .sdk (to get msvcrt.lib/msvcrtd.lib) but it's still
looking for msvcprt.lib and msvcprtd.lib

i was hoping for a lightweight way to compile some simple opengl apps
on the command line but things seem to be getting out of control.

any suggestions?

 

[Ronald Laeremans [MSFT]]

See my other mail in this thread.

Ronald

i followed some instructions in an earlier message and put
vcspawn.exe, vcprojectengine.dll, vcprojectui.dll and the .vcstyle
files in the same directory as vcbuild.exe and i am able to compile
stuff - losing vcspawn.exe broke things again and losing the .vcstyle
files caused all kinds of warnings to appear.

my problem now is linkage - i've installed all of the platform sdk and
the .net framework .sdk (to get msvcrt.lib/msvcrtd.lib) but it's still
looking for msvcprt.lib and msvcprtd.lib

i was hoping for a lightweight way to compile some simple opengl apps
on the command line but things seem to be getting out of control.

any suggestions?

 

[Jonathan Wilson]

if you download this def file: (made from msvcp71.dll with dumpbin /exports)
http://users.tpg.com.au/adsloptd/msvcprt.def
and run it through LIB /def:msvcprt.def
you get what (I hope) is a usable msvcprt.lib.

IANAL but from what I know of the law (at least in australia) doing this is
legal...

 

[3doutpost]

if you download this def file: (made from msvcp71.dll with dumpbin /exports)

http://users.tpg.com.au/adsloptd/msvcprt.def
and run it through LIB /def:msvcprt.def
you get what (I hope) is a usable msvcprt.lib.

IANAL but from what I know of the law (at least in australia) doing this is
legal...

thanks jonathan - that seemed to work, but as you said, since i'm
ultimately trying to find a way for anyone build the project without
the full MSVC.NET installed, i'd need to see if this was legal or not
first.

there is another thread running (ah! - i see you've spotted it ) and
it sounds like the project is being linked with the 'wrong' libs but
since i can't change that, i'm not sure where to go from here.