[Octave-bug-tracker] [bug #47832] Another DOCSTRINGS file in the source tree

[Dan Sebald]

Follow-up Comment #5, bug #47832 (project octave):

I meant "derived from the same source-tree".  (Was thinking "tree" and
conflated with "branch".)

I should be clear, the "build-tarball" step would not put the DOCSTRINGS into
the source tree liboctave directory, except inside the tarball itself if that
is possible with the "tar" command.  Then, the tarball would be uncompressed
and the liboctave/DOCSTRINGS files are present so a conditional DOCSTRINGS
build step would recognize them and not build the DOCSTRINGS, but instead (and
this is important) simply copy those DOCSTRINGS files to the
build-dir/liboctave/ directory.  Otherwise, the DOCSTRINGS would be built as
part of compilation into the build-dir/liboctave/ directory.  That way, in
either scenario the DOCSTRINGS end up in the build-dir/liboctave directory
where the next step of build process can always find them.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47832>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/