Kinook Software Forums

Go Back   Kinook Software Forums > Visual Build Professional > [VBP] Third Party Tools

Reply
 
Thread Tools Rating: Thread Rating: 2 votes, 5.00 average. Display Modes
  #1  
Old 07-02-2003, 12:20 PM
tapruden tapruden is online now
Registered User
 
Join Date: 07-02-2003
Posts: 4
Angry Target not found after building

I have a script in which I'm building 20+ C++ projects using the Visual Studio compiler. I have them all set to increment the version number. One of them, however, fails when it tries to perform this task.

I can see the message in the log:

<programname>.exe - 0 error(s), 0 warning(s)

Then, where the increment step is supposed to happen, I see the following error message:

Target not found after building

This is the only project out the 20+ for which this occurs. I compared the Visual Studio project settings for the project in question with a similar one, and they are identical.

Anyone have any ideas?
Reply With Quote
  #2  
Old 07-02-2003, 12:24 PM
tapruden tapruden is online now
Registered User
 
Join Date: 07-02-2003
Posts: 4
Oh, and I forgot to mention that this happens when I try to build everything in Release version. The Debug version of the script runs fine... no errors.
Reply With Quote
  #3  
Old 07-03-2003, 07:48 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 5,657
Sounds like there's something different about how the target filename is specified for that project's release configuration, which the Make VC6 action is unable to parse. Can you post the .dsp file in question?
Reply With Quote
  #4  
Old 07-17-2003, 05:04 PM
tapruden tapruden is online now
Registered User
 
Join Date: 07-02-2003
Posts: 4
Here's the project file...

# Microsoft Developer Studio Project File - Name="MyProject" - Package Owner=<4>
# Microsoft Developer Studio Generated Build File, Format Version 6.00
# ** DO NOT EDIT **

# TARGTYPE "Win32 (x86) Console Application" 0x0103

CFG=MyProject - Win32 Debug
!MESSAGE This is not a valid makefile. To build this project using NMAKE,
!MESSAGE use the Export Makefile command and run
!MESSAGE
!MESSAGE NMAKE /f "MyProject.mak".
!MESSAGE
!MESSAGE You can specify a configuration when running NMAKE
!MESSAGE by defining the macro CFG on the command line. For example:
!MESSAGE
!MESSAGE NMAKE /f "MyProject.mak" CFG="MyProject - Win32 Debug"
!MESSAGE
!MESSAGE Possible choices for configuration are:
!MESSAGE
!MESSAGE "MyProject - Win32 Release" (based on "Win32 (x86) Console Application")
!MESSAGE "MyProject - Win32 Debug" (based on "Win32 (x86) Console Application")
!MESSAGE

# Begin Project
# PROP AllowPerConfigDependencies 0
# PROP Scc_ProjName ""$/GHMW/MyProject", ZIEAAAAA"
# PROP Scc_LocalPath "."
CPP=cl.exe
RSC=rc.exe

!IF "$(CFG)" == "MyProject - Win32 Release"

# PROP BASE Use_MFC 0
# PROP BASE Use_Debug_Libraries 0
# PROP BASE Output_Dir "Release"
# PROP BASE Intermediate_Dir "Release"
# PROP BASE Target_Dir ""
# PROP Use_MFC 0
# PROP Use_Debug_Libraries 0
# PROP Output_Dir "Release"
# PROP Intermediate_Dir "Release"
# PROP Ignore_Export_Lib 0
# PROP Target_Dir ""
# ADD BASE CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /c
# ADD CPP /nologo /MD /W3 /GR /GX /Zi /O2 /I "..\include" /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /c
# ADD BASE RSC /l 0x409 /d "NDEBUG"
# ADD RSC /l 0x409 /d "NDEBUG"
BSC32=bscmake.exe
# ADD BASE BSC32 /nologo
# ADD BSC32 /nologo
LINK32=link.exe
# ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:console /machine:I386
# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:console /debug /machine:I386 /nodefaultlib:"libcmt.lib" /libpath:"..\Libs" /libpath:"$(GHMWROOT)\APIs\Espeed\Lib" /libpath:"$(GHMWROOT)\APIs\EurexAce\Lib" /libpath:"$(GHMWROOT)\APIs\CME\Lib" /libpath:"$(GHMWROOT)\APIs\Liffe\Lib" /libpath:"$(GHMWROOT)\APIs\BTec\Lib" /OPT:REF
# SUBTRACT LINK32 /pdb:none

!ELSEIF "$(CFG)" == "MyProject - Win32 Debug"

# PROP BASE Use_MFC 0
# PROP BASE Use_Debug_Libraries 1
# PROP BASE Output_Dir "Debug"
# PROP BASE Intermediate_Dir "Debug"
# PROP BASE Target_Dir ""
# PROP Use_MFC 0
# PROP Use_Debug_Libraries 1
# PROP Output_Dir "Debug"
# PROP Intermediate_Dir "Debug"
# PROP Ignore_Export_Lib 0
# PROP Target_Dir ""
# ADD BASE CPP /nologo /W3 /Gm /GX /ZI /Od /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /GZ /c
# ADD CPP /nologo /MDd /W3 /Gm /GR /GX /ZI /Od /I "..\include" /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /GZ /c
# ADD BASE RSC /l 0x409 /d "_DEBUG"
# ADD RSC /l 0x409 /d "_DEBUG"
BSC32=bscmake.exe
# ADD BASE BSC32 /nologo
# ADD BSC32 /nologo
LINK32=link.exe
# ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:console /debug /machine:I386 /pdbtype:sept
# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:console /debug /machine:I386 /nodefaultlib:"libcmt.lib" /out:"Debug/MyProjectD.exe" /pdbtype:sept /libpath:"..\Libs" /libpath:"$(GHMWROOT)\APIs\Espeed\Lib" /libpath:"$(GHMWROOT)\APIs\EurexAce\Lib" /libpath:"$(GHMWROOT)\APIs\CME\Lib" /libpath:"$(GHMWROOT)\APIs\Liffe\Lib" /libpath:"$(GHMWROOT)\APIs\BTec\Lib"

!ENDIF

# Begin Target

# Name "MyProject - Win32 Release"
# Name "MyProject - Win32 Debug"
# Begin Group "Source Files"

# PROP Default_Filter "cpp;c;cxx;rc;def;r;odl;idl;hpj;bat"
# Begin Source File

SOURCE=.\main.cpp
# End Source File
# Begin Source File

SOURCE=.\MyProject.cpp
# End Source File
# Begin Source File

SOURCE=.\MyProject.rc
# End Source File
# End Group
# Begin Group "Header Files"

# PROP Default_Filter "h;hpp;hxx;hm;inl"
# Begin Source File

SOURCE=.\MyProject.h
# End Source File
# Begin Source File

SOURCE=.\resource.h
# End Source File
# End Group
# End Target
# End Project
Reply With Quote
  #5  
Old 07-22-2003, 10:05 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 5,657
I'm not sure why this isn't working for you. The Release configuration doesn't specify the output file, so it would normally be generated by MSDEV (and looked for by VisBuildPro after building) as .\Release\MyProject.exe (relative to the location of the .dsp file).
Reply With Quote
  #6  
Old 07-22-2003, 10:09 AM
tapruden tapruden is online now
Registered User
 
Join Date: 07-02-2003
Posts: 4
So, is the target in the message "Target not found after building" the executable or is the Visual Build software looking for a different file?
Reply With Quote
Reply

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 06:25 AM.


Copyright 1999-2019 Kinook Software, Inc.