-
-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot build task from release tarball task-3.0.0.tar.gz #3294
Comments
It looks like the fix to this is to just edit the |
I suspect #3209 is the long-term fix here, by the way. |
After following @djmitche instructions (removing line 7 of file task-3.0.0/Cargo.toml) Although this is not a solution to the problem, it is the first instance of instructions for building from source which have worked for me. Hopefully it helps someone. |
What error did you get without creating
|
I've confirmed that the manual step in @Theblackcat98 if you can reproduce the requirement to create the build directory, please open a new issue. |
$:/tmp> tar -xf task-3.0.0.tar.gz
$:/tmp> cmake -S task-3.0.0 -B build
-- Configuring C++17
-- System: Linux
-- Looking for libshared
-- Found libshared
-- Looking for SHA1 references
-- Looking for libuuid
-- Found libuuid
-- Configuring cmake.h
-- Rust Target: x86_64-unknown-linux-gnu
-- Using Corrosion as a subdirectory
error: failed to load manifest for workspace member
/tmp/task-3.0.0/taskchampion/integration-tests
Caused by:
failed to read
/tmp/task-3.0.0/taskchampion/integration-tests/Cargo.toml
Caused by:
No such file or directory (os error 2)
CMake Error at /tmp/build/_deps/corrosion-src/cmake/CorrosionGenerator.cmake:24 (execute_process):
execute_process failed command indexes:
Call Stack (most recent call first):
/tmp/build/_deps/corrosion-src/cmake/CorrosionGenerator.cmake:217 (_cargo_metadata)
/tmp/build/_deps/corrosion-src/cmake/Corrosion.cmake:1098 (_generator_add_cargo_targets)
src/tc/CMakeLists.txt:11 (corrosion_import_crate)
-- Configuring incomplete, errors occurred!
$:/tmp>
The text was updated successfully, but these errors were encountered: