[En-Nut-Discussion] Build process proposal: Do not build HTML docs and wx based helpers as default

Ole Reinhardt ole.reinhardt at embedded-it.de
Thu Jul 23 01:09:46 CEST 2015

Hi Uwe,

Am 17.07.2015 13:27, schrieb Uwe Bonnes:
> is there any objection to not build the html docs and the wx-base nutconf
> and nutdisc by default?


clear yes


I see your point. But I'm currently not sure, which of the configurator
tools has the most recent code base. If I do remember correctly there
are at least a few minor changes that have not yet been ported to qnutconf.


Personally I do not use this tool, but I know a lot of people doing so.
Does qnutdisc offers the same functionality?

Personally, as a linux user, I do not have any hassle to build the
complete tool set. But how about the windows users? I think they will
either install wxwidgets or qt, but not both?

So perhaps we should start a discussion if it is worth to maintain two
versions of the same programs, or if we could not agree to focus on the
development of the qt tools (as qt is more common in the windows world
than wx-widgets).

> Not building the html docs speeds up initial build substantial.
> Not building the wx-base program relieves the user from the need to
> fullfill the wx-library requirements.

But how ever we decide, we should print at least a big info about the
enabled / disabled tools at the end of the configure run to notice the
user about the (by default) disabled tools and docs.

Further we should add some extra hints to a seperate readme and our
webpage, so users gets informed that there are more targets which can be



kernel concepts GmbH            Tel: +49-271-771091-14
Sieghuetter Hauptweg 48         Mob: +49-177-7420433
D-57072 Siegen

More information about the En-Nut-Discussion mailing list