Re: [CMake] Ninja generator bug when handling Windows .dll without associated import .lib

2016-08-01 Thread Brad King
On 07/21/2016 12:27 PM, Kamen Lilov wrote: > When a Windows .DLL is generated, the Microsoft linker may sometimes > decide that no import library needs to be built. This happens often in > one of our projects, we have many .dll’s that tie themselves into our > infrastructure during static class

[CMake] Ninja generator bug when handling Windows .dll without associated import .lib

2016-07-22 Thread Kamen Lilov
Hello, Apologies if this is a duplicate, I searched the net but was unable to find references to this bug. When a Windows .DLL is generated, the Microsoft linker may sometimes decide that no import library needs to be built. This happens often in one of our projects, we have many .dll's that

[CMake] Ninja generator bug when handling Windows .dll without associated import .lib

2016-07-22 Thread Kamen Lilov
Hello, Apologies if this is a duplicate, I searched the net to the best of my ability but was unable to find references to this bug. When a Windows .DLL is generated, the Microsoft linker may sometimes decide that no import library needs to be built. This happens often in one of our projects,