Re: [PATCH] ob-C.el compile-only header argument, was Re: How to use mpirun with C or C++ Org-babel?

2024-01-05 Thread Ihor Radchenko
Leo Butler writes: >> #+begin_src C :compile-only t :file foo :includes "stdio.h" >> printf("This is test"); >> #+end_src > > It should be "yes" not "t". I tested with :compile-only yes, but it did not change the observed issue. >> , executing should yield file link, even though it is not

Re: [PATCH] ob-C.el compile-only header argument, was Re: How to use mpirun with C or C++ Org-babel?

2024-01-04 Thread Leo Butler
On Fri, Dec 22 2023, Ihor Radchenko wrote: > Leo Butler writes: > >>> What will happen if we have something like :results value or :results >>> output instead of :results file link? >> >> Originally, I felt that only ":results file" makes sense. I have adopted >> your suggestion, though, and

Re: [PATCH] ob-C.el compile-only header argument, was Re: How to use mpirun with C or C++ Org-babel?

2023-12-22 Thread Ihor Radchenko
Leo Butler writes: >> What will happen if we have something like :results value or :results >> output instead of :results file link? > > Originally, I felt that only ":results file" makes sense. I have adopted > your suggestion, though, and added test cases so that the compiler > stderr output

[PATCH] ob-C.el compile-only header argument, was Re: How to use mpirun with C or C++ Org-babel?

2023-12-19 Thread Leo Butler
On Thu, Dec 14 2023, Ihor Radchenko wrote: > Leo Butler writes: > >> From 7d8e406bc4a92e2e2eab772b2671dcd72ca8c202 Mon Sep 17 00:00:00 2001 >> From: Leo Butler >> Date: Tue, 12 Dec 2023 12:32:41 -0600 >> Subject: [PATCH] lisp/ob-C.el: add :compile-only header to compile to a named >> target >