|
| Re: package not building when XDCOPTIONS not set to -v [message #648205 is a reply to message #647983] |
Tue, 11 January 2011 18:35  |
 Dave Russo
Messages: 172
Registered: July 2009 |
Senior Member |
|
|
This looks like a command line length limitation issue. The command
that failed has 62158 characters(!).
If GNU make can execute a command directly (via CreateProcess()) it
will. If it can't, it uses the shell and, in the case of Windows, it
creates a batch file containing the commands to run. When you run with
XDCOPTIONS=-v, the echo command is being run via a batch file, but when
you don't use -v, GNU make uses CreateProcess(). I don't know why there
would be a difference in command line limits for CreateProcess() verses
a .bat file, but I can believe there is one.
The root cause of the problem is that ti.targets.ITarget is placing all
objects to be archived on a single line. It should be either using
multiple lines to archive the files, or creating an "@ file" that lists
the objects to be archived.
It looks like you already fixed the archive command with a target
filter. So it should be easy to fix the immediate problem: your filter
can simply redefine the .msg property to not be too long. For example:
function archive(container, lib, objList, archArgs, res)
{
/* replace archive command with a command file file */
res.cmds = mkCommandFile(container, res.cmds);
/* limit message length to 1024 characters */
res.msg = res.msg.substr(0, 1024) + " ...";
}
On 1/10/2011 8:54 AM, Patrick Geremia wrote:
> All,
>
> I get an error when building my package w/o the XDCOPTION set to -v. See
> attached files for complete log.
> The XDC tools version is 3_20_03_63.
>
> Any explanation? Is this a bug?
>
> Regards
> Patrick Geremia
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02600 seconds
] 
Search
Help
Register
Login
Home
