https://cmake.org/cmake/help/latest/module/ExternalProject.html
since CMake can download stuff, it needs to support https, hence SSL, hence
OpenSSL
Best,
---
Jean-Michaël Celerier
http://www.jcelerier.name
On Sun, Jan 14, 2018 at 12:15 AM, Paul Smith wrote:
> Hi all.
>
> I build CMake mys
Hi all.
I build CMake myself. I've noticed that on GNU/Linux by default cmake
will be linked with openssl and require these shared libraries to be
available at runtime.
Why does cmake link with these libraries? I can't think of a reason it
might need them. What do I lose in functionality if I
Thank you Konstantin. get_target_properties(...) works very well.
On Sat, Jan 13, 2018 at 12:06 PM Konstantin Tokarev
wrote:
>
>
> 13.01.2018, 06:26, "Saad Khattak" :
> > Hi,
> >
> > Say I find LibA using find_package(LibA) and I now have access to
> LibA_DIR, which is the build folder of LibA.
Thanks J.
That requires me to use ExternalProject_Add. However, in my case, I have
all Libraries generated/built independently. Should I just start using
ExternalProject_Add for dependencies? If yes, what is the best way to do
that in conjunction with 'find_package(...)'?
On Sat, Jan 13, 2018 at
13.01.2018, 06:26, "Saad Khattak" :
> Hi,
>
> Say I find LibA using find_package(LibA) and I now have access to LibA_DIR,
> which is the build folder of LibA. Is there a way I can query additional
> variables, such as LibA's source directory, install directory etc. i.e.
> variables that are de
maybehttps://cmake.org/cmake/help/v3.2/module/ExternalProject.html
BUILD_ALWAYS 1No stamp file, build step always runs
On Fri, Jan 12, 2018 at 7:41 PM, Saad Khattak wrote:
> Hi,
>
> Let's say I have several CMake enabled libraries that have their own
> respective build directories and have been
