-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jow,
With the bool depends option I meant the option itself only to be
displayed if mylib was selected to be built. That indeed created a
recursive dependency.
After some trial-and-error I finally was able to realize the desired
configuration by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looking again at your Kconfig snippet, the depends do not make sense to
me. The bool option which ultimatively is supposed to select mylib
depends itself at mylib. This looks like a recursive dependency to me
and it does not surprise me that it does no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Strange! If I use
DEPENDS:=mylib
instead of
DEPENDS:=MYPACKAGE_USES_LIBRARY:mylib
the opkg dependency works, even without PKG_BUILD_DEPENDS (as Jo-Philipp
mentioned).
Is that a bug or is there another way to realize a configurable dependency?
C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jo-Philipp,
thanks for the reply. Unfortunately that does not work either. The
result is the same as with omitting the + sign.
The package gets built but the dependency is not passed on to opkg
therefore still installing the package without
the n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Use "DEPENDS:=+CONFIG_MYPACKAGE_USES_LIBRARY:mylib" (the plus in front).
That will also make the PKG_BUILD_DEPENDS unnecessary.
Adding a plus in front of a dependency spec means your package selects
the dependant package and it is also propagated
Hello,
I have a problem defining a library dependency in the Makefile of a project.
- First of all I defined a Config.in file like so:
config MYPACKAGE_USES_LIBRARY
bool "Use library"
depends PACKAGE_mypackage && PACKAGE_mylib
default n
help
bla...
- included it in the Mak
