<div dir="ltr">Hi,<br><div class="gmail_extra"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div><div>On Sat, Dec 7, 2013 at 8:56 PM, Mirco Wahab<br><<a href="mailto:mirco.wahab@chemie.tu-freiberg.de" target="_blank">mirco.wahab@chemie.tu-freiberg.de</a>> wrote:<br>> the build step creating gmx.exe works fine, but the executeable is created<br>
> in:<br>><br>> [build_dir]/bin/Release/gmx.exe<br>><br>> the next step (the install) expects the executeable<br>> gmx.exe located here:<br>><br>> [build_dir]/bin/gmx.exe<br>><br>
> and fails with:<br>> 28> Creating symlinks for alternative binary names<br>> 28> Error copying file (if different) from "[build_dir]/bin/gmx.exe" to<br>> "[build_dir]/bin/mdrun.exe".<br>
</div></div></blockquote><div> </div><div class="gmail_quote">On Sat, Dec 7, 2013 at 11:38 PM, Szilárd Páll <span dir="ltr"><<a href="mailto:pall.szilard@gmail.com" target="_blank">pall.szilard@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Lesson: we should add the install step to the jenkins builds; added a<br>
Redmine task for this (<a href="http://redmine.gromacs.org/issues/1396" target="_blank">http://redmine.gromacs.org/issues/1396</a>).<br>
<br>
I suggest that you also add a bug with the brief description you provide.</blockquote><div><br></div><div>This is a good idea, but would not have caught this, since this is not an issue that comes up during installation, but during a build. The symlinks are currently required in the build tree so that the user (and Jenkins) can run the regression tests against the build without installing it. <a href="https://gerrit.gromacs.org/#/c/2846/" target="_blank">https://gerrit.gromacs.org/#/c/2846/</a> now removes this, but this is not going to pass Jenkins until the regression tests and/or the way Jenkins runs them is updated.</div>
<div><br></div><div>If we would have wanted to catch this in Jenkins, we should do the build using msbuild/Visual Studio there. Running the regression tests from CMake/CTest may also be problematic in this directory layout, since tests/CMakeLists.txt hardcodes the binary location as ${CMAKE_BINARY_DIR}/bin/.</div>
<div><br></div><div>Teemu</div>
</div></div></div>