From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: kawa <kawa@sourceware.org>
Subject: Specifying parent load path
Date: Tue, 3 Oct 2023 09:23:25 +0200 [thread overview]
Message-ID: <CAMFYt2Ybj+wTgkT8r2B9wSMHmKer4K3X3qOiZHUuBJ-d9V6G0w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
I recently decided to clean up the GRASP repository a bit. Previously, all
the modules were piled in a single 'src/' directory, but I'm splitting it
into a few different directories.
Among those files, there were some tests included. They were essentially
stand-alone programs, but I thought it would be nice to move them all into
'src/tests/' directory.
The only problem is that once I do that, they no longer see their
dependency modules.
I tried adding
-Dkawa.include.path="|:`pwd`/src"
and
-Dkawa.include.path="|:.."
to the test runner, but none of it helped.
Here's the implementation of the test runner:
https://github.com/panicz/grasp/blob/main/run-tests
Is it possible to hint Kawa to look for modules in the file's parent
directory?
reply other threads:[~2023-10-03 8:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMFYt2Ybj+wTgkT8r2B9wSMHmKer4K3X3qOiZHUuBJ-d9V6G0w@mail.gmail.com \
--to=godek.maciek@gmail.com \
--cc=kawa@sourceware.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).