1

While adding custom packages, package A is using Makefile variable that needs to be updated (or not) by other package B, however package B is not mandatory for compiling package A. In other words, if configuration selects package B in that case shared Makefile variable be populated and values can be seen by other packages.

Package A

$(variable1)

package B

variable1 := "-Dxyz -Dabc"

I tried with setting empty "variable1" in rules.mk which is not working. Appreciate if anyone can point me existing examples for same.

mqm
  • 11
  • 1
  • Are Package A and Package B part of the same build? – John Bollinger Dec 19 '19 at 13:00
  • @JohnBollinger both packages are the part of same build environment, but i want to build single package A, without building package B. – mqm Dec 20 '19 at 06:40
  • I have been thinking about this, but I just don't have enough knowledge about openwrt's configuration and build framework to answer the question in its present form. The answer is likely to hinge on details of how that works, and of the way it sets up makefiles. Generally speaking, one makefile has no visibility on variables set in other makefiles, but there are ways to work around that. – John Bollinger Dec 20 '19 at 13:06
  • okay. Thanks @JohnBollinger for your inputs. – mqm Dec 23 '19 at 08:47

0 Answers0