Return-Path: 
 <ant-dev-return-25091-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@apache.org
Received: (qmail 44585 invoked from network); 10 Feb 2002 06:07:28 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 10 Feb 2002 06:07:28 -0000
Received: (qmail 19085 invoked by uid 97); 10 Feb 2002 06:07:34 -0000
Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org
Received: (qmail 19069 invoked by uid 97); 10 Feb 2002 06:07:34 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-dev-help@jakarta.apache.org>
List-Post: <mailto:ant-dev@jakarta.apache.org>
List-Id: "Ant Developers List" <ant-dev.jakarta.apache.org>
Reply-To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 19058 invoked from network); 10 Feb 2002 06:07:33 -0000
Message-ID: <004101c1b1f9$2df79d60$a800a8c0@CurtMicron>
From: "Curt Arnold" <carnold@houston.rr.com>
To: <ant-dev@jakarta.apache.org>
Cc: <ant-contrib-developers@lists.sourceforge.net>
Subject: <cc> status (was what's going on with 1.x)
Date: Sun, 10 Feb 2002 00:07:10 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_003E_01C1B1C6.E2D07DC0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

------=_NextPart_000_003E_01C1B1C6.E2D07DC0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I've been on the road the last week and was just browsing some of the =
"What's going on with Ant 1.x" thread on the ant-dev list.

One of the topics that was mentioned was the status of the <cc> task =
over in ant-contrib project at SourceForge.  I think it is premature to =
move it to the Apache CVS until we are able to build some serious =
projects with it and have refined it a bit more.  I'm just starting to =
use it to try to build Xerces-C and am finally able to spend working =
with it.  I'd hate to freeze the task syntax at this point.

In a previous message =
(http://www.geocrawler.com/lists/3/SourceForge/18057/0/7785927/) on the =
ant-contrib-developers mailing list, I discussed the problem on the =
parts of the compile fileset being dependent on properties.  For =
example, you'd only want to src/xercesc/util/NetAccessors/WinSock/*.cpp =
files compiled when "use-winsock" was defined and would have different =
files compiled when use-libwww, use-socket or use-macosurl were defined. =
=20

In that message, I described the problem and threw out a couple of ways =
of approaching the issue within the <cc> task.  However, with a little =
(but not much more) thought, it seems that adding an "if" and "unless" =
attribute to <fileset> (or maybe <includes> and <excludes>) might be a =
more generally useful approach.  However, I'll be the first to admit =
that I don't have a feel for how complicated that would be and whether =
it would be an affront to some Ant ethos.  (There would also need to be =
a "if" and "unless" on <defineset> or <define> and <undefine>, but that =
is within the cpptasks code).  If you are going to slam that suggestion, =
let me know how you would approach the problem.

I'll continue trying to build Xerces-C and will report the possibly =
unpretty trials and tribulations on the ant-contributors mailing list.  =
After we can build Xerces-C using VC on Win32 and gcc on Linux, then it =
would be a good opportunity with developers who have access to other =
platforms to up the supported compilers and platforms.  After that phase =
is complete, I'd think that <cc> would be ready to go mainstream.


------=_NextPart_000_003E_01C1B1C6.E2D07DC0--