0On Fri, Jan 27, 2023 at 02:05:08PM +0000, Stuart Henderson wrote: > On 2023/01/27 14:23, Alexandre Ratchov wrote: > > The above lines can be replaced with this, the other variables you've > listed above are set automatically: > > ---- > COMMENT= control sndiod with hot-keys and play keyboard bells > > GH_ACCOUNT= ratchov > GH_PROJECT= sndiokeys > GH_TAGNAME= v1.1.2 > > CATEGORIES= audio x11 > MAINTAINER= Alexandre Ratchov <[email protected]> > ---- > > It also needs > > MAKE_FLAGS= CC="${CC}" >
For the archives: it turns out that this is not necessary. In summary: When running "make CC=mycc build" in the ports tree, the CC=mybuild variable is set in the environment of the configure script, but not in the environment of the program's "make" run. So, if the program's Makefile (generated by the configure script) doesn't set CC, make will call "cc" instead of "mycc". But prior to running anything, the ports infrastructure creates a shell-script named "cc" in the PATH, which exececutes "mycc". So, the program will be built with "mycc" even if the program's Makefile makes no reference to it (make will log that "cc" is being run). > Otherwise ok. (FWIW for new ports I'd generally prefer a tar.gz that I > can just untar under mystuff or mystuff/category, a diff is more awkward > to apply). > thank you, note taken (as others suggested it in private as well)
