08/06/2020 10:33, David Marchand:
> On Mon, Jun 8, 2020 at 2:09 AM Dmitry Kozlyuk
> wrote:
> > On Sun, 7 Jun 2020 12:26:56 +
> > If you create a .def manually, it will override the generation from .map. Of
> > cause, this adds manual work and ideally all .def files should be generated.
>
> O
> Subject: Re: Handling missing export functions in MSVC linkage
>
> On Sun, 7 Jun 2020 12:26:56 +
> Tal Shnaiderman wrote:
>
> > In clang build the .map file is converted into Module-Definition (.Def)
> > File.
>
> If you create a .def manually, it will override the generation from .map.
On Mon, Jun 8, 2020 at 2:09 AM Dmitry Kozlyuk wrote:
>
> On Sun, 7 Jun 2020 12:26:56 +
> Tal Shnaiderman wrote:
>
> > In clang build the .map file is converted into Module-Definition (.Def)
> > File.
>
> If you create a .def manually, it will override the generation from .map. Of
> cause, th
On Sun, 7 Jun 2020 12:26:56 +
Tal Shnaiderman wrote:
> In clang build the .map file is converted into Module-Definition (.Def) File.
If you create a .def manually, it will override the generation from .map. Of
cause, this adds manual work and ideally all .def files should be generated.
> I
Hi,
I was wondering if there is a known solution for the following problem:
Whenever building a DPDK library using clang/MSVC there is an linkage issue if
the rte_*_version.map names a function that isn't being compiled.
For example, in librte_metrics several files in the lib build depend on th
5 matches
Mail list logo
