Ditto! I really like having just one thing to update when I make a
change...at least once we can get rid of the Makefile.am version. Which
reminds me, I'll need to update that for the changes to the samples...sigh.
It is really beautiful in handling differences between different build
types. It
I also want to say that I find the CMake system to be very flexible and,
after a little education, easy to work with. And highly system
independent.
When I recommended CMake I had no idea it would work as well as it has
for us.
David Ashley
On Thu, 2014-06-12 at 16:16 -0400, Rick McGuire wrote:
No, I basically implemented my own version of CPack, leveraging some of the
files produced by the install commands. CMake actually generates a script
that takes care of the hardest parts of the process, so it turned out to be
pretty easy to implement.
I'm finding this version to be incredibly fle
On Thu, Jun 12, 2014 at 12:47 PM, Rick McGuire
wrote:
> I think it is ready to go, although it probably needs a round or two of
> testing to make sure everything works. Right now, can build either of two
> ways, the non-template based version you did (although this version is
> probably out of da
I think it is ready to go, although it probably needs a round or two of
testing to make sure everything works. Right now, can build either of two
ways, the non-template based version you did (although this version is
probably out of date with respect to the samples) and the template-based
build I w
I've gotten confused on the status of packaging on Windows.
To create the NSIS package are we using CPack, going to use CPack but it
isn't ready yet, or ... ?
Thanks.
--
Mark Miesfeld
--
HPCC Systems Open Source Big Data
