From: Max Nikulin <email@example.com>
To: firstname.lastname@example.org, email@example.com
Subject: Re: Have export treat file: paths in INCLUDED file relative to the INCLUDING file's dir
Date: Thu, 2 Mar 2023 19:14:02 +0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 01/03/2023 04:42, gnuric wrote:
>> h-0.h:#include "include-1/h-1.h"
>> h-0.h:extern int h0;
>> include-1/h-1.h:#include "include-2/h-2.h"
> You have two #include directives in your example, which are
> processed recursively according to the preprocessor rules. What I
> had in mind was one #include preprocessor directive (similar to
> one #+INCLUDE: 'directive' in Org) and a non-preprocessor
> directive (`file:' in Org).
My idea was that second include should simulate a link relative to the
include-1/h-1.h file. I have no idea which feature of cpp may be used to
distinguish behavior of include and link in respect to relative paths.
My expectation is that relative paths are resolved in respect to the
file where they reside. I admit that in some cases included file may be
a kind of template, so it may add e.g. a logo specific to each project.
However, perhaps, I would prefer to define a macro.
Notice that CPP has another feature: include path, so while searching
for a file directories from a list tried till file is found:
cpp -I /usr/include/lib1 -I /usr/include/lib2
Org does not have such concept.
prev parent reply other threads:[~2023-03-02 12:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 1:52 Have export treat file: paths in INCLUDED file relative to the INCLUDING file's dir gnuric
2023-02-28 10:34 ` [FR] Allow to #+include files verbatim without any processing (was: Have export treat file: paths in INCLUDED file relative to the INCLUDING file's dir) Ihor Radchenko
2023-02-28 15:12 ` Timothy
2023-02-28 21:34 ` gnuric
2023-03-30 18:17 ` gnuric
2023-04-02 10:24 ` Ihor Radchenko
2023-04-02 21:32 ` gnuric
2023-04-03 9:18 ` Ihor Radchenko
2023-04-04 1:04 ` Samuel Wales
2023-04-04 8:57 ` Ihor Radchenko
2023-04-05 0:16 ` Samuel Wales
2023-04-04 8:07 ` gnuric
2023-04-04 8:26 ` Ihor Radchenko
2023-03-01 9:58 ` Ihor Radchenko
2023-02-28 15:03 ` Have export treat file: paths in INCLUDED file relative to the INCLUDING file's dir Max Nikulin
2023-02-28 21:42 ` gnuric
2023-03-02 12:14 ` Max Nikulin [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).