Skip to content

Conversation

@johan-andruejol
Copy link
Contributor

The GenerateCLP_FORWARD_PATHS_BUILD and GenerateCLP_FORWARD_PATHS_INSTALL
variables are used to generate a C++ macro. In d58e664
a bug was introduced when SlicerExecutionModel is built without JSON
support, the macro is generated with an empty line, breaking compilation.

This commit fixes the GenerateCLP_FORWARD_PATHS_[BUILD/INSTALL] variables
to make sure the C++ macro are always valid.

See Issue #81

The GenerateCLP_FORWARD_PATHS_BUILD and GenerateCLP_FORWARD_PATHS_INSTALL
variables are used to generate a C++ macro. In d58e664
a bug was introduced when SlicerExecutionModel is built without JSON
support, the macro is generated with an empty line, breaking compilation.

This commit fixes the GenerateCLP_FORWARD_PATHS_[BUILD/INSTALL] variables
to make sure the C++ macro are always valid.
@zachmullen
Copy link

LGTM

@jcfr
Copy link
Member

jcfr commented Sep 9, 2016

Thanks. 👍

Do you know why the CI didn't catch the problem previously ?

@johan-andruejol
Copy link
Contributor Author

@jcfr: CircleCI actually caught it, but it didn't report it correctly it look like: https://circleci.com/gh/Slicer/SlicerExecutionModel/63
My (totally untested) theory: Unix doesn't need the launcher, so the test could still build/run anyway and passed. CircleCI only reported the testing status and so showed it passing ?

@johan-andruejol johan-andruejol merged commit 983d211 into Slicer:master Sep 9, 2016
@jcfr
Copy link
Member

jcfr commented Sep 9, 2016

Arff. It looks like running ctest -DExperimental .. does not fail in case of build error.

See

ctest -VV -D Experimental || die "ctest failed"

and http://slicer.cdash.org/viewBuildError.php?buildid=881252

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants