Keep up-to-date with SMTK name changes.

This should go in simultaneous with SMTK pull request 152 and the matching CMB merge request 21.

Basic content checks passed!

Branch-at: dd5ed7b02b529e7a03b9166aad185e767daaccf1
Acked-by: @kwrobot

@buildbot test

BUILDBOT: Your merge request has been queued for testing. You may view the test results here. Kitware developers may monitor the status of testing here.

Branch-at: dd5ed7b02b529e7a03b9166aad185e767daaccf1

Added 1 new commit:

• c5fd79a0 - The special-case for SMTK on OS X should die!

Basic content checks passed!

Changes since last check: compare

Branch-at: c5fd79a0c79050bc8fae79d0347191479ab01bd1
Acked-by: @kwrobot

BUILDBOT: Your merge request has been queued for testing. You may view the test results here. Kitware developers may monitor the status of testing here.

Branch-at: c5fd79a0c79050bc8fae79d0347191479ab01bd1

I wonder if we shouldn't rely on tags rather than the master branches for the CMB superbuild. There are a lot of balls in the air with all these moving parts… The tags can be pushed synchronously much easier than merge requests.

@ben.boeckel I agree, tags would be better for SMTK. I'll push something else into this MR fixing SMTK.

Added 2 new commits:

• 1f4ca039 - NetCDF tarball has moved.
• 1c7c9b7d - Pull SMTK from release branch.

Basic content checks passed!

Changes since last check: compare

Branch-at: 1c7c9b7dac9a692162b7150d2080aafbc92087b6
Acked-by: @kwrobot

@ben.boeckel SMTK now has a release branch and the CMB superbuild is tied to the head of it. Please review.

BUILDBOT: Your merge request has been queued for testing. You may view the test results here. Kitware developers may monitor the status of testing here.

Branch-at: 1c7c9b7dac9a692162b7150d2080aafbc92087b6

Reassigned to @ben.boeckel

Hmm...why is CMB not finding SMTK?

@ben.boeckel wrote:

Hmm...why is CMB not finding SMTK?

Again, this happens with incremental updates+builds of the superbuild.

From the logs:

Emptying binary directory ...

+2

@dcthomp can you rebase this on current superbuild master please, after that is done feel free to merge

Status changed to closed

Hmm. There's no need to close this MR for a rebase; gitlab will pick up the new revision just fine.