POMAKE: fatal error: Don't know how to make 'cc'.

[colepc]

I am trying to convert an IDE project into a command line equivalent. I am currently using Version 7.00.355 (Win64). I have a project called "Test2x" which runs fine using the IDE. For my command line equivalent I keep getting this error message: POMAKE: fatal error: Don't know how to make 'cc'.
What does this mean and what could I be doing wrong?

I set my environment using these command statements:
set PellesCDir=C:\Program Files\PellesC
set PATH=%PellesCDir%\Bin;%PATH%
set INCLUDE=%PellesCDir%\Include;%PellesCDir%\Include\Win;%INCLUDE%
set LIB=%PellesCDir%\Lib;%PellesCDir%\Lib\Win;%LIB%

I change to my project directory using this command statement:
cd C:\Users\colepc2\Documents\Pelles C Projects\Test2x

I use "Make.bat" to run pomake which has these statements:
pomake /f Test2x.ppj >>xx.txt
type xx.txt
@pause

POMAKE reports the following (always two fatal errors and several "OK" statements that grow by one each time I run "Make.bat"):
POMAKE: fatal error: Don't know how to make 'cc'.
POMAKE: fatal error: Don't know how to make 'cc'.
'Test2x.exe' is OK.
'Test2x.exe' is OK.
'Test2x.exe' is OK.
'Test2x.exe' is OK.
'Test2x.exe' is OK.
'Test2x.exe' is OK.
'Test2x.exe' is OK.
'Test2x.exe' is OK.
'Test2x.exe' is OK.

"Test2x.ppj" has the following (same as used by the IDE that runs successfully - OK I didn't observe the WARNING but I wanted all file names to be the same as my project file name):
#
# PROJECT FILE generated by "Pelles C for Windows, version 7.00".
# WARNING! DO NOT EDIT THIS FILE.
#

POC_PROJECT_VERSION = 7.00#
POC_PROJECT_TYPE = 10#
POC_PROJECT_OUTPUTDIR = output#
POC_PROJECT_RESULTDIR = .#
POC_PROJECT_ARGUMENTS = #
CC = pocc.exe#
AS = poasm.exe#
RC = porc.exe#
LINK = polink.exe#
SIGN = posign.exe#
CCFLAGS = -Tamd64-coff -Ot -W1 -Ze -std:C11#
ASFLAGS = -AAMD64#
RCFLAGS = -r#
LINKFLAGS = -machine:amd64 -subsystem:windows kernel32.lib user32.lib gdi32.lib comctl32.lib comdlg32.lib advapi32.lib delayimp64.lib#
SIGNFLAGS = -location:CU -store:MY -timeurl:http://timestamp.verisign.com/scripts/timstamp.dll -errkill#
INCLUDE = $(PellesCDir)\Include\Win;$(PellesCDir)\Include#
LIB = $(PellesCDir)\Lib\Win64;$(PellesCDir)\Lib#
WizCreator = Pelle Orinius#

#
# Build Test2x.exe.
#
Test2x.exe: \
   output\Test2x.obj \
   output\Test2x.res
   $(LINK) $(LINKFLAGS) -out:"$@" $**

#
# Build Test2x.obj.
#
output\Test2x.obj: \
   Test2x.c \
   Test2x.h
   $(CC) $(CCFLAGS) "$!" -Fo"$@"

#
# Build Test2x.res.
#
output\Test2x.res: \
   Test2x.rc \
   Test2x.h \
   Test2x.ico
   $(RC) $(RCFLAGS) "$!" -Fo"$@"

.SILENT:

[czerny]

I use "Make.bat" to run pomake which has these statements:
pomake /f Test2x.ppj >>xx.txt
type xx.txt
@pause

POMAKE reports the following (always two fatal errors and several "OK" statements that grow by one each time I run "Make.bat"):

Use a single '>':

Code: [Select]

pomake /f Test2x.ppj >xx.txt

[colepc]

Thanks Czerny. I can finally command line compile not realizing that I was already doing it. I'm a happy camper  .

As you know, the double >> was appending opmake messages to the file "xx.txt" giving me old error messages that I thought were new error messages. The >> came from an old make file of mine that I did back in 2001. I'm sure there was a reason for using it back then but now I have forgotten why. Thanks again.