[phc-general] How to make a distribution
Satyam at satyam.com.ar
Tue Aug 29 18:45:15 CEST 2006
Since I've been out of touch for a while, you might have suspected I was out
on vacation. Well, sort of, it was friends & family who came our way and we
had a joyful though somewhat busy time. In no way have I lost interest in
So, I got myself into building a distribution for my project, with PHC plus
my changes. This is now available as a download at www.satyam.com.ar/pht.
I also changed the name of the project, from PhpSt to PHT which is shorter.
So I changed the name of the executable accordingly and the site, and the
distribution tar file and so on. Just in case, I put a redirect on the
I did the changes to makefile.am as you sugested below and tried to rebuild
it which, of course, failed. Since I didn't know the whole process it took
a while until I figured to run aclocal and automake. Actually, the error
message from automake pointed me to aclocal, I just had to learn what
automake was, which is good so I end up getting some experience in this.
As I was changing things and building, a warning told me that phc-1.0.xsd
didn't show amongst the destination files, which I added amongst the list of
destinations for maketea. Another file produced is README.TreeTransform,
which is not listed, but not required anywhere and it doesn't seem to be
anything but a kind of log file of what happened, so it seems it doesn't
hurt to leave it out. Also, in the same section, after moving schema.xsd
to phc-1.0.xsd I added a line to create the symbolic link to the root, just
in case you actually start with an empty /generated directory.
----- Original Message -----
From: "Edsko de Vries" <edsko at phpcompiler.org>
To: "Satyam" <Satyam at satyam.com.ar>
Cc: <phc-general at phpcompiler.org>
Sent: Saturday, August 12, 2006 10:33 AM
Subject: Re: [phc-general] How to make a distribution
> On Fri, Aug 11, 2006 at 07:43:09PM +0200, Satyam wrote:
>> I was about to list the files I got with the files in the regular
>> distribution to figure out which ones go into the distribution and which
>> don't, to build the download of my version. I was wondering if there
>> any easier way, some 'make something' that would clean it all up.
> Hmmm. "make dist" _ought to_ sort that out, but in fact doesn't. The
> reason is that our Makefile.am is not careful enough to list each and
> every file that is needed for a distribution. Instead, we use a
> shellscript that creates releases for us. However, this shellscript is
> not distributed with phc, because it needs information that is not
> available from within the phc source tree.
> I think the easiest way would be to make a small scriptscript that
> copies all the files you need into a new folder, and then tar up that
> folder. A bit of work, but a once-off investment.
>> Also, where would I change the name of the final executable? It wouldn't
>> be Ok to let it have the same name since it doesn't have the same
>> functionality. Since many of the files depend on each other, if I touch
>> of the productions instead of the root, I'll mess it all up.
> To change the name of the executable to "phcst" (say), you must modifiy
> Makefile.am. You will find a line
> bin_PROGRAMS = phc
> change that to
> bin_PROGRAMS = phcst
> then you will find another line
> phc_SOURCES = \
> and change that to
> phcst_SOURCES = \
> (be careful not to insert a space after that final backslash).
> I think that should do it.
> phc-general mailing list
> phc-general at phpcompiler.org
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.405 / Virus Database: 268.10.9/417 - Release Date: 11/08/2006
More information about the phc-general