why does the CMakeList check to ensure you provide a custom HTTPClient callback when building as a static library?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cmake, cpp
- Domain
- build-system
Research direction
Inspect the CMakeLists configuration and locate the check for a custom HTTPClient callback when building the static library. Trace the related C++ SDK build and callback entry points to establish why the requirement exists; the issue is resolved when that rationale is clearly answered or documented.
Written by the indexing model from the issue text.
Description
I assume there was some issue that caused this check to be added? I'm curious. I would have thought it would work just fine 🤔
- Dominant language
- C++
- Stars
- 34
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Countly/countly-sdk-cpp
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Countly/countly-sdk-cpp#103 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Countly/countly-sdk-cpp#100 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Countly/countly-sdk-cpp#35 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Countly/countly-sdk-cpp#34 ·
-
No namespaceOpen
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Countly/countly-sdk-cpp#33 · 1 reaction ·
All issues in Countly/countly-sdk-cpp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
enhancement question
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DarkStarSystems/pcons#224 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
LizardByte/Sunshine#5953 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
(S1 - Need confirmation)
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
CleverRaven/Cataclysm-DDA#89133 ·
Maintainers usually reply within 1 day