From: Jaft <jaft.r@outlook.com>
To: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Adjusting Load Path from C/C++?
Date: Wed, 15 Apr 2020 04:08:08 +0000 (UTC) [thread overview]
Message-ID: <DM6PR19MB246072D8367E2092CDA9D51499DB0@DM6PR19MB2460.namprd19.prod.outlook.com> (raw)
In-Reply-To: 546899605.742163.1586923688566.ref@mail.yahoo.com
Hello.
I'm attempting to use Guile, from C, in a project. I've managed, I believe, to properly hook up the dependencies and can #include but running scm_init_guile() results in the error
Throw without catch before boot:
Throw to key misc-error with args ("primitive-load-path" "Unable to find file ~S in load path" ("ice-9/boot-9") #f)Aborting.
Definitely someone correct me if I'm mistaken but I'm guessing it's occurring because it's not finding the .scm files that typically (I think? Leastwise, where I've always seen them) reside in a "share" directory somewhere on the root path tree?
So this project allows moving libraries into where it's deployed but all other files are containerized in the app's designated directory.
I believe there's a way to set the load path on build of Guile (though, now that I think about it, the project may not share what the eventual app. directory is/will-be during the build process so that may not even be feasible…) but I was wondering if there was a way to set (or add to) the build path from C?
I was thinking something like add-to-load-path but I didn't see a corresponding C function in the documentation.
If I had a way, I figured I could just, then, have the necessary modules moved to the app.'s directory on build, add the current directory to the load path, and then call scm_init_guile().
I dunno if there is a solve but thanks to anyone for any help!
Jonathan
next parent reply other threads:[~2020-04-15 4:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <546899605.742163.1586923688566.ref@mail.yahoo.com>
2020-04-15 4:08 ` Jaft [this message]
2020-04-16 5:25 ` Adjusting Load Path from C/C++? Mike Gran
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM6PR19MB246072D8367E2092CDA9D51499DB0@DM6PR19MB2460.namprd19.prod.outlook.com \
--to=jaft.r@outlook.com \
--cc=guile-user@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).