Closed rudism closed 1 year ago
Here's what happens when I manually run the command that it reports failed:
~/src/Junction main
❯ /home/rudism/src/Junction/src/../troll/gjspack/bin/gjspack --appid=re.sonny.Junction --prefix /re/sonny/Junction --project-root /home/rudism/src/Junction --resource-root /home/rudism/src/Junction/src --blueprint-compiler /usr/bin/blueprint-compiler --no-executable ../src/main.js --potfiles ../src/../po/POTFILES src
(gjspack:8112): Gjs-WARNING **: 13:05:50.833: JS ERROR: Gio.IOErrorEnum: Error opening file /home/rudism/src/src/main.js: No such file or directory
processSourceFile@resource:///gjspack/src/gjspack.js:135:36
build@resource:///gjspack/src/gjspack.js:365:40
@resource:///gjspack/src/cli.js:247:39
That path it's trying to open /home/rudism/src/src/main.js
is definitely not right... Looks like it's missing a directory in there, I think it should be /home/rudism/src/Junction/src/main.js
instead? I'm completely unfamiliar with meson/ninja so I'm not sure where to start looking.
When running ninja -C build install
, it first does cd build/
and then, from that directory, runs the gjspack command in question.
Here's what happens when I manually run the command that it reports failed:
So, you must run this from inside the src/Junction/build/ directory -- not from src/Junction/.
Thanks for the hint... Trying that does not seem to produce any output, but the command is exiting with non-zero, so I'm still not sure what's up:
~/src/Junction/build main
❯ /home/rudism/src/Junction/src/../troll/gjspack/bin/gjspack --appid=re.sonny.Junction --prefix /re/sonny/Junction --project-root /home/rudism/src/Junction --resource-root /home/rudism/src/Junction/src --blueprint-compiler /usr/bin/blueprint-compiler --no-executable ../src/main.js --potfiles ../src/../po/POTFILES src
~/src/Junction/build main
❯ echo $?
1
The reason you're not getting an error message is probably an outdated blueprint-compiler
or troll
But even then you'll need libadwaita 1.4 (not released)
Do yourself a favor and use the Flatpak :)
This is what I get with your steps to reproduce:
sonny@porygon ~/t/Junction (main)> ninja -C build install
ninja: Entering directory `build'
[29/30] Generating src/gjspack with a custom command
FAILED: src/re.sonny.Junction.src.gresource
/home/sonny/tmp/Junction/src/../troll/gjspack/bin/gjspack --appid=re.sonny.Junction --prefix /re/sonny/Junction --project-root /home/sonny/tmp/Junction --resource-root /home/sonny/tmp/Junction/src --blueprint-compiler /home/sonny/.local/bin/blueprint-compiler --no-executable ../src/main.js --potfiles ../src/../po/POTFILES src
error: Namespace Adw does not contain a type called Breakpoint
at /home/sonny/tmp/Junction/src/window.blp line 10 column 7:
10 | Adw.Breakpoint {
| ^
hint: Did you check your spelling?
hint: Are your dependencies up to date?
error: Namespace Adw does not contain a type called Breakpoint
at /home/sonny/tmp/Junction/src/window.blp line 19 column 7:
19 | Adw.Breakpoint {
| ^
hint: Did you check your spelling?
hint: Are your dependencies up to date?
ninja: build stopped: subcommand failed.
Well, it does look like troll was downloaded by running git submodule update (and the report includes a description of the commit that got checked out as a result).
I personally think it's a bit odd and perhaps a bug in the gjspack command if it exits nonzero without an error message, regardless of mismatched versions (unless a newer gjspack command actually has better logging) but I know nothing about either one, just about meson's command scheduling. :D
unless a newer gjspack command actually has better logging
Yes, I remember fixing that issue.
Excellent, then I guess this problem is solved by syncing the subproject in c54a749720a1adb1f5dc52899c6ec9e62c556d9a and @rudism should try to git pull
today's changes and build the project again.
I'm trying to build this for a local user install, but running into an error at the
ninja
step. Here's a transcript of the build process with the error at the end. Am I doing something incorrectly, or is it a version/dependency problem, or something else?