Re: [general][build] compile units linked in both verifier.lib and verifier-ext.lib

[Alexey Varlamov <al...@gmail.com>]

I think the reason is that verifier makes callbacks to VM engine, thus
needs either runtime-binded interface to VM or explicit linkage with
it. The first variant is not elaborated (yet?) so the last is adopted.

--
Alexey

2008/3/29, Francis ANDRE <fr...@easynet.fr>:
> Gregory
>
> Is there any reason why verifier should be a lib and not a dll??
>
> Francis
>
> Gregory Shimansky a écrit :
> > On 29 March 2008 Francis ANDRE wrote:
> >> Hi Harmonists
> >>
> >> By looking at the contents of verifier.lib and verifer-ext.lib, it seems
> >> that some programs are compiled in both libraries. Is it normal??
> >
> > The verifier-ext is an external (or extension?) library that may be used as a
> > separate component used by a different project. So it includes all of the
> > verifier sources and some additional stuff such as stack map calculation. I
> > don't know all of the details, you may want to look at [1] for them.
> >
> > [1] http://harmony.apache.org/subcomponents/drlvm/verifier.html
> >
>