abrenneke
commented
1 year ago @vibl try node 20.4, 20.6.1 doesn't seem to have prebuilt binaries yet.
Closed vibl closed 1 year ago
abrenneke
commented
1 year ago @vibl try node 20.4, 20.6.1 doesn't seem to have prebuilt binaries yet.
vibl
commented
1 year ago Using Node 20.4, it does build but with some errors:
yarn dev
Bundling to bin/executor-bundle.js...
Compiling to native binary for linux...
> pkg@5.8.1
> Fetching base Node.js binaries to PKG_CACHE_PATH
fetched-v18.5.0-linux-x64 [====================] 100%
> Warning Cannot resolve 'config.extends'
/home/vianney/dev/js/forks/rivet/packages/app-executor/bin/executor-bundle.js
Dynamic require may fail at run time, because the requested file
is unknown at compilation time and not included into executable.
Use a string literal as an argument for 'require', or leave it
as is and specify the resolved file name in 'scripts' option.
> Warning Cannot resolve 'path2'
/home/vianney/dev/js/forks/rivet/packages/app-executor/bin/executor-bundle.js
Dynamic require may fail at run time, because the requested file
is unknown at compilation time and not included into executable.
Use a string literal as an argument for 'require', or leave it
as is and specify the resolved file name in 'scripts' option.
Copied dist/rivet-app-executor to dist/app-executor-x86_64-unknown-linux-gnu for tauri sidecar
Running BeforeDevCommand (`yarn start`)
VITE v4.4.7 ready in 494 ms
➜ Local: http://localhost:5173/
➜ Network: use --host to expose
Info Watching /home/vianney/dev/js/forks/rivet/packages/app/src-tauri for changes...
Updating crates.io index
Updating git repository `https://github.com/tauri-apps/plugins-workspace`
Updating git repository `https://github.com/tauri-apps/plugins-workspace`
Downloaded gdkwayland-sys v0.15.3
Downloaded string_cache_codegen v0.5.2
Downloaded alloc-stdlib v0.2.2
[...]
Compiling regex-automata v0.3.6
Compiling json-patch v1.0.0
Compiling tauri-utils v1.4.0
The following warnings were emitted during compilation:
warning: `"pkg-config" "--libs" "--cflags" "libsoup-2.4" "libsoup-2.4 >= 2.62"` did not exit successfully: exit status: 1
error: failed to run custom build command for `soup2-sys v0.2.0`
Caused by:
process didn't exit successfully: `/home/vianney/dev/js/forks/rivet/packages/app/src-tauri/target/debug/build/soup2-sys-3b58d5373361346e/build-script-build` (exit status: 1)
--- stdout
cargo:rerun-if-env-changed=LIBSOUP_2.4_NO_PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
cargo:warning=`"pkg-config" "--libs" "--cflags" "libsoup-2.4" "libsoup-2.4 >= 2.62"` did not exit successfully: exit status: 1
error: could not find system library 'libsoup-2.4' required by the 'soup2-sys' crate
--- stderr
Package libsoup-2.4 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libsoup-2.4.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libsoup-2.4', required by 'virtual:world', not found
Package 'libsoup-2.4', required by 'virtual:world', not found
warning: build failed, waiting for other jobs to finish...
The following warnings were emitted during compilation:
warning: `"pkg-config" "--libs" "--cflags" "javascriptcoregtk-4.0" "javascriptcoregtk-4.0 >= 2.24"` did not exit successfully: exit status: 1
error: failed to run custom build command for `javascriptcore-rs-sys v0.4.0`
Caused by:
process didn't exit successfully: `/home/vianney/dev/js/forks/rivet/packages/app/src-tauri/target/debug/build/javascriptcore-rs-sys-e38355fbdda0f806/build-script-build` (exit status: 1)
--- stdout
cargo:rerun-if-env-changed=JAVASCRIPTCOREGTK_4.0_NO_PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
cargo:warning=`"pkg-config" "--libs" "--cflags" "javascriptcoregtk-4.0" "javascriptcoregtk-4.0 >= 2.24"` did not exit successfully: exit status: 1
error: could not find system library 'javascriptcoregtk-4.0' required by the 'javascriptcore-rs-sys' crate
--- stderr
Package javascriptcoregtk-4.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `javascriptcoregtk-4.0.pc'
to the PKG_CONFIG_PATH environment variable
Package 'javascriptcoregtk-4.0', required by 'virtual:world', not found
Package 'javascriptcoregtk-4.0', required by 'virtual:world', not foundI created a separate issue for this, for better future reference: https://github.com/Ironclad/rivet/issues/146
Closing this one.
What happened?
Here are the command I use to try build Rivet, and the resulting errors:
The
yarn devcommand fails:If I run it again, it fails with another error message:
What was the expected functionality?
Build
Describe your environment
Kubuntu 23.04 Node.js v20.6.1
Relevant log output
The file logs:
The other log files are the same.
Relevant screenshots
No response
Code of Conduct