Re: [A-A-P-develop] Libtool support (was: changing filetypes)

[Bram M. <Br...@mo...>]

Adriaan de Groot wrote:

> On Thursday 31 July 2003 13:25, Bram Moolenaar wrote:
> > 	:program myprog {var_LTLIBS = libmine} : source.c
> >
> > Doesn't this look simpler than changing the filetype of the program?
> > Especially since it's still the same kind of program.  Using the
> > filetype to build a program in a different way works, but it does not
> > sound logical to me.
> 
> This looks quite workable, though you'd need to decide on those
> variables, and document the possible combinations of things to build.
> ie. suppose that you have regular executables, litool exes, and
> objprelink executables; what to do with
> 
> 	:program myprog { var_LTLIBS = libmine } { var_OBJPRELINK = all } : source.c

Eh, what is an objprelink executable?  Does it require another kind of
building as well?

If this is a combination that happens often (e.g., for people compiling
KDE applications) then Aap should support this.  We would not want to
shift the problem towards the user.

> What kinds of costs does that bring to default.aap and the python code
> that's there? Would checking these combinations be prohibitive? If
> invalid combinations only become visible at the end when the :build
> action is performed, this might be a problem, since then debugging the
> recipe becomes rather time-consuming.

Well, the idea is that Aap does automatically what it can.  At least for
tasks that more than a few people will use.  Obscure things would still
have to be spelled out in detail, like you would do in a Makefile.

How much work it is to implement is less important.  It only needs to be
done once for all users, instead of that every user has to do it.  We
will want to find ways to avoid implementing every combination of
options, of course.

I think problems would be detected quite early, since an action to build
the program would be missing.  But sometimes you might only find out
that it doesn't work when a variable you specified isn't recognized.
E.g. when you typed var_LTLIPS instead of var_LTLIBS.  There is no
check for unused attributes.  But my experience so far is that you
discover problems quick enough (if you can't spot the typo in var_LTLIPS
you have a problem...).

-- 
How To Keep A Healthy Level Of Insanity:
11. Specify that your drive-through order is "to go".

 /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///