mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] policy for shared or static libs in ptxdist?
Date: Wed, 13 Sep 2017 07:54:51 +0200	[thread overview]
Message-ID: <20170913055451.pdh435mcniya6d7p@pengutronix.de> (raw)
In-Reply-To: <2374422.4ql4Zy1NQ0@ada>

On Tue, Sep 12, 2017 at 10:57:17AM +0200, Alexander Dahl wrote:
> Hei everyone,
> 
> for a C library project built with CMake, which I'm currently the 
> maintainer for, I got some patches from the buildroot folks to support 
> static linking of the library. AFAIK buildroot supports building the 
> whole BSP statically linked. For CMake based projects it sets the global 
> CMake variable BUILD_SHARED_LIBS to control if a package should be built 
> as shared or static lib (which of course must be supported by the 
> upstream packages then).
> 
> As far as ptxdist is concerned, I used grep today to find out how this 
> is handled over here. What I could see was no central support for either 
> the one or the other, but letting the packages do what they want, each 
> handling it individually. However I saw most packages (most are 
> autotools based) setting --enable-shared and --disable-static – so I 
> assume the general policy for ptxdist is to build shared libraries and 
> there's no support for building static libraries, except for some rare 
> packages, where a menu option for this exists.

I'm sharing your point of view.
 
> 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.

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.

rsc
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-09-13  5:54 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 [this message]
2017-09-13 11:35   ` Alexander Dahl

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=20170913055451.pdh435mcniya6d7p@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --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