mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] policy for shared or static libs in ptxdist?
Date: Wed, 13 Sep 2017 13:35:56 +0200	[thread overview]
Message-ID: <20345872.4usmrIiGuR@ada> (raw)
In-Reply-To: <20170913055451.pdh435mcniya6d7p@pengutronix.de>

Hello,

Am Mittwoch, 13. September 2017, 07:54:51 schrieb Robert Schwebel:
> > So what I want to know is how this is handled or should be handled
> > in
> > ptxdist? Depending on that I maybe will send a patch for building
> > CMake based (library) packages.
> 
> Make static library handling possible on the library level, but use
> shared for the ptxdist make file.

Sounds reasonable for both sides.

> If we might have a clear usecase in the future, we might want to
> introduce a global mechanism for that. The closer a single library to
> the "standard" way of doing things is, the better.

I thought a little more about how we could handle this for CMake based 
packages. I think hardcoding BUILD_SHARED_LIBS into $(CROSS_CMAKE_USR) 
would be bad, before someone introduced such a global mechanism. FWIW, I 
also don't see such a usecase for static only libs at the moment.

However thanks for your point of view, I will prefer shared libs in 
package receipts for now.

Greets
Alex


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2017-09-13 11:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-12  8:57 Alexander Dahl
2017-09-13  5:54 ` Robert Schwebel
2017-09-13 11:35   ` Alexander Dahl [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=20345872.4usmrIiGuR@ada \
    --to=ada@thorsis.com \
    --cc=ptxdist@pengutronix.de \
    /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