[ http://issues.apache.org/jira/browse/GUMP-32?page=all ]
     
Leo Simons closed GUMP-32:
--------------------------

    Resolution: Fixed

Stefan implemented this a while ago. See the apr project as an example.

> support configure/make/automake
> -------------------------------
>
>          Key: GUMP-32
>          URL: http://issues.apache.org/jira/browse/GUMP-32
>      Project: Gump
>         Type: New Feature
>   Components: Python-based Gump
>     Versions: Gump2
>     Reporter: Leo Simons
>      Fix For: Gump2

>
> Gump currently knows how to interact with ant, and work is in progress on 
> interacting with maven, but gump doesn't know how to behave like (for 
> example) a C programmer.
> To build these kinds of projects, the GOM needs to change to have things like 
> <configure/>, <make/>, <automake/> and <rpmbuild/>. In addition, I think we 
> need to have a <sequence/>, because building many projects is a sequence of 
> commands. Example (incomplete snippets):
> <project name="apache-httpd-prefork">
>   <sequence>
>     <script name="buildconf"/>
>     <configure>
>       <argument project="apxs-install"
>            value="--with-apxs=${installdir}"/>
>       <argument value="--with-mpm=prefork">
>     </configure>
>     <make/>
>   </sequence>
> </project>
> <project name="apache-httpd-prefork-install">
>   <make target="install"/>
>   <installdir value="build/install/prefork"/>
>   <depend project="apache-httpd-prefork"/>
> </project>
> <project name="apache-httpd-prefork-rpm">
>   <rpmbuild specfile="build/rpm/httpd.spec.in"/>
>   <depend project="apache-httpd-install"/>
> </project>
> Besides changing the GOM, we need to check for the existence of these tools 
> (and figure out what to check for). Maybe we also need to implement some 
> generic property expansion...
> ...an option for getting this in place quickly is delegating these new tags 
> to ant buildfiles. The disadvantage from calling the tools directly might be 
> that what ant does differs a little from what the tools do by themselves...
> ...but if we go through ant for integrating these things, we can work 
> incrementally by creating some manual ant files for the first few projects 
> first. That might give good insight in what these tags need to look like.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to