I believe the instructions said to CWD to the source directory and then issue the command. Yes, I was issuing the cmake from the source directory itself. This is under windows, rather than Unix. I didn't open a git issue because the process quit before it did anything that I could see, so the files that are asked for in the event of a failure didn't yet exist as far as I could tell.
So if you shouldn't issue the cmake from the hyperion source directory itself, does it matter what directory you are in when you issue the command ?
---In hercules-***@yahoogroups.com, <***@...> wrote :
Hi,
I believe this is the result of trying to build Hercules Hyperion in the source directory, which is something that the CMake build for Hyperion does not support. I cannot be sure of this, though, because error messages were not included in the post.
Looking at the web documentation for using CMake to build Hercules on a UNIX-like system (http://hercules-390.github.io/html/CMake/index.html http://hercules-390.github.io/html/CMake/index.html), I see there is no instruction to make the build directory the current working directory. This instruction does exist in the Windows and OS X/macOS web documentation.
From this I surmise that you are trying to build Hercules on a UNIX-like system.
I have updated the CMake web documentation for UNIX-like systems just now.
If the problem persists, please see "What to do When it Fails" at the bottom of the above-referenced page.
Best Regards,
Steve Orso
---In hercules-***@yahoogroups.com, <***@...> wrote :
Downloaded and installed everything as directed from the git Hyperion page. Running the cmake to build the generator produces the error that cmake can't run until the CMakecache.txt file and the CMakefiles/ directory are removed from the source directory. The problem is these two items don't exist until cmake creates them, at which point it complains they are there.
What gives, why is it creating these things and then complaining about their existence ?