[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Introducing Autoperl
From: |
Jeff Fulmer |
Subject: |
Re: Introducing Autoperl |
Date: |
Wed, 30 Mar 2005 09:00:07 -0500 |
User-agent: |
Mutt/1.4.2i |
I'm a little busy, but I'll check this out when I get a chance. I've
used autoconf for perl programs but it's a square peg round hole
situation. Here's an example: ftp://ftp.joedog.org/pub/sproxy/
Your project sounds promising.
Jeff
On Tue, Mar 29, 2005 at 11:10:14PM -0500, address@hidden wrote:
> Hello,
>
> I'd like to let the Autoconf developers know about a related project I'm
> working on. It's called Autoperl, and it's a partial reimplementation of
> Autoconf/Automake but written in Perl. It tries to be 100% syntax
> compatible with the GNU toolchain, and uses the same terminology and
> concepts.
>
> "Why would anyone do such a stupid thing?", you might ask...
>
> I am a veteran Perl programmer, but I have always admired the Autoconf
> configuration system and wanted something similar for my Perl programs.
> Autoconf is *really* geared towards C/C++ development, and doesn't mesh
> well with Perl, IMHO. (Yes, I know about the bin_SCRIPTS macro)
>
> What Autoperl does differently is:
>
> * Automatically checks for Perl library dependencies
>
> * Validates the syntax of all Perl source code files during the
> compilation phase
>
> * Combines all Perl modules into a single file like ld(1)
>
> * Creates a "config.h" in pure Perl and exports the
> configuration variables into the application.
>
> "But this is the Autoconf list; I don't care about Autoperl!" you may
> say...
>
> I wanted the Autoconf developers to be aware of this new project and to
> think of ways of connecting Autoperl with Autoconf. It should be
> possible to implement the Autoperl-specific macros as native Autoconf
> macros. My goal is for Autoperl to work silently in the background and
> do as little as possible, while Autoconf/Automake calls upon Autoperl as
> needed.
>
> One final thought: the next version of Autoperl will support a 'make
> package' target that will run 'make install DESTDIR=/tmp/foo' and
> package the results as a native binary package (RPM,DEP,TGZ,etc.) This
> would enable developers to build native packages for many different
> systems and architectures without any extra effort.
>
> It would be great if Autoperl and Autoconf could cooperate!
>
> The Autoperl home page is:
>
> http://heily.com/~mark/projects/autoperl
>
> You can reach me at:
>
> address@hidden
>
> Regards,
>
> Mark Heily
> Chief Autoperl hacker
>
>
> _______________________________________________
> Autoconf mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/autoconf
>
--
#include <stdio.h>
int main(){int a[]={74,117,115,116,32,97,110,111,116,104,101,114,32, \
67,32,104,97,99,107,101,114,10,0}; int *b=a;while(*b>0)putchar(*b++);}