linkage problems when building a VC7.1 project from the command line
- From: Bit byte <flip@xxxxxxxx>
- Date: Sun, 07 May 2006 08:40:53 +0100
I have a project that I normally build (without problems) from the DevStudio IDE. However, I have embarked on automating all my builds (this test project being one of several).
The project creates a DLL. I am able to build the project without any probs in the IDE, however - when I build the project from the command line (using the same options shown in the 'Command line' node in the 'Project Settings' dialog box), I get the following linkage problem (the compilation with cl.exe seems to work ok though) - however link.exe barfs like this:
link /OUT:timer.dll /INCREMENTAL /NOLOGO /DLL /DEBUG /SUBSYSTEM:WIND
OWS /IMPLIB:timer.lib /MACHINE:X86 Winmm.lib kernel32.lib user32.lib gdi32.lib winspool.lib advapi3
2.lib shell32.lib
LINK : warning LNK4001: no object files specified; libraries used
LINK : error LNK2001: unresolved external symbol __DllMainCRTStartup@12
timer.dll : fatal error LNK1120: 1 unresolved externals
Whats going on?. I suspect I must be using lib.exe somewhere along the line in the build process (or is this a red herring?)
.
- Follow-Ups:
- Re: linkage problems when building a VC7.1 project from the command line
- From: Marcus Heege
- Re: linkage problems when building a VC7.1 project from the command line
- From: Bruno van Dooren
- Re: linkage problems when building a VC7.1 project from the command line
- Prev by Date: Re: Calling a local C# Dll from Javascript!
- Next by Date: Re: linkage problems when building a VC7.1 project from the command line
- Previous by thread: Calling a local C# Dll from Javascript!
- Next by thread: Re: linkage problems when building a VC7.1 project from the command line
- Index(es):