Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #105299

Re: dll and function name conflict

From Cholo Lennon <chololennon@hotmail.com>
Newsgroups comp.lang.c
Subject Re: dll and function name conflict
Date 2017-03-01 16:00 -0300
Organization Aioe.org NNTP Server
Message-ID <o975p2$18pj$1@gioia.aioe.org> (permalink)
References <57f7a647-93d2-467d-9d2a-e0343f1e8316@googlegroups.com> <iq_sA.69742$EN2.65582@fx44.iad> <7a224ce3-4afe-4625-9c29-04ee3c7b5264@googlegroups.com>

Show all headers | View raw


On 27/02/17 15:56, fir wrote:
> W dniu poniedziałek, 27 lutego 2017 19:42:30 UTC+1 użytkownik Scott Lurndal napisał:
>> fir <profesor.fir@gmail.com> writes:
>>> say i got two dlls (A & B) whose i link
>>> statically
>>
>> The 'd' in 'dll' implies dynamic.
>>
>> If you have a.a and b.a, then you have
>> static libraries (technically archives of
>> object files) that you may link with.
>>
>>>
>>> what if one of the function in A has
>>> teh same name as one of the function
>>> in B.. is this conflict unresolvable then
>>> and must i just link it dynamically and
>>> rename the pointer?
>>
>> The first symbol definition found by the linker
>> will be used, so the order in which you specify
>> the static libraries (object archives) matters.
>>
>> windows milage may vary.
>
> those are dynamic libreries but linked
> pseudo statically - know what i mean
>

What you mean is "implicit Linking" of dynamic link libraries (using 
Windows terminology)

> you just add  -l"dlllibname"  in command line when compiling app and it will link to it as startup (this is done probably by just creating (filling) import table in exe .. mystery is however why such compilation to be succesfull need a physical image of given dll to be
> present.. it seems like set of declarations could maybe suffice.. well problem is maybe that that import declaration do not name the modules so it dont know what dll name to use.. if so this is a glith
>


-- 
Cholo Lennon
Bs.As.
ARG

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

dll and function name conflict fir <profesor.fir@gmail.com> - 2017-02-27 10:18 -0800
  Re: dll and function name conflict fir <profesor.fir@gmail.com> - 2017-02-27 10:25 -0800
  Re: dll and function name conflict scott@slp53.sl.home (Scott Lurndal) - 2017-02-27 18:42 +0000
    Re: dll and function name conflict fir <profesor.fir@gmail.com> - 2017-02-27 10:56 -0800
      Re: dll and function name conflict Chad <cdalten@gmail.com> - 2017-02-27 11:49 -0800
      Re: dll and function name conflict Cholo Lennon <chololennon@hotmail.com> - 2017-03-01 16:00 -0300
        Re: dll and function name conflict fir <profesor.fir@gmail.com> - 2017-03-01 12:03 -0800
          Re: dll and function name conflict fir <profesor.fir@gmail.com> - 2017-03-01 12:20 -0800
          Re: dll and function name conflict Cholo Lennon <chololennon@hotmail.com> - 2017-03-01 17:39 -0300
            Re: dll and function name conflict Chad <cdalten@gmail.com> - 2017-03-01 14:38 -0800
              Re: dll and function name conflict Cholo Lennon <chololennon@hotmail.com> - 2017-03-02 12:19 -0300
                Re: dll and function name conflict gazelle@shell.xmission.com (Kenny McCormack) - 2017-03-02 15:45 +0000
                Re: dll and function name conflict fir <profesor.fir@gmail.com> - 2017-03-02 11:50 -0800
                Re: dll and function name conflict Chad <cdalten@gmail.com> - 2017-03-02 12:32 -0800
                Re: dll and function name conflict Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-03-04 12:48 -0800
                Re: dll and function name conflict "James R. Kuyper" <jameskuyper@verizon.net> - 2017-03-04 10:47 -0500
                Re: dll and function name conflict fir <profesor.fir@gmail.com> - 2017-03-05 04:22 -0800
                Re: dll and function name conflict Chad <cdalten@gmail.com> - 2017-03-05 06:45 -0800

csiph-web