I'm not an expert but the include/kernel.mk file (which gets included from target.mk) has the following two lines:
PATCH_DIR ?= ./patches$(shell [ -d "./patches-$(KERNEL_PATCHVER)" ] && printf -- "-$(KERNEL_PATCHVER)" || true ) FILES_DIR ?= ./files$(shell [ -d "./files-$(KERNEL_PATCHVER)" ] && printf -- "-$(KERNEL_PATCHVER)" || true ) You can probably accomplish what you want by overriding the settings in your target Makefile with empties, before you include target.mk. PATCH_DIR := FILES_DIR := ===Jac ----- Original Message ----- From: "bifferos" <biffe...@yahoo.co.uk> To: "OpenWrt Development List" <openwrt-devel@lists.openwrt.org> Sent: Saturday, March 28, 2009 3:27 AM Subject: [OpenWrt-Devel] OpenWrt build system: New target,how to avoid generic patches/files? > > > I am trying to add a new OpenWrt target by introducing a new set of files > under target/linux/<target>/. > > I would like to avoid applying any generic kernel patches for this target, > however I'm unable to work out how to do this, other than to just remove > all generic patches and files prior to the build: > > $ rm -Rf target/linux/generic-2.6/patches-2.6.27/* > $ rm -Rf target/linux/generic-2.6/files-2.6.27/* > $ rm -Rf target/linux/generic-2.6/files/* > > This is not ideal as I'd like to leave to OpenWrt files untouched. I > don't care how much complexity I add to my own target makefile. I have > tried redefining GENERIC_PLATFORM_DIR, GENERIC_PLATFORM_DIR, > GENERIC_FILES_DIR to a dummy empty location after including target.mk, > however nothing I do seems to work. > > Suggestions most welcome. > > thanks, > Simon. > > > > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
