[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nano-devel] begin using gnulib?
|
From: |
Kamil Dudka |
|
Subject: |
Re: [Nano-devel] begin using gnulib? |
|
Date: |
Fri, 05 Feb 2016 22:59:37 +0100 |
|
User-agent: |
KMail/4.14.8 (Linux/4.1.15-gentoo-r1; KDE/4.14.8; x86_64; ; ) |
On Friday, February 05, 2016 12:40:19 Chris Allegretta wrote:
> > And then: how much bigger is nano going to become
> > because of using modules from gnulib? Surely some
> > of those modules will contain functions that nano won't
> > use. Are they still compiled into the binary?
>
> Since it's dynamically linked against,
AFAIK, gnulib supports static linking only.
> it shouldn't AFAIK change binary size significantly.
This is true -- the resulting nano binary will include only gnulib code that
is directly or indirectly used by nano assuming a smart enough linker is used.
Kamil
- [Nano-devel] [PATCH 1/2] check stat's result and avoid calling stat on a NULL pointer, Kamil Dudka, 2016/02/03
- [Nano-devel] [PATCH 2/2] use futimens() if available, instead of utime(), Kamil Dudka, 2016/02/03
- Re: [Nano-devel] [PATCH 2/2] use futimens() if available, instead of utime(), Mike Frysinger, 2016/02/03
- Re: [Nano-devel] [PATCH 2/2] use futimens() if available, instead of utime(), Kamil Dudka, 2016/02/03
- [Nano-devel] begin using gnulib?, Benno Schulenberg, 2016/02/04
- Re: [Nano-devel] begin using gnulib?, Mike Frysinger, 2016/02/04
- Re: [Nano-devel] begin using gnulib?, Chris Allegretta, 2016/02/05
- Re: [Nano-devel] begin using gnulib?,
Kamil Dudka <=
Re: [Nano-devel] [PATCH 1/2] check stat's result and avoid calling stat on a NULL pointer, Benno Schulenberg, 2016/02/06