From: Moritz WarningMoritz Warning
Reply: OpenWrt Development List [email protected]
Date: January 28, 2014 at 12:40:31 AM
To: [email protected] [email protected]
Subject: Re: [OpenWrt-Devel] Basic Package/Feed Workflow
-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On 01/28/2014 07:20 AM, Chad Monroe wrote:
>> The core problem I need to solve is how to compile/test a package and make
>> change after change after change to it, then when it’s ready, create a patch
>> set. I have a feeling I’ve been doing things the hard way for a while and
>> would appreciate a push in the right direction. I love what OpenWRT is doing
>> for the community and an more than happy to contribute back; if this is
>> something that isn’t in a wiki and should be I’m more than happy to document
>> it if someone can help me get the procedure straight. Thanks for your time,
>
>What I do for step by step development is to create a soft link to my project
>folder:
>ln -s ~/myproject/.git openwrt/package/myproject/git-src
>
>Enable "Advanced configuration options" => "Enable package source tree
>override"
>so that OpenWrt will get follow the soft link.
>
>Now you can edit the sources of your package and hit compile every time.
>
>regards,
>mwarning
>
>
>
>
>
Great tip. By setting the symlink and enabling package source tree override, I
was able to build a package from a source dir on my local host. However, when
I made subsequent changes to files in my source dir, followed by:
make package/<pkgname>/clean
make package/<pkgname>/compile
OpenWRT still built my package using my original sources (all subsequent
changes were ignored).
Is there an additional step required get OpenWRT to "see" the latest versions
of my sources?
thanks,
-adam
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
