On Sat, 2017-07-15 at 15:47 +0300, Robert Berger wrote:
> Hi,
>
> On 2017-07-14 23:32, Robert Joslyn wrote:
> >
> > Just to clarify, the typical way this is done is to put the major
> > version number as part of the package name. For example, the
> > recipes
> > could be called zeromq3_3.2.2.bb
Hi,
On 2017-07-14 23:32, Robert Joslyn wrote:
Just to clarify, the typical way this is done is to put the major
version number as part of the package name. For example, the recipes
could be called zeromq3_3.2.2.bb and zeromq4_4.1.5.bb. This assumes
zeromq can tolerate having multiple versions
On Fri, 2017-07-14 at 19:49 +0100, Burton, Ross wrote:
>
> On 14 July 2017 at 18:17, Jimi Damon wrote:
> > Do to a fun "feature" of zeromq, the newest libraries are not
> > backward compatible and hence I need to install a zeromq-4.1.5 and
> > zeromq-3.2.2 libraries onto my
Hi,
Do to a fun "feature" of zeromq, the newest libraries are not backward
compatible and hence I need to install a zeromq-4.1.5 and zeromq-3.2.2
libraries onto my target to assist with one application using the old
version and a newer application using the newer one.
How can I do this