All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3 0/4] openpowerlink bump to v2.2
Date: Mon, 10 Aug 2015 15:14:24 +0200	[thread overview]
Message-ID: <55C8A3B0.2060109@openwide.fr> (raw)
In-Reply-To: <1438954143-23533-1-git-send-email-romain.naour@openwide.fr>

Hi Thomas,

Le 07/08/2015 15:28, Romain Naour a ?crit :
> From doc/openpowerlink.md:
> "The openPOWERLINK release V2.X is an evolution of the openPOWERLINK V1 stack.
> Running the kernel and user layers of openPOWERLINK on different processors in
> a multi-processor/multi-platform architecture, required fundamental changes in
> the Communication Abstraction Layer. Additionally, the existing code base was
> greatly improved so that it is easier to understand and maintain. Due to these
> reasons a new major release was started."
> 
> The openpowerlink2 package archive contains several cmake projects,
> and each of them must be packaged separately in Buildroot.
> 
> "With version 2.0, the source code has been cleanly split into an
> application-oriented user library and a time-critical stack driver."
> 
> This complicates the packaging but it helps to refine the dependencies
> compared to openpowerlink v1 build system.
> (openpowerlink v1 requires C++ only for the qt demo)
> 

You asked on IRC if it's possible to have only one openpowerlink package.
I would say yes, by adding a top-level CMakeLists.txt like this one [1] but
the build dependencies between each projects are not handled.
All is build at the same time.
This is a problem for demo applications which are looking for openpowerlink
libraries using FIND_OPLK_LIBRARY, but before it had time to be compiled.

I don't know how to add a dependency between the "stack" project and the "app"
project.

Otherwise, we need to package each sub projects in order to handle the
dependency outside of the CMake world...

Samuel, have you an idea ?

Best regards,
Romain

[1] https://sourceforge.net/u/kubu/code/ci/f80f43d02aabb0f2acc09d4ce420ecc3dcfad81c/

      parent reply	other threads:[~2015-08-10 13:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 13:28 [Buildroot] [PATCHv3 0/4] openpowerlink bump to v2.2 Romain Naour
2015-08-07 13:29 ` [Buildroot] [PATCHv3 1/4] package/openpowerlink: bump to v2.2.0 Romain Naour
2015-08-07 13:29 ` [Buildroot] [PATCHv3 2/4] package/openpowerlink-kernel-drivers: new package Romain Naour
2015-08-07 13:29 ` [Buildroot] [PATCHv3 3/4] package/openpowerlink-pcap-daemon: " Romain Naour
2015-08-07 13:29 ` [Buildroot] [PATCHv3 4/4] package/openpowerlink-apps-demo-mn-console: " Romain Naour
2015-08-10 13:14 ` Romain Naour [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55C8A3B0.2060109@openwide.fr \
    --to=romain.naour@openwide.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.