Windows dll .edata Name RVA

[Keno]

When building with MinGW on windows openblas creates both openblas-r0.2.2.dll and also symlinks (which is really a hardlink on windows) to openblas.dll. However, while this maybe a valid thing to do on other platforms, the PE/COFF format contains something called the "Name RVA" in the .edata section. However, this causes the problem that libraries and executables linking directly to openblas.dll cannot find the dll afterwards as they expect it to called openblas-r0.2.2.dll in accordance with the "Name RVA". I am unsure about the correct solution to this, but I see the following possibilities:

1. Don't generate openblas.dll and use openblas-r0.2.2.dll
2. Don't generate openblas-r0.2.2.dll and use openblas.dll
3. Generate both independently of each other with the correct "Name RVA"
4. Patch openblas.dll to have the correct "Name RVA"

I would prefer to keep openblas.dll so I'm really fine with 2-4, but would tend more towards 3-4, though I am unsure as to the feasibility of 4. Let me know what you think the the best solution is and I can probably implement it (or you could implement it yourself).

[xianyi]

@zchothia , any suggestion?

Xianyi

[zchothia]

Thanks for the pointing this out. I agree with your assessment and would be inclined to take either option 2 or 3. Whilst option 4 is technically possible, I would dissuade from its use due to the added complexity it would bring. Personally I think option 2 is most appropriate, since openblas.dll would be referenced without specifying a particular version. This makes it possible to upgrade between OpenBLAS versions without needing to re-link an application. Does this sound reasonable or would it be preferable to take option 3?

[Keno]

Yeah, taking option 2 sounds good to me.