Issue tracker is ONLY used for reporting bugs with technical details. "It doesn't work" or new features should be discussed with our customer support. Please use bug report function in Bridge or contact bridge@protonmail.ch.
Expected Behavior
I build the linux gui version and get a working program without issue. 2.3.0 did that.
Current Behavior
Fails because vcpkg is missing, wrong, etc
Snippet of output
./build.sh: line 61: dev: command not found
git submodule update --init --recursive /home/jcaldwel/Downloads/proton-bridge-3.0.21/internal/../extern/vcpkg
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
check_exit 'Failed to initialize vcpkg as a submodule.'
'[' 128 -ne 0 ']'
echo 'Process failed: Failed to initialize vcpkg as a submodule.'
Process failed: Failed to initialize vcpkg as a submodule.
rm -r ./cmake-build-release
Possible Solution
Maybe build it on a current distributions before deploying it for each distribution and ensure it works on the major ones?
Steps to Reproduce
1) See the notice about updating
2) Crawl around the obtuse websites for the version listed in the update notice for the source package of that version. When you find it then
3) Try and build it.
Version Information
3.0.32 source file from that is packaged and stored on this git
Issue tracker is ONLY used for reporting bugs with technical details. "It doesn't work" or new features should be discussed with our customer support. Please use bug report function in Bridge or contact bridge@protonmail.ch.
Expected Behavior
I build the linux gui version and get a working program without issue. 2.3.0 did that.
Current Behavior
Fails because vcpkg is missing, wrong, etc Snippet of output
./build.sh: line 61: dev: command not found
Possible Solution
Maybe build it on a current distributions before deploying it for each distribution and ensure it works on the major ones?
Steps to Reproduce
1) See the notice about updating 2) Crawl around the obtuse websites for the version listed in the update notice for the source package of that version. When you find it then 3) Try and build it.
Version Information
3.0.32 source file from that is packaged and stored on this git
Context (Environment)
I use it with a local mail client.
Detailed Description
Fix the source build.
Possible Implementation