You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by ax...@ws.apache.org on 2004/10/25 03:41:26 UTC

[jira] Commented: (AXISCPP-221) improve makefile.in

The following comment has been added to this issue:

     Author: Samisa Abeysinghe
    Created: Sun, 24 Oct 2004 6:40 PM
       Body:
I propose that we remove Makefile.in from cvs and keep only Makefile.am in the cvs.

If we do this, people who checkout from CVS would need to use auto amke tools to build the source. (This want be a problem as those who want to get it form CVS must be having enough know-how on how to get the auto tools working - alternatively for those who do not wish to use auto tools the Ant script is there)

When it comes to releases, developers could use auto tools and use 'make dist' to create the dist packgae having the configure script, so that those who download may not require to use auto tools but use the './configure;make; make install' triple.

---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXISCPP-221?page=comments#action_54567

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-221

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-221
    Summary: improve makefile.in
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Axis-C++
   Fix Fors:
             1.4 Beta
   Versions:
             1.3 Final

   Assignee: 
   Reporter: John Hawkins

    Created: Fri, 22 Oct 2004 6:49 AM
    Updated: Sun, 24 Oct 2004 6:40 PM
    Due:     Fri, 26 Nov 2004 12:00 AM

Description:
Currently we use makefile.in. These are causing us a headache so we must improve on them


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira