Doc: Fix target documentation #640

Merged
cmorty merged 1 commit from fix-doc into master 2023-11-17 05:45:47 -06:00
cmorty commented 2023-11-16 04:55:55 -06:00 (Migrated from github.com)
No description provided.
Youw (Migrated from github.com) reviewed 2023-11-16 04:55:55 -06:00
Youw (Migrated from github.com) reviewed 2023-11-16 10:37:00 -06:00
@ -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;
Youw (Migrated from github.com) commented 2023-11-16 10:37:00 -06:00

thanks

thanks
Youw (Migrated from github.com) reviewed 2023-11-16 10:38:30 -06:00
@ -214,7 +214,7 @@ This is done to let the host project's developer decide what is important (what
In 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.
Youw (Migrated from github.com) commented 2023-11-16 10:38:30 -06:00

this statement is deceptive

  1. this is a list of targets as explicitly stated above
  2. The original statement is true: 1, 2
this statement is deceptive 1) this is a list of _targets_ as explicitly stated above 2) The original statement is true: [1](https://github.com/libusb/hidapi/blob/9b507edd8ab66bd8c16cbd9379f6c26ca72d6465/windows/CMakeLists.txt#L44), [2](https://github.com/libusb/hidapi/blob/9b507edd8ab66bd8c16cbd9379f6c26ca72d6465/mac/CMakeLists.txt#L32)
cmorty (Migrated from github.com) reviewed 2023-11-16 10:46:47 -06:00
@ -214,7 +214,7 @@ This is done to let the host project's developer decide what is important (what
In 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.
cmorty (Migrated from github.com) commented 2023-11-16 10:46:46 -06:00

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::hidapi for all targets?

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::hidapi` for all targets?
Youw (Migrated from github.com) reviewed 2023-11-16 11:00:43 -06:00
@ -214,7 +214,7 @@ This is done to let the host project's developer decide what is important (what
In 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.
Youw (Migrated from github.com) commented 2023-11-16 11:00:43 -06:00

not nesessary
per-platform files has per-platform definitions
documentation is in one place
we should be good as is

not nesessary per-platform files has per-platform definitions documentation is in one place we should be good as is
cmorty (Migrated from github.com) reviewed 2023-11-17 01:17:40 -06:00
@ -214,7 +214,7 @@ This is done to let the host project's developer decide what is important (what
In 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.
cmorty (Migrated from github.com) commented 2023-11-17 01:17:40 -06:00

Ok. The advantage of cleaning things up would be that the sentence would be:

`hidapi` [...] an alias of `hidapi::hidapi` 

but probably one shouldn't use those targets anyway. :)

Ok. The advantage of cleaning things up would be that the sentence would be: ``` `hidapi` [...] an alias of `hidapi::hidapi` ``` but probably one shouldn't use those targets anyway. :)
Youw (Migrated from github.com) reviewed 2023-11-17 05:44:37 -06:00
@ -214,7 +214,7 @@ This is done to let the host project's developer decide what is important (what
In 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.
Youw (Migrated from github.com) commented 2023-11-17 05:44:37 -06:00

hidapi [...] an alias of hidapi::hidapi

That would be a strong but technically invalid statement as of right now.

> `hidapi` [...] an alias of `hidapi::hidapi` That would be a strong but technically invalid statement as of right now.
Youw (Migrated from github.com) reviewed 2023-11-17 05:45:40 -06:00
@ -214,7 +214,7 @@ This is done to let the host project's developer decide what is important (what
In 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.
Youw (Migrated from github.com) commented 2023-11-17 05:45:39 -06:00

probably one shouldn't use those targets anyway. :)

That's exactly why that target is added for compatibility cases only.
I'll consider removing it completely for v1.0

> probably one shouldn't use those targets anyway. :) That's exactly why that target is added for compatibility cases only. I'll consider removing it completely for v1.0
Sign in to join this conversation.
No reviewers
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-libusb/hidapi!640
No description provided.