Petr,
Thanks for the info. I'm working on getting the builds to work exactly like I
want for both native *nix and cross-compile Windows builds, so it's a learning
process. I do appreciate your info.
vadtecvad...@vadtec.net
On Thu, 04 Feb 2016 01:49:12 -0600 Petr Kmoch
Hi Vadtec.
*The* standard CMake way of dealing with building your dependencies is the
ExternalProject module (
https://cmake.org/cmake/help/latest/module/ExternalProject.html ). It's a
huge beast, but I belive there are some examples and tutorials available
out there.
The gist is: you create a
On 30/01/16 09:42 PM, vadtec wrote:
> Let me start by saying I consider my self a cmake newbie. I've made
> simple makefiles and simple cmake files, but anything more complicated
> has to this point eluded me. Not for a lack of trying, searching,
> researching, trail, and a great deal of error: I
On 31-Jan-16 03:42, vadtec wrote:
curl, libiconv, libpng, libssh2, and zlib are the libs I want to build
and use both on Linux and Windows. I know all of those are available
on Linux and I could use the system installed versions, but I want to
use the same vesions on Windows as well. The
Vadtec,
> My main problem is getting cmake to use only my locally
installed/compiled copies of the libs. I need those libs to live along side
the binaries, and using the versions I compile is important.
I'll answer the question of finding the libraries and not the building
problem. We (in my
Let me start by saying I consider my self a cmake newbie. I've made simple
makefiles and simple cmake files, but anything more complicated has to this
point eluded me. Not for a lack of trying, searching, researching, trail, and a
great deal of error: I simply have not been able to achieve the
I generally use one CMake build for compiling a single project. Your
dependencies should be built separately from your main program. Ways to do
this:
1. Try EasyBuild or Spack. The only reason I wouldn't recommend them is
I'm not sure if they've ever been run on Windows. But that doesn't mean
