Le mar. 24 nov. 2020 à 20:41, andy pugh <bodge...@gmail.com> a écrit :
> On Tue, 24 Nov 2020 at 09:42, Les Newell <les.new...@fastmail.co.uk> > wrote: > > The issue I was trying to address is with the .comp files that create > many of the HAL components. These contain documentation as part of the > file, but those strings are not part of the compiled C file, but > instead create manpages as part of the halcompile process. > Does halcompile have an option to only generate man the pages? This could be triggered on commits on GH? Well, as hal manpages are there, may be this is already in place? 🤔 Likewise, the 'po' submake could be called to generate/update automatically the base linuxcnc.pot file. This file is not in the repository, whereas it's mentioned in the po's readme, and is missing for a clean translation toolchain setup as a reference. For instance, Crowdin seem to need a reference file to translate and doesn't like managing all translations without a common ground. > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
