From: Eric Schulte <email@example.com>
To: Daimrod <firstname.lastname@example.org>
Subject: Re: URGENT Org Babel C/C++
Date: Sat, 31 Mar 2012 11:47:52 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (email@example.com's message of "Thu, 29 Mar 2012 01:01:07 +0200")
[-- Attachment #1: Type: text/plain, Size: 2250 bytes --]
Daimrod <firstname.lastname@example.org> writes:
> Eric Schulte <email@example.com> writes:
>> Applied, Thanks!
>> Daimrod <firstname.lastname@example.org> writes:
>>> I've made a small patch to ob-C.el so it now includes the current
>>> directory to the list of directories to be searched for header files.
>>> Without this, I cannot include a local header file because the
>>> compilation happens in /tmp and thus gcc or g++ doesn't search for
>>> header files in the directory I currently work.
>>> diff --git a/lisp/ob-C.el b/lisp/ob-C.el
>>> index f1525aa..4f33fc4 100644
>>> --- a/lisp/ob-C.el
>>> +++ b/lisp/ob-C.el
>>> @@ -96,15 +96,14 @@ or `org-babel-execute:C++'."
>>> (with-temp-file tmp-src-file (insert full-body))
>>> - (format "%s -o %s %s %s -I \"%s\""
>>> + (format "%s -o %s %s %s"
>>> ((equal org-babel-c-variant 'c) org-babel-C-compiler)
>>> ((equal org-babel-c-variant 'cpp) org-babel-C++-compiler))
>>> (org-babel-process-file-name tmp-bin-file)
>>> (mapconcat 'identity
>>> (if (listp flags) flags (list flags)) " ")
>>> - (org-babel-process-file-name tmp-src-file)
>>> - (file-name-directory (expand-file-name (buffer-file-name)))) ""))))
>>> + (org-babel-process-file-name tmp-src-file)) ""))))
>>> ((lambda (results)
>>> (if (member "vector" (cdr (assoc :result-params params)))
> Hum, I'm quite embarrassed, this doesn't work when the block is executed
> during an export. I didn't track it down yet, but (buffer-file-name)
> returns nil during the export probably because the buffer changes.
I've reverted this commit, I should have been more cautious in its
application. I've reverted this commit in both the hotfix-7.8.06 branch
and the master branch.
> A workaround would be to use the :flags header argument though it's a
> bit tedious because it doesn't seem possible to eval elisp during the
> #+BEGIN_SRC cpp :flags -I (file-name-directory (buffer-file-name))
I don't believe the above statement is true, for example the following
code block evaluates its header argument on export.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: example.org --]
[-- Type: text/x-org, Size: 156 bytes --]
Example of code eval during export.
#+headers: :exports results
#+begin_src emacs-lisp :var this=(file-name-directory (buffer-file-name))
[-- Attachment #3: Type: text/plain, Size: 54 bytes --]
prev parent reply other threads:[~2012-03-31 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 18:12 Org Babel C/C++ Daimrod
2012-03-26 11:39 ` Eric Schulte
2012-03-28 23:01 ` Daimrod
2012-03-29 1:34 ` Michael Hannon
2012-03-30 11:17 ` Daimrod
2012-03-31 15:47 ` Eric Schulte [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).