From: Ergus <spacibba@aol.com>
To: tomas@tuxteam.de
Cc: help-gnu-emacs@gnu.org
Subject: Re: Out of source compilation
Date: Sun, 1 Sep 2019 18:22:16 +0200 [thread overview]
Message-ID: <20190901162216.t7bzavekajd3mmdq@Ergus> (raw)
In-Reply-To: <20190901082430.GA19628@tuxteam.de>
No, sorry I explained wrong myself ;)
I was asking about using the M-x compile command in general. So use
compilation buffers, recompile, goto-next-error and so on.
When compiling in source it is almost trivial, but when the building
directory is out of sources (like cmake does by default) I don't know if
there is a way to tell to emacs that the compilation directory is
somewhere else.
On Sun, Sep 01, 2019 at 10:24:30AM +0200, tomas@tuxteam.de wrote:
>On Sun, Sep 01, 2019 at 05:57:07AM +0200, Ergus wrote:
>> Hi:
>>
>> Sorry if this is a too dumb question, but I don't find any related
>> reference.
>>
>> What's the recommended method to do out of source compilation?
>
>You are talking about compiling Emacs from source?
>
>> Right now I am doing a cd dir && make. But maybe there is
>> something else, more complete?
>>
>> Maybe a variable in the locals file?? Or a set command?
>
>If my guess above was right, it's easy (this is true of most well
>managed "modern" Autotools projects):
>
> - just make yourself a build directory somewhere (in my case
> it's just a neighbour of the source dir, but that's not
> necessary)
>
> - cd to your build directory
>
> - call configure script from your build directory
>
> - the build machinery gets deployed in your build directory.
>
> - do there make && make install as usual.
>
>Cheers
>-- t
next prev parent reply other threads:[~2019-09-01 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 3:57 Out of source compilation Ergus
2019-09-01 8:24 ` tomas
2019-09-01 12:55 ` VanL
2019-09-01 14:19 ` tomas
2019-09-01 16:22 ` Ergus [this message]
2019-09-01 16:52 ` Óscar Fuentes
2019-09-01 17:12 ` tomas
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=20190901162216.t7bzavekajd3mmdq@Ergus \
--to=spacibba@aol.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.