Re: [cmake-developers] [CMake] Need ideas/opinions on third party library management

2016-08-13 Thread Ian Henriksen
On Sat, Aug 13, 2016 at 6:43 PM Elizabeth A. Fischer < elizabeth.fisc...@columbia.edu> wrote: > I would look into Anaconda, which does work for Windows. Its version > management is not as well developed as Spack, but it's more cross-platform. > > Auto-builders are just coming into their own,

[cmake-developers] [PATCH v6] For Windows encode process output to internally used encoding

2016-08-13 Thread Dāvis Mosāns
Typically Windows applications (eg. MSVC compiler) use current console's codepage for output to pipes so we need to encode that to internally used encoding (KWSYS_ENCODING_DEFAULT_CODEPAGE). --- Source/CMakeLists.txt | 2 + Source/ProcessOutput.hxx.in| 160

Re: [cmake-developers] [CMake] Need ideas/opinions on third party library management

2016-08-13 Thread Elizabeth A. Fischer
I would look into Anaconda, which does work for Windows. Its version management is not as well developed as Spack, but it's more cross-platform. Auto-builders are just coming into their own, it's a brave new world. I expect things to be more complete in a few years. -- Elizabeth On Sat, Aug

Re: [cmake-developers] [CMake] Need ideas/opinions on third party library management

2016-08-13 Thread Robert Dailey
I did some brief digging into spack, and it doesn't look like it supports Windows. All I see are shell scripts and the documentation uses POSIX. If I'm going to use a package manager, it needs to be able to support Android (ARM), Windows, and Linux. I have specific toolchains that I'll need the