On Fri, Mar 19, 2021 at 07:31:51PM +0100, [email protected] wrote:
>
> 8) Are there any other important ``make`` targets that could be useful to a
> user / low profile developer workflow?
All "make" targets that I expect user to use are in INSTALL
file:
make
make MAYBE_VIEWPORT=viewports
make viewports
make install
There is also "make check", it is important but I expect
(maybe wrongly) normal users to skip it. Then you have
make all-input
that I use for testing. Concerning "low profile developers",
I expect most of FriCAS developement to be done independently
of "make". So "make" targets are important only for final
testing. Note that adding files in normally can be done by
adding file names to appropriate lists of files in Makefile-s.
Of course some people will want to modify Makefile-s, then
you need to understand how "make" works and look at comments
in Makefile-s.
Concerning your other questions: "make" essentially is a
programming language which exposed internals of program
(that is Makefile) to the users. So the right question
is not "what make will do if I do some weird command?"
The right question is "how do I archive effect X?", where
X is one of things normally done with "make". Note
that many "make" targets are to support packagers
and FriCAS tries to follow common practice there,
in particular relevant parts of GNU coding standards.
--
Waldek Hebisch
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/fricas-devel/20210319224520.GB24079%40math.uni.wroc.pl.
