Overview
Features
Download
Documentation
Community
Add-Ons & Services

VS2005 build error with 1.3.1

Please post support and help requests here.

VS2005 build error with 1.3.1

Postby rekkai » 30 Aug 2007, 19:50

The custom build step in the beginning fails with this error. I am using VS 2005 Professional Edition.

MC: may only specify one message file to compile.
MC: may only specify one message file to compile.
MC: may only specify one message file to compile.
MC: may only specify one message file to compile.
MC: may only specify one message file to compile.
MC: may only specify one message file to compile.
Microsoft (R) Message Compiler Version 1.12.2505
Copyright (c) Microsoft Corporation. All rights reserved.
usage: MC [-?aAcdnosuUvw] [-m maxmsglen] [-h dirspec] [-e extension] [-r dirspec] [-x dbgFileSpec] filename.mc
-? - displays this message
-a - input file is ANSI (default).
-A - messages in .BIN file should be ANSI.
-b - .BIN filename should have .mc filename_ included for uniqueness.
-c - sets the Customer bit in all the message Ids.
-d - FACILTY and SEVERITY values in header file in decimal.
Sets message values in header to decimal initially.
-e extension - Specify the extension for the header file.
From 1 - 3 chars.
-h pathspec - gives the path of where to create the C include file
Default is .
-m maxmsglen - generate a warning if the size of any message exceeds
maxmsglen characters.
-n - terminates all strings with null's in the message tables.
-o - generate OLE2 header file (use HRESULT definition instead of
status code definition)
-r pathspec - gives the path of where to create the RC include file
and the binary message resource files it includes.
Default is .
-s - insert symbolic name as first line of each message.
-u - input file is Unicode.
-U - messages in .BIN file should be Unicode (default).
-v - gives verbose output.
-w - warns if message text contains non-OS/2 compatible inserts.
-x pathspec - gives the path of where to create the .dbg C include
file that maps message Ids to their symbolic name.
filename.mc - gives the names of a message text file
to compile.
Generated files have the Archive bit cleared.
Project : error PRJ0019: A tool returned an error code from "Performing Custom Build Step"
rekkai
 
Posts: 11
Joined: 02 Aug 2007, 05:53
Location: United_States

Re: VS2005 build error with 1.3.1

Postby guenter » 31 Aug 2007, 08:10

Could it be the path to the POCO directory contains spaces? Unfortunately, MC does not like spaces in a path.
guenter
 
Posts: 1119
Joined: 11 Jul 2006, 16:27
Location: Austria

Re: VS2005 build error with 1.3.1

Postby rekkai » 31 Aug 2007, 20:45

Thanks, that was it! When I moved the Poco1.3.1 directory to be under say c:, the build was fine. Something for people to aware of.

Is it possible to make the mc exe take the argument with " " so that spaces in the path don't make it fall apart? I am sure others might run into the same issue.

rekkai
 
Posts: 11
Joined: 02 Aug 2007, 05:53
Location: United_States


Return to Support

Who is online

Users browsing this forum: No registered users and 1 guest

cron