Ralf Hemmecke wrote:
>
> What is the right way to use mkdist.sh?
>
> Remember, I want to make the generation of the fricas.spkg more
> automatic. (And for that I have a few tweaks for the
> fricas-aldor-interface that can hopefully also go into 1.0.8.)
>
> I guess, that I first have to build fricas. But what are the exact
> commands so that mkdist.sh will work.
>
> I have a local build
> Ralf
>
> PS: Shouldn't the task of mkdist.sh be better done by makefile rules (so
> they would work for an in-place build and an out-of-source/vpath build?
>
Before using mkdist.sh you should do full bootstrap. If you
want to create a distribution you should also build graphic
.pht pages (othewise distribution you build will miss
images on HyperDoc pages). mkdist.sh works from top of build
tree. mkdist.sh copies sources and some "compiled" files from
build tree into 'dist' subdirectory of the build tree (the name
is hardcoded into the script). More precisely, mkdist.sh copies
generated Lisp files and .pht pages. For convenience mkdist.sh
may also copy some files which are not in build form SVN
sources -- that is noweb, gcl and help files. For noweb
and gcl one has to specify location of corresponding tarball,
for help files location of apropriate directory.
Proper use depens on what you want to do. One use is to
create release tarball, then we use:
mkdist.sh --copy_lisp --copy_gphts --copy_phts \
--copy_noweb=.... --copy_help=....
Actually, currently --copy_phts implies --copy_gphts
but this may change. For current distribution I did not
use the option to bundle gcl.
Another possibility is when for testing I want to re-build
FriCAS, but to save time I do not want to re-compile algebra
and re-build .pht pages. In such case --copy_noweb=... and
--copy_help=.... are of little use, so
mkdist.sh --copy_lisp --copy_phts
is enough.
Concerning .spkg, do you want to create .spkg from svn
snapshot? If you use releases as base for .spkg then
all mkdis.sh can do is already done.
Concerning making the process more automatic -- for me mkdist.sh
was enough. The point is that when creating release tarball
there are several steps that does not automate well. Namely,
making sure that X is available for building graphics, locating
extra files, checking test results.
> PS: Shouldn't the task of mkdist.sh be better done by makefile rules
> (so
> they would work for an in-place build and an out-of-source/vpath
> build?
>
mkdist.sh performs recursive copy which really works only for out
of source build.
Main criterion for mkdist.sh was simplicity and robustness. The
point is that I use mkdist.sh to make releases, so I want it to run
really reliably in controlled enviroment. Using make would mean
more complexity and conseqenty more effort to get it right. And
I am not sure if effect would be wort the effort.
--
Waldek Hebisch
[email protected]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/fricas-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
