Doc: Fix target documentation #640
No reviewers
Labels
No labels
3rdparty
Android
API
Author does not respond
bsd
bug
build system/CI
ci-virtual-device
CMake
Contributions Welcome
Core
dependencies
device-specific
documentation
don't_merge
duplicate
enhancement
Example
Haiku
hidraw
hotplug
info required
invalid
libusb
macOS
Misc
Not an issue
question
Release
Test
Test GUI
Windows
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-libusb/hidapi!640
Loading…
Reference in a new issue
No description provided.
Delete branch "fix-doc"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -216,3 +216,3 @@Available CMake targets after `add_subdirectory(hidapi)` _are the same as in case of [standalone build](#standalone-package-build)_, and a few additional ones:- `hidapi_include` - the interface library; `hidapi::hidapi` is an alias of it;- `hidapi_include` - the interface library; `hidapi::include` is an alias of it;- `hidapi_winapi` - library target on Windows; `hidapi::winapi` is an alias of it;thanks
@ -214,7 +214,7 @@ This is done to let the host project's developer decide what is important (whatIn a _subdirectory build_, even if not set, those variables remain unchanged, so a host project's developer has a full control over the HIDAPI build configuration.this statement is deceptive
@ -214,7 +214,7 @@ This is done to let the host project's developer decide what is important (whatIn a _subdirectory build_, even if not set, those variables remain unchanged, so a host project's developer has a full control over the HIDAPI build configuration.You are right, I actually missed that. Wouldn't it make sense to remove those two and declare them at the same place as
hidapi::hidapifor all targets?@ -214,7 +214,7 @@ This is done to let the host project's developer decide what is important (whatIn a _subdirectory build_, even if not set, those variables remain unchanged, so a host project's developer has a full control over the HIDAPI build configuration.not nesessary
per-platform files has per-platform definitions
documentation is in one place
we should be good as is
@ -214,7 +214,7 @@ This is done to let the host project's developer decide what is important (whatIn a _subdirectory build_, even if not set, those variables remain unchanged, so a host project's developer has a full control over the HIDAPI build configuration.Ok. The advantage of cleaning things up would be that the sentence would be:
but probably one shouldn't use those targets anyway. :)
@ -214,7 +214,7 @@ This is done to let the host project's developer decide what is important (whatIn a _subdirectory build_, even if not set, those variables remain unchanged, so a host project's developer has a full control over the HIDAPI build configuration.That would be a strong but technically invalid statement as of right now.
@ -214,7 +214,7 @@ This is done to let the host project's developer decide what is important (whatIn a _subdirectory build_, even if not set, those variables remain unchanged, so a host project's developer has a full control over the HIDAPI build configuration.That's exactly why that target is added for compatibility cases only.
I'll consider removing it completely for v1.0