mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Handling build time only dependencies
Date: Fri, 22 Sep 2017 16:06:19 +0200	[thread overview]
Message-ID: <20170922140619.zsr4pvbl4wirxco3@pengutronix.de> (raw)
In-Reply-To: <20170922132407.qksxkmfe55ewq5up@falbala.home.lespocky.de>

On Fri, Sep 22, 2017 at 03:24:08PM +0200, Alexander Dahl wrote:
> Hello,
> 
> I'm a little stuck with a problem I consider a maybe common one. I
> have an ordinary C library. For some projects I compile and link
> against it the usual way, so in my applications .in rule I just do
> 'SELECT LIBFOO' and the library package will be copied to the target
> including .so file, loading at runtime etc.
> 
> Now for another BSP I have another application where I only need to
> include some header files of this library, but do not call any API
> functions and do not link against it. So I only need the library at
> build time, no library package has to be copied to the target later
> and the library doesn't need to be loaded at runtime.
> 
> Can I express this somehow in ptxdist and how?
> 
> (This is just to save space on the target, I know I could let copy the
> lib to the target, where it won't be loaded then, which is the way
> it's done currently.)

"select LIBFOO if BUILDTIME"

Michael


-- 
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-22 14:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 13:24 Alexander Dahl
2017-09-22 14:06 ` Michael Olbrich [this message]
2017-09-22 15:21   ` 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=20170922140619.zsr4pvbl4wirxco3@pengutronix.de \
    --to=m.olbrich@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