[EMAIL PROTECTED] wrote: > Hi Florian, > > this does not answer my question, I asked about PKG_BUILD_DEPENDS, not > DEPENDS! > Defining the dependencies between packages is not the problem. > > My problem is an application, that can manage two different chips via their > drivers. > To build the application I need the sources of the driver unpacked/installed > before compiling, > to include the interface definition of the driver. > > For a single driver it is no problem to define > PKG_BUILD_DEPENDS:=driver_x > > But if I can select a second driver and define > PKG_BUILD_DEPENDS:=driver_x driver_y > both drivers gets unpacked and built (which is not what I want, but would be > a workaround!). > You can try the same with ppp and libpcap (which is only listed as > build-dependency!) > > If I do the definition like described in my first mail, no build-dependency > is defined, > as the config-options are not known during package-scan (which is correct in > general). > > Maybe you have an idea, how to restrict the build-dependencies to the > selected packages. > Currently updating to kamikaze/trunk is not an option, even if it might be > fixed there.
Currently those dynamic dependencies are not possible, because dependencies are calculated at package scan time, before menuconfig is run. I will add an extension for config option based dependencies soon, e.g. DEPENDS:= +CONFIG_FOO:bar - Felix _______________________________________________ openwrt-devel mailing list [email protected] http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
