Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Received-SPF: pass (nike.apache.org: domain of
 prvs=539142702f=shawn.castrianni@halliburton.com designates 34.254.247.12 as
 permitted sender)
From: Shawn Castrianni <Shawn.Castrianni@halliburton.com>
To: "'Ant Users List'" <user@ant.apache.org>
Date: Wed, 20 May 2009 03:24:12 -0500
Subject: prepend to cpptasks command line
Thread-Topic: prepend to cpptasks command line
Thread-Index: AcnZJFq3BEdqLkh1QtO9xCyqiAezWA==
Message-ID: 
 <34721A41A7BCF54ABC3B116219A8C1C2057525715F@NP1EXCH012.corp.halliburton.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_34721A41A7BCF54ABC3B116219A8C1C2057525715FNP1EXCH012cor_"
MIME-Version: 1.0

--_000_34721A41A7BCF54ABC3B116219A8C1C2057525715FNP1EXCH012cor_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"

What is the easiest way for me to prepend stuff to the command line that th=
e cpptasks plugin generates before execution?  I am trying to integrate my =
build with coverity which requires prepending the C/C++ command line with i=
ts own command and parameters.  My ideas so far:


1.       use the libtool option, but alias or override the libtool executab=
le with the coverity command and parameters

2.       make my own compiler processor class that can be specified within =
the cpptasks xml tags and override the getCommand() method to return the co=
verity command and parameters before the real g++ command.  This doesn't wo=
rk since getCommand is a final method.

3.       hack up cpptasks source code and make my own cpptasks.jar

---
Shawn Castrianni

----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and pri=
vileged information for the sole use of the intended recipient.  Any review=
, use, distribution, or disclosure by others is strictly prohibited.  If yo=
u are not the intended recipient (or authorized to receive information for =
the intended recipient), please contact the sender by reply e-mail and dele=
te all copies of this message.

--_000_34721A41A7BCF54ABC3B116219A8C1C2057525715FNP1EXCH012cor_--