Linux CAN drivers development
 help / color / mirror / Atom feed
From: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
To: "André Hartmann" <aha_1980@gmx.de>
Cc: linux-can@vger.kernel.org, Mirza Krak <mirza.krak@gmail.com>
Subject: Re: SocketCAN device enumeration API
Date: Thu, 11 Aug 2016 12:05:58 +0200	[thread overview]
Message-ID: <20160811100558.GA2147@airbook.newtec.eu> (raw)
In-Reply-To: <e7d06ad8-579d-0053-c7e5-ddc8feee673b@gmx.de>

> Hello Kurt and Mirza,
> 
> thanks for your pointers, I did already did search time, but haven't found
> much useful.
> 
> Kurt, your library does exactly what I need. I was impressed (and a bit
> shocked), how much code is necessary to do this work.

I too think netlink was as such not designed to be an end-user
interface, but a generic mechanism to create libraries like
libsocketcan, of libenumif.

> I think (parts of)
> your library would also make a good extension to libsocketcan, as it seems
> I'm not the only one asking, so there is definitely a need for this
> function.

Well, libsocketcan could copy part of the code for easy CAN enumeration.
libenumif is not really restricted to CAN, or any other type.

> 
> However, the only possiblity I see for me now, would be to ship a copy of
> libenumif along with Qt and to integrate it into Qt's build system for
> cross-platform builds.

When you ship libenumif along with QT, doesn't that imply that it should
stay out of QT.
Or did you mean to ship libenumif as shared object along with QT's
shared objects?

> 
> Thats where my problems begin. I neither know about the technical, nor the
> legal possibilities to do so :(

QT is not my technical competence.
Legally, libenumif is shipped with LGPLv3. I don't see a problem
shipping it. LGPL allows to use the library (as shared object) from
non-GPL code AFAIK.

Kurt

  reply	other threads:[~2016-08-11 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 11:06 SocketCAN device enumeration API André Hartmann
2016-08-09 12:33 ` Mirza Krak
2016-08-09 14:04 ` Kurt Van Dijck
2016-08-11  8:36   ` André Hartmann
2016-08-11 10:05     ` Kurt Van Dijck [this message]
2016-08-11 10:31       ` André Hartmann

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=20160811100558.GA2147@airbook.newtec.eu \
    --to=dev.kurt@vandijck-laurijssen.be \
    --cc=aha_1980@gmx.de \
    --cc=linux-can@vger.kernel.org \
    --cc=mirza.krak@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox