Date: Thu, 25 Apr 2024 19:18:06 +0100 From: "Souji Thenria" <mail@souji-thenria.net> To: "Tomek CEDRO" <tomek@cedro.info>, "Kyle Evans" <kevans@freebsd.org> Cc: <questions@freebsd.org> Subject: Re: bsd sed / make vs bsd sed / make Message-ID: <D0TES3TCD38Z.BPRK4LWVQGFP@souji-thenria.net> In-Reply-To: <CAFYkXj=nRJ6VRV=nVab12zT=MdM_x=uTaWnHk1KSh==5p8p2dg@mail.gmail.com> References: <CAFYkXjnq7LB3mhnK4vtQ0p_YJfSU5OOCWgcF6sm64FTCN8gF8Q@mail.gmail.com> <493f8ca1-75e1-4ae6-8641-5998c53457cb@FreeBSD.org> <CAFYkXj=nRJ6VRV=nVab12zT=MdM_x=uTaWnHk1KSh==5p8p2dg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu Apr 25, 2024 at 6:59 PM BST, Tomek CEDRO wrote: > Well it will not be a port just local git clone bootstrapped per > project. No hardcoded paths to sed luckily :-) Just wondering what are > the best practices to turn BSD make run GNU make a simple bsd only > makefile that would wrap make wall with gmake or something ? Not > really a big problem I can use it with gmake just want to make life > easier for other users :-) Hi Tomek, Wrapping gmake with make would work. You can also create a shell script which runs gmake from inside the project directory. Trying to convert the syntax is probably not worth the effort. Regards, Souji
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D0TES3TCD38Z.BPRK4LWVQGFP>