From: hwidjaja@my-deja.com
To: help-gcc@gnu.org
Subject: Re: using make on big Java projects
Date: Thu, 02 Dec 1999 19:54:00 -0000 [thread overview]
Message-ID: <827e3b$cku$1@nnrp1.deja.com> (raw)
In-Reply-To: <3845C34E.4FFB923A@usa.net>
if you handling lot of files in a big project, I recommend OTC makeit
(www.dscpl.com.au) which has the capability to handle Java files.
however, it takes a while to setup, but once you get it going..
OTC makeit is really useful.
fyi, otc makeit uses gnu make ...
cheers,
hwidjaja
In article < 3845C34E.4FFB923A@usa.net >,
oneself <oneself@usa.net> wrote:
> Hi!
>
> I have just recently started writing makefiles and using make.
> and I want to it on an already existing, very big Java project
> that contains something like 500 files in an elaborate tree structure.
> from the brief but decisive acquaintance I had with make there was
> one thing that became obvious to me, and that is that I had to
actually
> put in every file name in the make file. and,if I was bored enough,
> their dependencies.
>
> my first question is, am I right or wrong. if I'm wrong then how can
> I make make make my whole project with out putting in every
> file name in the makefile.
> if I'm write, are there any tools out there that make this task easier
> to manage.
>
> thanks.
>
>
Sent via Deja.com http://www.deja.com/
Before you buy.
WARNING: multiple messages have this Message-ID
From: hwidjaja@my-deja.com
To: help-gcc@gnu.org
Subject: Re: using make on big Java projects
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <827e3b$cku$1@nnrp1.deja.com> (raw)
Message-ID: <19991231222400.c0i-UNGZZeg5P9UXO8qQcM94BBt3KhfTPbOAEUgraWg@z> (raw)
In-Reply-To: <3845C34E.4FFB923A@usa.net>
if you handling lot of files in a big project, I recommend OTC makeit
(www.dscpl.com.au) which has the capability to handle Java files.
however, it takes a while to setup, but once you get it going..
OTC makeit is really useful.
fyi, otc makeit uses gnu make ...
cheers,
hwidjaja
In article < 3845C34E.4FFB923A@usa.net >,
oneself <oneself@usa.net> wrote:
> Hi!
>
> I have just recently started writing makefiles and using make.
> and I want to it on an already existing, very big Java project
> that contains something like 500 files in an elaborate tree structure.
> from the brief but decisive acquaintance I had with make there was
> one thing that became obvious to me, and that is that I had to
actually
> put in every file name in the make file. and,if I was bored enough,
> their dependencies.
>
> my first question is, am I right or wrong. if I'm wrong then how can
> I make make make my whole project with out putting in every
> file name in the makefile.
> if I'm write, are there any tools out there that make this task easier
> to manage.
>
> thanks.
>
>
Sent via Deja.com http://www.deja.com/
Before you buy.
next prev parent reply other threads:[~1999-12-02 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-01 17:01 oneself
1999-12-02 9:10 ` dpace
1999-12-31 22:24 ` dpace
1999-12-02 19:54 ` hwidjaja [this message]
1999-12-31 22:24 ` hwidjaja
1999-12-03 2:31 ` Volker Borchert
1999-12-31 22:24 ` Volker Borchert
1999-12-03 8:25 ` Paul D. Smith
1999-12-31 22:24 ` Paul D. Smith
1999-12-31 22:24 ` oneself
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='827e3b$cku$1@nnrp1.deja.com' \
--to=hwidjaja@my-deja.com \
--cc=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).