>From the CMake side of things yes, but MSVC requires an import library. You
>could use a tool such as Digital Mars' implib tool
>(https://digitalmars.com/ctg/implib.html), or use dumpbin to list all exports,
>put those in a .def file and use lib to create an import library from the def
>file.
You are correct this doesn't work with ninja and ExternalProjects due
to the jobserver work not being upstreamed. There are forks of ninja
that do have jobserver support and therefore this would work with
those.
On Fri, Mar 30, 2018 at 1:27 PM, Isaiah Norton wrote:
>> A "CMAKE_JOB_POOLS" variable
Hi all,
Reading the documentation I can see:
https://cmake.org/cmake/help/v3.11/manual/cmake.1.html?highlight=find%2
0package#find-package-tool-mode id="-x-evo-selection-start-marker">
"
Note
This mode is not well-supported due to some technical limitations. It
is kept for compatibility but shoul
Hello,
Suppose I have a cmake_minimum_required(VERSION 2.8.12) project I would like to
contribute to.
So when I am testing code for a v2.8.12 project, but my installed CMake version
is say 3.10, if I (accidentally, or through ignorance) write code that would
only work in CMake 3.x but not in 2
On 2018 M04 3, Tue 16:01:58 CEST jeandet wrote:
> Hi all,
>
> Reading the documentation I can see:
> https://cmake.org/cmake/help/v3.11/manual/cmake.1.html?highlight=find%2
> 0package#find-package-tool-mode id="-x-evo-selection-start-marker">
> "
> Note
>
> This mode is not well-supported due to
> if I (accidentally, or through ignorance) write code that would only work in
> CMake 3.x but not in 2.8.12, will the build fail or should I make sure to
> install 2.8.12 and test using that? if I ended up using an entirely new
> command that did not exist at the time of 2.8.12, but does
Ok cool thank you for explaining! Somewhat related, I really enjoy that I can
build CMake 2.8.12 with CMake 3.10 :)
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMa
> > Is it not possible to wrap an external DLL-only library in an IMPORTED
> > target?
> >
>
> Yes it is.
>
> > I have an external dependency that is a single DLL (shared library) and a
> > header file, but no LIB (static library) file.
>
> How does this work in Visual Studio C++? If I am not
> -Ursprüngliche Nachricht-
> Von: CMake [mailto:cmake-boun...@cmake.org] Im Auftrag von Marek
> Vojtko (Firaxis)
> Gesendet: Dienstag, 3. April 2018 23:24
> An: cmake@cmake.org
> Betreff: Re: [CMake] IMPORTED DLL-only Target on MSVC
>
> > > Is it not possible to wrap an external DLL-only
