From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] Mkfile Project Template Advertisement
Date: Fri, 31 Jul 2020 11:03:55 +0100 [thread overview]
Message-ID: <36cf97e8-9257-4697-8187-ea38aa4b70f8@www.fastmail.com> (raw)
In-Reply-To: <5f0c402f-f1b2-4afe-7e7e-773132e6bd1c@gmail.com>
nice one! :D
i used to have a little bit of trouble with copying & adapting other mkfiles; not much, but to have it even easier is great!
On Fri, Jul 31, 2020, at 3:14 AM, Amavect wrote:
> Tired of writing a new mkfile for your external 9FRONT SYSTEM projects?
> Sick of having to add a new word to $OFILES when adding a new .c file?
>
> Introducing the ONLY mkfile you'll ever need! *
> Just add your C files to the src directory,
> and the mkfile knows how to build your program.
> Using advanced G.R.E.P. processing, the mkfile figures out which files
> contain a main entry point and builds those as executable programs.
> Automatic, mkfile magic!
>
> The Amavect Industries mkfile makes installing manual pages a breeze.
> Add as many man pages as you want; the mkfile can handle it all!
> It can even install rc scripts!
>
> There's nothing you can't do with the Amavect Industries mkfile! **
>
> I RM'D THIS DIRECTORY IN HALF
> and rebuilt it with only mkfiles!
> That's right, the mkfile supports uninstalling all installed files!
>
> That's the power of the Amavect project template mkfile.
>
> Download today at this webzone: https://git.sr.ht/~amavect/template
> or call 1-800-AMA-VECT to order now! ***
>
>
> *does not cover all use cases
> **some restrictions apply
> ***don't call that number
>
>
prev parent reply other threads:[~2020-07-31 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 2:14 Amavect
2020-07-31 2:26 ` Amavect
2020-07-31 6:22 ` [9front] " Xiao-Yong Jin
2020-07-31 11:43 ` Amavect
2020-07-31 10:03 ` Ethan Gardener [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36cf97e8-9257-4697-8187-ea38aa4b70f8@www.fastmail.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).