OpenWrt Forum Archive

Topic: Determining the list of options used to compile an official package.

The content of this topic has been archived on 7 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,

In OpenWrt build system, there are usually some options in the menuconfig for packages. How do I know which of them was selected to build the package present in the official repository?

Thanks in advance.
Pierre.

(Last edited by pparent on 31 May 2016, 10:48)

The default ones. For releases Luci GUI is included, but otherwise it is plain defaults also there.
See example of 15.05.1 release config: https://downloads.openwrt.org/chaos_cal … onfig.diff

(buildbot trunk snapshots do not include Luci, as that is not included by default)

Starting with and empty .config and selecting your device will give you the same options for the package inclusion and possible settings.

The same goes for individual packages, both snapshots and releases are compiled with the defaults in the source repo.

Thanks for your message,
So I need to be more specific.

I'm trying to rebuild coova-chilli from 15.05. The problem is that the options used to compile coova-chilli depend on whether or not another package is selected into menuconfig or not (ipt-coova).

$(if $(CONFIG_COOVACHILLI_MATRIXSSL),--with,--without)-matrixssl \
    $(if $(CONFIG_COOVACHILLI_CYASSL),--with,--without)-cyassl \
    $(if $(CONFIG_COOVACHILLI_OPENSSL),--with,--without)-openssl \
    $(if $(CONFIG_PACKAGE_kmod-ipt-coova),--with-nfcoova) \
    )

https://github.com/openwrt/packages/blo … i/Makefile

In this case how can I know what options was really used?

Pierre.

pparent wrote:

In this case how can I know what options was really used?

The basic starting point is that defaults are used. Other options like they are in https://github.com/openwrt/packages/blo … /Config.in

Regarding that one dependency to a kernel module, snapshots and release builds are made with "build all modules", which leads to that kmod-ipt-coova being present in the build, and I think that it will lead into enabling that option in coova's Makefile. Not quite sure, though.

It should also be noted that the kmod-ipt-coova is completely useless without coova-chilli built without --with-nfcoova. So if this option is not included in default built, then the package ipt-coova is not usefull in openwrt.

But if coova-chilli is built with the --with-nfcoova option then it should not work without the ipt-coova package. Since it works without it, I guess that it was compiled without --with-nfcoova option.

(Last edited by pparent on 31 May 2016, 13:54)

The discussion might have continued from here.