All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Leopold Palomo-Avellaneda <leo@alaxarxa.net>, xenomai@xenomai.org
Subject: Re: [Xenomai] Packaging Xenomai-3
Date: Fri, 23 Jan 2015 17:04:37 +0100	[thread overview]
Message-ID: <54C27115.7030901@xenomai.org> (raw)
In-Reply-To: <129277905.Ag2XebZWbK@soho>

On 01/23/2015 01:09 PM, Leopold Palomo-Avellaneda wrote:
> Hi,
> 
> now that I have some kernel to boot, I would like to ask some aspects of 
> Xenomai-3 in order to package it.
> 
> Reading the documentation, now the new libxenomai could use two kind of 
> kernels: the patched one (Cobalt) or the preempt_rt (Mercury).
> 

Mercury does not require preempt-rt. In some cases, one may want the API
emulation capabilities without actually having real-time requirements.

> 1) Is it possible to have _only_ one library (binary) that uses one or another 
> kernel in function which is running?
> 

No. Definitely not.

> 2) If not, as we must recompile the library, all the programs linked against 
> must be recompiled or if it's binary compatible?
> 

Can't have the same ABI. Two separate builds are required.

> 3) Comparing the files generated (xenomai-2.x vs xenomai-3.x, if you bump the 
> sonames of libanalogy, libpsos and libvxworks you could have (I guess) both 
> binary versions installed in the same box.
> 

This would make sense, but only for libs. Scripts, includes would conflict.

> 4) Why the libvxworks has lower soname version in 2.6.4 than in 3.0.0?
> 

Because it has been entirely rewritten over the copperplate interface
and extended in terms of emulated services.

-- 
Philippe.


  parent reply	other threads:[~2015-01-23 16:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 12:09 [Xenomai] Packaging Xenomai-3 Leopold Palomo-Avellaneda
2015-01-23 15:52 ` Gilles Chanteperdrix
2015-01-23 16:50   ` Leopold Palomo-Avellaneda
2015-01-23 17:27     ` Gilles Chanteperdrix
2015-01-24 17:56       ` Leopold Palomo-Avellaneda
2015-01-25  9:14         ` Philippe Gerum
2015-01-25 11:14           ` Leopold Palomo-Avellaneda
2015-01-25 18:10             ` Philippe Gerum
2015-01-25 18:43               ` Leopold Palomo-Avellaneda
2015-01-26 12:08                 ` Gilles Chanteperdrix
2015-01-26 12:39                   ` Leopold Palomo-Avellaneda
2015-01-26 13:38                     ` Daniele Nicolodi
2015-01-26 14:17                       ` Leopold Palomo-Avellaneda
2015-01-26 14:24                         ` Daniele Nicolodi
2015-01-26 14:01                     ` Philippe Gerum
2015-01-26 14:47                       ` Leopold Palomo-Avellaneda
2015-01-26 14:55                         ` Gilles Chanteperdrix
2015-01-26 14:08                     ` Gilles Chanteperdrix
2015-01-26 14:56                       ` Leopold Palomo-Avellaneda
2015-01-26 14:59                         ` Gilles Chanteperdrix
2015-01-26 17:46                           ` Leopold Palomo-Avellaneda
2015-01-26 18:20                             ` Gilles Chanteperdrix
2015-01-26 22:17                               ` Leopold Palomo-Avellaneda
2015-01-26 22:26                                 ` Daniele Nicolodi
2015-01-26 22:57                                   ` Leopold Palomo-Avellaneda
2015-01-26 18:32                             ` Gilles Chanteperdrix
2015-01-26 22:19                               ` Leopold Palomo-Avellaneda
2015-01-23 16:04 ` Philippe Gerum [this message]
2015-01-23 17:02   ` Leopold Palomo-Avellaneda
2015-01-23 17:24     ` Philippe Gerum
2015-01-23 17:47       ` Gilles Chanteperdrix
2015-01-24 10:05         ` Philippe Gerum
2015-01-24 17:43       ` Leopold Palomo-Avellaneda

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=54C27115.7030901@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=leo@alaxarxa.net \
    --cc=xenomai@xenomai.org \
    /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.