From: Francis Belliveau <f.belliveau@comcast.net>
To: "B.V. Raghav" <bvraghav@iitk.ac.in>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Compilation in C and ADA
Date: Tue, 19 Jul 2016 22:50:12 -0400 [thread overview]
Message-ID: <4781A7A0-F110-47CC-A19D-0C9F1619FD23@comcast.net> (raw)
In-Reply-To: <87shv5sf78.fsf@ram.bvr.dp.lan>
Although previous response described how to work around the problem, I believe that bit of clarity expansion is needed here with regard to what is actually happening.
I am no emacs expert, but from the evidence it seems clear to me that the emacs "compile" default is to make an entire application, not just compile a single file or the current buffer.
It has been a long time since I used Ada, so I cannot speak to how Ada applications are built these days, but I expect "make" can be used to do it.
However, both C and C++ developers commonly use make, or one of its many flavors, to describe the dependancies between application sources and how to build the applications. Normally when you compile a C file you get an object file, not an executable program. All the objects for the project, just the one in this case, then need to be linked with the appropriate set of libraries in order to create the program executable. Again this is just a simple system library in the case of a "hello" application.
Since I do not use the menus either, I do not know what the various choices are.
However, this sounds to me like a "Human Factors" ambiguity problem.
Either the default for "compile" should be to execute "gcc" rather than "make", or the menu command "compile" should be changed to something like "make app".
next prev parent reply other threads:[~2016-07-20 2:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 11:11 Compilation in C and ADA Edward Zacharek
2016-07-19 17:36 ` B.V. Raghav
2016-07-20 2:50 ` Francis Belliveau [this message]
2016-07-20 4:30 ` B.V. Raghav
2016-07-23 14:22 ` Francis Belliveau
2016-07-23 17:52 ` Dale Snell
[not found] ` <mailman.1937.1469296394.26859.help-gnu-emacs@gnu.org>
2016-07-23 20:08 ` Emanuel Berg
[not found] ` <mailman.1922.1469283823.26859.help-gnu-emacs@gnu.org>
2016-07-23 15:05 ` Emanuel Berg
2016-07-24 4:20 ` Francis Belliveau
[not found] ` <mailman.1955.1469334108.26859.help-gnu-emacs@gnu.org>
2016-07-24 12:48 ` Emanuel Berg
2016-07-23 16:23 ` Kendall Shaw
[not found] <mailman.1680.1468936015.26859.help-gnu-emacs@gnu.org>
2016-07-20 3:43 ` Rusi
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=4781A7A0-F110-47CC-A19D-0C9F1619FD23@comcast.net \
--to=f.belliveau@comcast.net \
--cc=bvraghav@iitk.ac.in \
--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.
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.