From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Problem compiling C++ in Org-mode
Date: Fri, 18 Nov 2011 23:57:05 +0100 [thread overview]
Message-ID: <80k46x82f2.fsf@somewhere.org> (raw)
In-Reply-To: 1321646363.68187.YahooMailNeo@web161909.mail.bf1.yahoo.com
Hi Michael,
Michael Hannon wrote:
> Just for the record, adding the following to my .emacs file seems to solve
> the problem I was having, where the C++ compiler was compiling a source
> block (written to a temporary file in /tmp/...) and was unable to find an
> include file in the current working directory:
>
> (setq org-babel-C++-compiler
> (concat "g++ -std=c++0x "
> "-I"
> (expand-file-name ".")
> )
> )
Your previous version contained "-I~/...". I don't know why you changed it,
but this could eventually enlighten you:
┏━━━━[ from Cygwin's ML]
┃ "If a word begins with an unquoted tilde character (`~'), all of the
┃ characters up to the first unquoted slash (or all characters, if there
┃ is no unquoted slash) are considered a TILDE-PREFIX."
┃
┃ Note "word begins". I've been bitten by this in a makefile:
┃
┃ OPENSSL_DIR := ~/lib/openssl
┃ CPPFLAGS := -I$(OPENSSL_DIR)
┃
┃ The gcc command line then contained -I~/lib/openssl, and the ~ was not
┃ expanded by the shell. ${HOME}/lib/openssl would have worked.
┗━━━━
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2011-11-18 22:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 4:56 Problem compiling C++ in Org-mode Michael Hannon
2011-11-18 7:38 ` Olaf Meeuwissen
2011-11-18 8:39 ` Michael Hannon
2011-11-18 9:32 ` Olaf Meeuwissen
2011-11-18 19:59 ` Michael Hannon
2011-11-18 20:16 ` Eric Schulte
2011-11-18 22:57 ` Sebastien Vauban [this message]
2011-11-19 5:13 ` Michael Hannon
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80k46x82f2.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).