Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
scord
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
eu
ADMIRE
scord
Commits
a4b3b4d3
Verified
Commit
a4b3b4d3
authored
1 year ago
by
Alberto Miranda
Browse files
Options
Downloads
Patches
Plain Diff
CMake: Update `tl::expected` to v1.1.0
Fixes
#125
parent
859fd00a
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!89
"Resolve build fails with outdated `tl::expected`"
Checking pipeline status
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CMakeLists.txt
+1
-2
1 addition, 2 deletions
CMakeLists.txt
with
1 addition
and
2 deletions
CMakeLists.txt
+
1
−
2
View file @
a4b3b4d3
...
...
@@ -246,14 +246,13 @@ FetchContent_MakeAvailable(genopts)
### expected: required for using tl::expected in the C++ library implementation
### until std::expected makes it to C++
message
(
STATUS
"[
${
PROJECT_NAME
}
] Downloading and building tl::expected"
)
set
(
EXPECTED_BUILD_PACKAGE OFF
)
set
(
EXPECTED_BUILD_TESTS OFF
)
FetchContent_Declare
(
expected
GIT_REPOSITORY https://github.com/TartanLlama/expected
GIT_TAG
3e304a4bdd00feef8d41f5b388c37bd9d6108025
# latest
GIT_TAG
292eff8bd8ee230a7df1d6a1c00c4ea0eb2f0362
# v1.1.0
GIT_SHALLOW ON
GIT_PROGRESS ON
)
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment