From: pjb@informatimago.com (Pascal J. Bourguignon)
To: help-gnu-emacs@gnu.org
Subject: Re: is there a good way to do emacs project management ?
Date: Wed, 15 Apr 2009 23:48:13 +0200 [thread overview]
Message-ID: <87myahfv1e.fsf@galatea.local> (raw)
In-Reply-To: 49e63013$0$90267$14726298@news.sunsite.dk
"Colin S. Miller" <no-spam-thank-you@csmiller.demon.co.uk> writes:
> Pascal J. Bourguignon wrote:
>> halida <linjunhalida@gmail.com> writes:
>>
>>> I use emacs to do some coding, and text editing,
>>> When I create a new coding project, I simply create a new folder,
>>> and add source code into it.
>>> The problem is, with multi-forders, it is hard to change back to the
>>> top,
>>> and run the makefile.
>> Type: M-x compile RET C-e SPC -C
>> /path/to/the/directory/where/is/Makefile RET
>> then to recompile: M-x recompile RET
>> from any directory...
>>
>
> I use
>
> cd /path/to/make/file && make -f Makefile
>
> as my build command.
Indeed, this way is more portable, since it works even with non GNU make.
But:
make -C /path/to/dir/where/makefile/is
is conceptually simplier, when you have GNU make.
--
__Pascal Bourguignon__
next prev parent reply other threads:[~2009-04-15 21:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 0:34 is there a good way to do emacs project management ? halida
2009-04-15 3:29 ` Kiwon Um
2009-04-15 7:32 ` Pascal J. Bourguignon
2009-04-15 8:11 ` Peter Dyballa
2009-04-15 8:26 ` Alberto Luaces
2009-04-15 8:42 ` Alberto Luaces
[not found] ` <mailman.5369.1239783125.31690.help-gnu-emacs@gnu.org>
2009-04-15 8:46 ` Pascal J. Bourguignon
2009-04-15 11:13 ` Richard Riley
[not found] ` <mailman.5370.1239783629.31690.help-gnu-emacs@gnu.org>
2009-04-15 8:48 ` Pascal J. Bourguignon
2009-04-15 19:05 ` Colin S. Miller
2009-04-15 21:04 ` Richard Riley
2009-04-15 21:48 ` Pascal J. Bourguignon [this message]
2009-04-15 13:29 ` Nikolaj Schumacher
-- strict thread matches above, loose matches on Subject: below --
2009-04-15 12:51 grischka
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87myahfv1e.fsf@galatea.local \
--to=pjb@informatimago.com \
--cc=help-gnu-emacs@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).