Replace ArborX_ENABLE with ARBORX_ENABLE

[Rombur]

@dalg24 saw the light for Kokkos and recognized the superiority of CAPS LOCK. If we merge this PR will need to update spack.

[aprokop]

If we merge this PR will need to update spack.

Fair enough. Should be trivial.

I also wonder why in DTK we already had SET(ARBORX_ENABLE_MPI TRUE). Nevermind, I see from the patch.

[aprokop]

Updating spack is actually a bit non-trivial. We have two versions of arborx there: 0.8-beta, and master. They would need different options. We have two choices:

1. Do if statement in cmake_args to switch between options
   This is ugly. We'll have to do version comparison too.
2. We could do a new release (0.8-beta2?) and replace old release in spack

I would prefer the second option. The changes are not backward compatible, so new version is warranted.

[dalg24]

3rd option. We don’t merge until Kokkos CMake is more stable.

…

On Mon, Sep 16, 2019 at 4:56 PM Andrey Prokopenko ***@***.***> wrote: Updating spack is actually a bit non-trivial. We have two versions of arborx there: 0.8-beta, and master. They would need different options. We have two choices: 1. Do if statement in cmake_args to switch between options This is ugly. We'll have to do version comparison too. 2. We could do a new release (0.8-beta2?) and replace old release in spack I would prefer the second option. The changes are not backward compatible, so new version is warranted. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#99?email_source=notifications&email_token=AACIQEU5SLNWWERVEJDF2WDQJ76KPA5CNFSM4IXD66PKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD62UO7Q#issuecomment-531974014>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACIQETU3ZQR3HRI4L4KQJDQJ76KPANCNFSM4IXD66PA> .

[Rombur]

It's only a beta release, we can replace it.