665e13c85e
Since a while, the semantic of BR2_PREFER_STATIC_LIB has been changed from "prefer static libraries when possible" to "use only static libraries". The former semantic didn't make much sense, since the user had absolutely no control/idea of which package would use static libraries, and which packages would not. Therefore, for quite some time, we have been starting to enforce that BR2_PREFER_STATIC_LIB should really build everything with static libraries. As a consequence, this patch renames BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS, and adjust the Config.in option accordingly. This also helps preparing the addition of other options to select shared, shared+static or just static. Note that we have verified that this commit can be reproduced by simply doing a global rename of BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS plus adding BR2_PREFER_STATIC_LIB to Config.in.legacy. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
22 lines
878 B
Plaintext
22 lines
878 B
Plaintext
config BR2_PACKAGE_PHIDGETWEBSERVICE
|
|
bool "phidgetwebservice"
|
|
depends on BR2_TOOLCHAIN_HAS_THREADS # libusb, libphidget
|
|
depends on !BR2_STATIC_LIBS # libphidget
|
|
select BR2_PACKAGE_LIBPHIDGET
|
|
help
|
|
phidgetwebservice (the Phidget WebService) provides an HTTP
|
|
front-end to the libphidget device control API. This provides
|
|
an alternative to the libphidget C linkage interface for
|
|
controlling locally attached Phidgets USB devices and it also
|
|
allows you to control Phidget USB devices remotely when the host
|
|
running the phidgetwebservice has an exposed network interface.
|
|
|
|
The phidgetwebservice client program uses the libphidget HTTP
|
|
functions to send commands to the phidgetwebservice.
|
|
|
|
http://phidgets.com/
|
|
|
|
comment "phidgetwebservice needs a toolchain w/ threads, dynamic library"
|
|
depends on !BR2_TOOLCHAIN_HAS_THREADS
|
|
depends on BR2_STATIC_LIBS
|