Commit ce184a81 authored by Alessandro Rubini's avatar Alessandro Rubini Committed by Adam Wujek

config: force ppsi reconfiguration by default

Without this, after the first build of wrpc-sw the ppsi
configuration was never changed.

So if you built e.g. "gsi_defconfig" and then reconfigure
for "gsi_pdelay_defconfig" you'll get no pdelay in there.

For me, and the next maintainers of ppsi, the new configuration option
CONFIG_PPSI_FORCE_CONFIG can be unset in order to test with personale
changes in ppsi configuration.
Signed-off-by: Alessandro Rubini's avatarAlessandro Rubini <rubini@gnudd.com>
parent e37189e2
......@@ -13,6 +13,10 @@ config WR_NODE
# most options with no prompt here are prompted-for in the "advanced" section
config PPSI_FORCE_CONFIG
bool
default y
config PRINT_BUFSIZE
int
default 128
......@@ -207,6 +211,16 @@ config DEVELOPER
directly working on this package. Please don't use unless
you are a developer of wrpc-sw.
config PPSI_FORCE_CONFIG
depends on DEVELOPER && WR_NODE
bool "Reconfigure ppsi from wrpc-sw at every build"
default y
help
If you are playing with custom ppsi configurations, please
disable this. Otherwise the option allows wrpc-sw to always
reconfigura ppsi, so if you change from end-to-end to
peer-to-peer here, the change is propagated to the ppsi build.
config HOST_PROCESS
depends on DEVELOPER && WR_NODE
boolean "Build as a host process, to develop/debug network"
......
......@@ -138,6 +138,11 @@ PPSI-FLAGS-$(CONFIG_LM32) = CONFIG_NO_PRINTF=y
$(obj-ppsi):
test -s $(PPSI)/.config || $(MAKE) -C $(PPSI) $(PPSI-CFG-y)
@if [ "$(CONFIG_PPSI_FORCE_CONFIG)" = "y" ]; then \
$(MAKE) -C $(PPSI) $(PPSI-CFG-y); \
else \
echo "Warning: keeping previous ppsi configuration" >& 2; \
fi
$(MAKE) -C $(PPSI) ppsi.o WRPCSW_ROOT=.. \
CROSS_COMPILE=$(CROSS_COMPILE) CONFIG_NO_PRINTF=y
USER_CFLAGS="$(PPSI_USER_CFLAGS)"
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment