From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: help-gnu-emacs@gnu.org
Subject: Transforming paths in compilation output (containerized builds)
Date: Sat, 07 Dec 2024 21:58:36 +0200 [thread overview]
Message-ID: <35978.8326708198$1733601574@news.gmane.org> (raw)
Hello,
I'm looking how to transform the output in the compilation buffer or
just make Emacs open the correct paths inside builds happen inside
containerized builds.
The output of the programs ran inside these environments relates
to the environment they are build in e.g. container in
/var/tmp/build-root/<name> and output as if /var/tmp/build-root/<name>
is /.
I'm having this situation when building with osc build which sets up a
linux environment generated according to the settings of the repository,
e.g. a Debian system debbuild or openSUSE system with rpmbuild with
the dependencies required to build a package. For context osc is the
commandline client to the Open Build Service also known as openSUSE build service.
The builds can be inside a change root, a container or a vm.
The second example would be builds in Scratchbox2, a cross compiling
environment.
There the paths are also relative to the environment, a Scratchbox2
target or if they don't exist in the target simply relative to the host.
E.g. /usr/include/foo.h -> target
~/project/foo.c -> host
I did some research, I found other modes such as ppcompile which uses
compilation-finish-functions.
For remote environments I know that tramp uses file-name-handler-alist.
Is it possible to register temporary file-name handler for this context
or are there better methods to achieve what I want to do?
Have a great weekend,
Björn
next reply other threads:[~2024-12-07 19:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 19:58 Björn Bidar [this message]
[not found] <87y10rnu37.fsf@>
2024-12-07 20:21 ` Transforming paths in compilation output (containerized builds) Eli Zaretskii
2024-12-07 21:17 ` Björn Bidar
[not found] ` <87plm3nqfr.fsf@>
2024-12-08 5:42 ` Eli Zaretskii
2024-12-08 6:32 ` Yuri Khan
2024-12-08 7:04 ` Eli Zaretskii
2024-12-08 19:45 ` Björn Bidar
[not found] ` <87frmy2c38.fsf@>
2024-12-08 20:44 ` Eli Zaretskii
[not found] <6754a91d.050a0220.355713.95f8SMTPIN_ADDED_BROKEN@mx.google.com>
2024-12-08 6:24 ` Yuri Khan
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='35978.8326708198$1733601574@news.gmane.org' \
--to=bjorn.bidar@thaodan.de \
--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.
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).