Hello Stéphane, Yes you should also commit the Makefile.in ; it should be provided within the source tree to ease Scilab macros and help pages development as these does not require autotools / vcproj manipulation.
Side note: some projects use a `./bootstrap` or ./autogen.sh` (mainly Gnome ones) to generate them using the machine local autotools ; we currently stick to Automake guidelines [1]. [1]: https://www.gnu.org/software/automake/manual/automake.html#CVS Thanks, -- Clément Le mardi 03 avril 2018 à 17:09 +0200, Stéphane Mottelet a écrit : > Hello devs, > > I would like to know what is the policy when *new* source files (C,C++ > or Java) are added when fixing a bug or adding a feature. A explained in > > https://wiki.scilab.org/Scilab%20Module%20Architecture > > when new source files are added in a module, Makefile.am has to mention > these files but Makefile.in can only be regenerated by running > autoreconf at the main SCI folder. > > So, should I add the resulting Makefile.in in my commit ? > > S. > > _______________________________________________ dev mailing list [email protected] http://lists.scilab.org/mailman/listinfo/dev
