Re: Wine MinGW system libraries

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Sep 7, 2021 at 5:45 PM Zebediah Figura <zfigura@xxxxxxxxxxxxxxx> wrote:
> On 9/7/21 2:12 AM, Richard W.M. Jones wrote:
> > On Mon, Sep 06, 2021 at 05:59:41PM -0500, Zebediah Figura wrote:
> >> Thanks everyone for their input.
> >>
> >> There seems to be a consensus that Fedora would prefer that we use
> >> their MinGW dynamic libraries. However, this leaves a couple of
> >> questions:
> >>
> >> * As I described in [1], we *may* be able to hack things in the Wine
> >> loader such that we can use unmodified dynamic libraries. However,
> >> it's not fully clear yet that it's feasible. If it turns out to be
> >> infeasible, what preferences does Fedora have? (Renamed dynamic
> >> libraries shipped separately, shipped as part of Wine, static
> >> libraries, etc...)
> >
> > Adding -static subpackages is the easiest option from our point of
> > view.  As I mentioned in the previous email this would mean adjusting
> > an existing spec such as:
> > https://src.fedoraproject.org/rpms/mingw-gnutls/blob/rawhide/f/mingw-gnutls.spec
> > so that it builds the static library.  It's a simple and obvious
> > change.
> >
> > But can Wine use the static library built this way unmodified?
> > And are there any other implications versus using a DLL?
>
> I believe we should be able to use unmodified static libraries, yes.
>
> There are the usual implications—more space on disk and in memory; in
> Wine's case it doesn't really matter a lot, but we do still have cases
> of multiple DLLs that use the same library. It may be possible to use
> helper DLLs to avoid that in most cases.
>
> And, of course, I hate developing with static libraries :-(

Could you perhaps just build a new dynamic library (with the adjusted
name) by linking an empty/dummy object with the Fedora-provided static
library? (Not sure if that's possible, but it's what came to my mind
when reading this thread.)

-- 
Ondrej Mosnacek
Software Engineer, Linux Security - SELinux kernel
Red Hat, Inc.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux