[Buildroot] [PATCH 1/2] qwt: compile as a static lib if QT_SHARED is not selected
Richard Genoud
richard.genoud at gmail.com
Mon Jan 26 10:16:04 UTC 2015
2015-01-26 10:54 GMT+01:00 Peter Korsgaard <peter at korsgaard.com>:
>>>>>> "Richard" == Richard Genoud <richard.genoud at gmail.com> writes:
>
> Hi,
>
>>> I agree that it would be cleaner, but the reason the explicit QT_SHARED
> >> stuff was added was afaik a lot of systems only needed Qt in a single
> >> application / that application only used a subset of the Qt
> >> functionality, so having a static libQt while everything else was shared
> >> was quite a big win in size / startup time.
>
> > yes, that's exactly my case. I've got one single Qt application, and Qt
> > is quite huge, so making it static saves a lot of space.
> > I didn't trying to compile with BR2_STATIC_LIBS=y, but I guess that my
> > rootfs will be much bigger.
>
> Indeed. I guess this is (still) quite common.
>
>
> >> It does complicate LGPL compliance and I don't know if the disk space
> >> concerns are as big these days though.
> >>
> > Hum... I didn't think about the static vs dynamic LGPL compliance. I'll
> > have to check that.
>
> I'm not a lawyer, but as I understand it - Because of the LGPLs
> relinking requirements you basically have to provide the object files of
> your application.
That's what I also understood. And it makes perfect sense !
> > And for disk space concern, I must admit that I haven't got much space (
> > 60Mio for the rootfs, and the Qt application takes 10Mio
>
> Heh, I've been involved with projects using Qt in <10MB ;)
:) Well, I guess that I may have some possible optimization to do !
More information about the buildroot
mailing list