From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Wed, 9 Oct 2019 15:34:54 +0200 Subject: [Buildroot] [PATCH v2 7/9] package/netopeer2-keystored: add package In-Reply-To: References: <20191009112656.21232-1-heiko.thiery@gmail.com> <20191009112656.21232-8-heiko.thiery@gmail.com> <20191009141235.016e4b23@windsurf> Message-ID: <20191009153454.1f5f3e09@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Wed, 9 Oct 2019 15:14:15 +0200 Heiko Thiery wrote: > > > +NETOPEER2_KEYSTORED_LICENSE = BSD-3-Clause > > > +NETOPEER2_KEYSTORED_LICENSE_FILES = LICENSE > > > +NETOPEER2_KEYSTORED_SUBDIR = keystored > > > +NETOPEER2_KEYSTORED_DEPENDENCIES += host-sysrepo sysrepo > > So I have to move all the stuff from the 3 packages (netopeer2-server, > netopeer2-cli, netopeer2-keystored) into one package e.g. netopeer2. Yes. > Is it possible to have there 3 different build targets depending on > the configuration? It depends on what you call build targets. Looking at the netooper2 code base, it's indeed 3 separate projects together, each with its own CMake build system. I.e, there is no top-level CMakeLists.txt to build the different components. So we would have to do the CMake configuration/build/install steps manually, as the cmake-package infrastructure only deals with a single top-level CMake build infrastructure, which netopeer2 doesn't have. In the light of this in the end, perhaps it makes sense to have three packages like you did. It kind of reflects the fact that even though they are stored in the same Git repo, they are three independent components each with its own build system. Peter, Arnout, Yann, any thoughts ? See https://github.com/CESNET/Netopeer2 for the code base. Thomas -- Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com