octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Eliminating more recursive make invocations


From: Mike Miller
Subject: Re: Eliminating more recursive make invocations
Date: Sun, 12 Jul 2015 00:59:56 -0400
User-agent: Mutt/1.5.23 (2014-03-12)

On Tue, Jul 07, 2015 at 12:34:05 -0400, John W. Eaton wrote:
> I'm considering doing the same for the liboctave, libinterp, libgui, src,
> and scripts directory.  At that point, the only directory that will be
> handled by a recursive make invocation will be libgnu.

This looks like it's working for me with your latest changes, thanks for
keeping at it.

I just pushed a few fixes to restore 'make install', let me know if I
missed something.

I've compared the file contents of 'make install' to an older 4.1.0+
install, there are a few discrepancies that still need fixing:

 * a few missing files, including oct-hdf5-id.h, Array.cc-tst,
   Sparse.cc-tst
 * m-files are now installed to share/octave/4.1.0+/m/scripts
 * tests are now installed to share/octave/4.1.0+/etc/tests/fixed/tests,
   share/octave/4.1.0+/etc/tests/libinterp/libinterp, and
   share/octave/4.1.0+/etc/tests/liboctave/liboctave

I haven't tracked down the reason for the few missing files yet.

The m-file and test directory differences are because of Automake's
nobase feature. I think the only way to fix that might be to use custom
install-data-local rules for those files.

Another important change is that building Octave now always rebuilds the
documentation. This means that the documentation shipped in a dist
tarball will always be rebuilt after Octave is compiled. I haven't
tracked down the cause yet.

-- 
mike



reply via email to

[Prev in Thread] Current Thread [Next in Thread]