so where does a (in buildroot root)
$> make package/<pkg>/{clean,compile} V=99
leave you?... attach the output or pastebin it .. also check if the new binary
is created in builddir
..ede
On 12.05.2011 16:08, John Zavgren wrote:
> It get's built and staged when I do a "global" make.
>
> I want a technique for making just this one KLM, so that I don't need to
> build the entire enchilada, every time I make a change to it's source code.
> I don't care where the .ko file lands, because I'm moving it to my target
> (via scp) anyway. (I'm not replacing the entire file system with each
> incremental build.)
>
> All I'm looking for, at this point, is a simple hack that will save me a huge
> amount of development time.
>
>
>
> On Thu, May 12, 2011 at 9:37 AM, <[email protected]
> <mailto:[email protected]>> wrote:
>
> isn't it build in the build_dir or just not installed? i see no install
> definition in your makefile. as jow wrote
>
> > f you can you should consider packaging your source as an out-of-tree
> > module, see for example the KernelPackage / kmod defintions in
> > package/wprobe/Makefile .
>
> ede
>
> On 12.05.2011 15:24, John Zavgren wrote:
> > Here's the Makefile. Thanks, John
> > ------------------
> >
> > #
> > # Copyright (C) 2006 OpenWrt.org
> > #
> > # This is free software, licensed under the GNU General Public
> License v2.
> > # See /LICENSE for more information.
> > #
> > # $Id: Makefile 10203 2008-01-15 03:25:11Z matteo $
> >
> > include $(TOPDIR)/rules.mk <http://rules.mk> <http://rules.mk>
> > include $(INCLUDE_DIR)/kernel.mk <http://kernel.mk>
> <http://kernel.mk>
> >
> > PKG_NAME:=vislinkRcv
> > PKG_VERSION:=1.1
> >
> > include $(INCLUDE_DIR)/package.mk <http://package.mk>
> <http://package.mk>
> >
> > define KernelPackage/vislinkRcv
> > SUBMENU:=Network Devices
> > TITLE:=Vislink tunnel receiver.
> > FILES:=$(PKG_BUILD_DIR)/vislinkRcv.$(LINUX_KMOD_SUFFIX)
> > AUTOLOAD:=$(call AutoLoad,50,vislinkRcv)
> > endef
> >
> > define KernelPackage/vislinkRcv/description
> > This module receives and processes frames that have been
> > created by vislink encpasulation.
> > endef
> >
> > define Build/Prepare
> > mkdir -p $(PKG_BUILD_DIR)
> > cp src/Makefile src/vislink.h src/vislinkRcv.c
> $(PKG_BUILD_DIR)/
> > endef
> >
> > define Build/Compile
> > $(MAKE) -C $(LINUX_DIR) \
> > CROSS_COMPILE="$(TARGET_CROSS)" \
> > ARCH="$(LINUX_KARCH)" \
> > SUBDIRS="$(PKG_BUILD_DIR)" \
> > KERNELDIR=$(LINUX_DIR) \
> > CC="$(TARGET_CC)" \
> > modules
> > endef
> >
> > $(eval $(call KernelPackage,vislinkRcv))
> >
> >
> >
> > On Thu, May 12, 2011 at 9:09 AM, <[email protected]
> <mailto:[email protected]> <mailto:[email protected]
> <mailto:[email protected]>>> wrote:
> >
> > Could you post your makefile here?.. ede
> >
> > On 12.05.2011 02:02, John Zavgren wrote:
> > > Thanks, Christian:
> > >
> > > I read the article on the wiki and then I tried "make
> package/vislinkRcv/compile" from the TOPDIR (vislinkRcv is the stuff that I'm
> developing) and no KLM was actually built. When I do the general purpose
> "make" operation from the same context, it is built.
> > >
> > > Confused.
> > >
> > > On Wed, May 11, 2011 at 6:53 PM, Christian Sobkowski
> <[email protected] <mailto:[email protected]> <mailto:[email protected]
> <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]>
> <mailto:[email protected] <mailto:[email protected]>>>> wrote:
> > >
> > > The Wiki basically answers it:
> > > http://wiki.openwrt.org/doc/howto/build
> > >
> > > A 'make path/to/package/compile' (i.e. 'make
> package/busybox/compile') in the TOPDIR with an optional V=99 switch will do
> the trick.
> > >
> > > Cheers,
> > > Christian
> > >
> > > On May 12, 2011, at 12:40 AM, John Zavgren wrote:
> > >
> > >> If I wish to build just one KLM (or application, or
> library), is there a way I can target my build to just that one thing? At
> this time, I'm executing a make command at the top level of the openWRT
> source tree, every time I wish to cross compile something. And, ... , that's
> awfully slow.
> > >>
> > >> Thanks,
> > >> John
> > >>
> > >>
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
