[OpenWrt-Devel] concept of package/compile output
ct at xmodus-systems.de
Wed Aug 6 08:09:56 EDT 2014
On 06.08.2014 13:44, thomas.langer at lantiq.com wrote:
> Hello Claudio,
> Claudio Thomas wrote on 2014-08-06:
>> is there a special concept what the package/compile output (without V=s)
> These are the real targets the build system is executing, nothing intended to be called directly by a user!
> The "make" indicates that it is already the third sub-process of make from your invocation!
> This includes some internal lookups to find the real path of a package and providing
> some other information from the build environment.
>> Sometime you see something like..
>> make -C package/libs/librpc compile
>> make -C package/network/utils/iwinfo compile
>> make -C package/system/uci compile
>> what corresponds to the make-rules
>> make package/libs/librpc/compile
>> make package/network/utils/iwinfo/compile
>> make package/system/uci/compile
>> but also often
>> make -C feeds/packages/admin/htop compile
>> make -C feeds/packages/libs/file compile
>> make -C feeds/packages/net/wget compile
>> what does not corresponds to the expected but not existent target-rules
>> make feeds/packages/admin/htop/compile
>> make feeds/packages/libs/file/compile
>> make feeds/packages/net/wget/compile
>> but to the rules:
>> make package/feeds/packages/htop/compile
>> make package/feeds/packages/file/compile
>> make package/feeds/packages/wget/compile
>> Last ones I've found out by try and error...
>> OK, no I know it, but I'm probably not the first one :-)
> The simple rule, if you want to compile a package NAME,
> just call "make package/NAME/compile" and ignore the real path for the package!
>> Why does the output of the first examples is identical to the target
>> rule and on the others not?
>> Why is in the first examples the section (libs, network/utils, system)
>> part of the target rule and on the others not?
> If you look at the path of the packages, you can find a symlink inside.
> And make will automatically replace it by the real path...
>> Suggestion: Maybe it could make things easier for all newbies that join
>> openwrt in future if the output reflect the real target rule, like in
>> the first examples.
>> Best regards,
> Best Regards,
thanks for the explanation.
Now I now how to compile a package directly without guessing what would
be the correct rule to use.
But I still wonder why sometimes it is shown in one way and on some
packages like the other examples.
Probably sometimes is wondering necessary to learn to comprehend things
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel