Re: [Help-bash] Help to add new builtin

[Joaquin Manuel Crespo]

Ok.
So if I can understand right, as "Makefile.in" is the template, adding a
".def" file into the builtins directory and then specifing the same (and
headers) into make file should be enogh to bash add the new builtin from
the directory.

Thank you for your time Greg, I will try it.

El jue., 8 de ago. de 2019 a la(s) 10:41, Greg Wooledge (address@hidden)
escribió:

> On Thu, Aug 08, 2019 at 10:29:10AM -0300, Joaquin Manuel Crespo wrote:
> > Great, thank you Greg.
> > For finish this, in the last case (add new builtin) when I create the
> > ".def" file in "bash-[version]/builtins" and then the respective entries
> in
> > "Makefile.in", Must I edit or add some more in another source file or
> when
> > bash is compiled will add/link all object files that are under the same
> > directory?
>
> I'm not the best person to teach you how to maintain a project that uses
> GNU autoconf and related tools, but the basics?  Maybe I can cover some
> of those.
>
> Makefile.in is a template that ./configure uses to generate Makefile.
>
> So, changes to Makefile.in do not require any re-running of autoconf
> or automake or any other GNU tools within the development tree.
>
> Such changes will be put into effect when the end user runs ./configure
> (or ../bash-5.0/configure or whatever) in their build directory.
>
> If you are not currently using separate development trees and build
> directories, I would strongly advise you to start doing so as soon as
> possible.  One of the worst mistakes you could make is to do everything
> all in the same directory, and then have no idea which parts did what.
>
> Other than that, learn by trial and error.  If you edit a file and then
> run ../bash-5.0/configure and make in the build directory and something
> doesn't work, then read the error messages, figure out what's wrong,
> fix it, and repeat.
>


-- 
Un cordial saludo.

*Joaquín Manuel Crespo.*

Gnu/Linux SysAdmin / C developper