C/C++ task

[Dave Smith <DS...@jabber.com>]

Greetings..

I recently started a transition for my company over to ant (from the
autotools suite), and along the way ran into a desperate need for a C/C++
Task. Since there didn't seem to be any, I wrote my own. It's fairly fully
featured, provides basic dependency engine, conditional defines, can link
static and shared libraries, etc. Anyways, I've gotten permission to
contribute it back to the Ant project and I'd like to do so. First off, is
the Ant project interested in such a task? (this seems a bit rhetorical..
:)) Secondly, what are the steps that I need to go through to get it
included? What are the standards for documentation, organization, etc..

I should note also that at this point the task is fairly gcc-centric, but
I've tried to make it as modular as possible because I need to support Sun's
Forte compiler as well.

Diz


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: C/C++ task

[Stefan Bodewig <bo...@apache.org>]

On Tue, 11 Dec 2001, Curt Arnold <ca...@houston.rr.com> wrote:

> There are some that feel that a C++ task is a distraction to Ant,
> others think a good C++ task would be very useful.

My recollection is a bit different.  At least I am just waiting for
the merged effort of the two implementations you are pointing to to be
submitted.

Stefan

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: C/C++ task

[Curt Arnold <ca...@houston.rr.com>]

There have been a couple of other C++ tasks that have been submitted for
consideration over the last few months and the response has been mixed.
There are some that feel that a C++ task is a distraction to Ant, others
think a good C++ task would be very useful.

You might want to review some of the recent threads on the topic,
http://marc.theaimsgroup.com/?l=ant-dev&w=2&r=1&s=gcc&q=b should be a start.

I had really good intentions to try to take the best features of the two
other C++ tasks and set up an area on the ant-contrib project at SourceForge
to try to work in the features that I would like.  My criteria for success
would be that Ant could be used to build Xerces-C and Xalan-C on all
supported platforms.  Of course, that would require the participation of
quite a few people, since I don't have a OS/390, AS/400 or 20 other
different platforms.

One of the things that seemed missing from the other tasks is a way to
specify compiler specific flags for multiple compilers in the task,
something like

<cpp...>
    <flags compiler="gcc" os="Win32" processor="x86" flags="..."/>
    <flags compiler="vc6" os="Win32" processor="x86" flags="..."/>
    <flags compiler="gcc os="Linux" processor="Alpha" flags="..."/>
</cpp>



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>