Here is a safer version: # cd ~/Backup rm -rf apl mkdir apl cd apl cp -rp ../gnu-apl.svn/* . ./configure make sudo make install
On Wed, May 13, 2015 at 6:15 AM, Blake McBride <blake1...@gmail.com> wrote: > I build with the following script: > > # > cd ~/Backup > mkdir apl > cd apl > rm -rf * > cp -rp ../gnu-apl.svn/* . > ./configure > make > sudo make install > > > This way my SVN copy is never touched. > > Blake > > > On Tue, May 12, 2015 at 9:45 AM, Juergen Sauermann < > juergen.sauerm...@t-online.de> wrote: > >> Hi Louis, >> >> The *SVN* number is written by *./configure*, so if you want it to be >> correct then you need to >> re-run *./configure* after *svn update*. But that number not too >> relevant so skipping this *./configure* >> is normally OK. >> >> The more important question is that of dependencies. The default >> *./configur**e* selects a "fast install" that >> skips some dependency checks. For a packet installed from the GNU APL >> project *tar* file that is OK but >> when working with *SVN* it is not because some changes in *.hh *and >> *.def* files will not be noticed. Therefore, >> when working from the *SVN* repository, you should do one of the >> following: >> >> 1. *make clean* after (every) *svn update* (OK but not optimal) >> 2. .*/configure* with -*-enable-maintainer-mode* (and possibly other >> options) >> 3. *make develop* after the first *./configure* >> >> 3. does 2. and a few more useful things like enabling assertions and >> dynamic logging. >> See *README-**2-configure* for details. >> >> 2. is needed only once and stays until the next *./configure* (which >> makes it better than 1.) >> >> You should also always do a *make install*, otherwise you could get >> conflicts between the *apl* >> binary and shared libraries if you start a new *apl* binary and it uses >> old shared libraries. >> >> /// Jürgen >> >> >> On 05/12/2015 03:47 PM, Louis Chretien wrote: >> >> After doing an update of my local working copy, with: >> >> svn update ./apl >> >> What are the commands required to rebuild APL? >> >> Right now, through trials and erros, i’ve come up with: >> >> make distclean (it seems that make clean is not enough, because the >> resulting APL doesn’t have the new SVN number) >> ./configure >> make >> >> Are there any other ways to do this? better? >> >> Thanks, >> >> --- >> Louis Chrétien >> lchret...@mac.com >> >> >> >> >> >> >
