public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Milind <dmilind@india.hp.com>
To: Sarada prasanna <csaradap@mihy.mot.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Makefile or Shell file
Date: Thu, 09 Aug 2001 11:44:35 +0530	[thread overview]
Message-ID: <3B722A4B.B139BCC2@india.hp.com> (raw)
In-Reply-To: <C1590740235CD211BA5600A0C9E1F6FF0260226B@hydmail.mihy.mot.com>

I think any of them will help you out , but based on your requisites.

If you have tasks that are independent , then you can go for shell file and
execute
it using sh(sh-posix) or ksh(korn shell) or bash/ksh if you are using linux.

Makefile is generally used for a sequence of dependent tasks, normally the
makefile has a hierarchical structure, eg

target (exe): <a.o> <b.o>
                     <other dependencies like .a , .h  files>

a.o : cc  <options> a.c
        <other dependencies like .h , .a files>
b.o:  cc <options> b.c
        .
        .
        .

So its really question of nature of tasks.


Sarada prasanna wrote:

> I have a process here before which I have to complete  some pre required
> tasks ...Right now I do them manually.....i want an automated process that
> will do them automatically....
> Is there any way.....
>   will makefile or shell file come to my rescue....
>
>                                                 cspn
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2001-08-09  6:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09  5:34 Sarada prasanna
2001-08-09  6:14 ` Milind [this message]
2001-08-09  6:51 ` Automated tasks Riley Williams

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=3B722A4B.B139BCC2@india.hp.com \
    --to=dmilind@india.hp.com \
    --cc=csaradap@mihy.mot.com \
    --cc=linux-kernel@vger.kernel.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