public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ming Cheng <chengm349@hotmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Fw: Makefile format
Date: Tue, 21 Jun 2022 08:49:27 +0000	[thread overview]
Message-ID: <SI2PR03MB5242442233067D919743B94DFBB39@SI2PR03MB5242.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <SI2PR03MB5242F39C786CA8C53496F745FBB39@SI2PR03MB5242.apcprd03.prod.outlook.com>


________________________________
From: Ming Cheng <chengm349@hotmail.com>
Sent: Tuesday, June 21, 2022 8:41 AM
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Re: Makefile format

Hi Jonathan Wakely,

Thanks for your kind first step. I should have made my question more clearer.

We have a module called abc. Amazingly user can just define abc_type, abc_target; and GNU make seems to me that  according to its rules will implicitly look for these bars if defined. Does the same doc have these rules description?

Thanks
Ming
________________________________
From: Jonathan Wakely <jwakely.gcc@gmail.com>
Sent: Monday, June 20, 2022 6:45 AM
To: Ming Cheng <chengm349@hotmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Makefile format



On Mon, 20 Jun 2022, 05:58 Ming Cheng via Gcc-help, <gcc-help@gcc.gnu.org<mailto:gcc-help@gcc.gnu.org>> wrote:
Hi,

In a .mk makefile, there are these kinds of lines:
modules := abc  xyz
abc_type := static_library
abc_target := libabc.a


I know traditional Makefile format(simple usage). Where can find these "new" format guide?

GCC requires GNU Make. This syntax is documented in the GNU Make manual:

https://www.gnu.org/software/make/manual/html_node/Flavors.html#Flavors



Thanks
Ming Cheng

  parent reply	other threads:[~2022-06-21  8:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  4:57 Ming Cheng
2022-06-20  6:45 ` Jonathan Wakely
     [not found]   ` <SI2PR03MB5242F39C786CA8C53496F745FBB39@SI2PR03MB5242.apcprd03.prod.outlook.com>
2022-06-21  8:49     ` Ming Cheng [this message]
2022-06-21  9:42       ` Fw: " Jonathan Wakely
2022-06-21 11:55         ` Paul Smith
2022-06-22  3:12           ` Ming Cheng
2022-06-22 14:06             ` Paul Smith

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=SI2PR03MB5242442233067D919743B94DFBB39@SI2PR03MB5242.apcprd03.prod.outlook.com \
    --to=chengm349@hotmail.com \
    --cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).