Skip to content

Commit

Permalink
Updating version number for point release
Browse files Browse the repository at this point in the history
  • Loading branch information
khuck committed Dec 10, 2024
1 parent 76cecfd commit 68382dc
Show file tree
Hide file tree
Showing 4 changed files with 9 additions and 9 deletions.
2 changes: 1 addition & 1 deletion CMakeLists.txt
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ project (APEX CXX C)
set (APEX_DESCRIPTION "Autonomic Performance Environment for eXascale" CACHE STRING "APEX project description")
set (APEX_VERSION_MAJOR 2 CACHE STRING "APEX Major Version")
set (APEX_VERSION_MINOR 7 CACHE STRING "APEX Minor Version")
set (APEX_VERSION_PATCH 0 CACHE STRING "APEX Patch Version")
set (APEX_VERSION_PATCH 1 CACHE STRING "APEX Patch Version")
set (APEX_HOMEPAGE_URL "http://github.com/UO-OACISS/apex" CACHE STRING "APEX homepage URL")

# cmake_policy(VERSION 3.20.1) - implicitly called by cmake_mimium_required
Expand Down
2 changes: 1 addition & 1 deletion doc/Doxyfile.in
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ PROJECT_NAME = "Autonomic Performance Environment for eXascale (APEX)"
# could be handy for archiving the generated documentation or if some version
# control system is used.

PROJECT_NUMBER = 2.7.0
PROJECT_NUMBER = 2.7.1

# Using the PROJECT_BRIEF tag one can provide an optional one line description
# for a project that appears at the top of each page and should give viewer a
Expand Down
12 changes: 6 additions & 6 deletions doc/webdocs/docs/install.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ APEX is integrated into the [HPX runtime](https://hpx.stellar-group.org), and is
-DHPX_WITH_APEX=TRUE
```

The `-DHPX_WITH_APEX_TAG=develop` can be used to indicate a specific release version of APEX, or to use a specific GitHub branch of APEX. We recommend using the default configured version that comes with HPX (currently `v2.6.5`) or the `develop` branch. Additional CMake flags include:
The `-DHPX_WITH_APEX_TAG=develop` can be used to indicate a specific release version of APEX, or to use a specific GitHub branch of APEX. We recommend using the default configured version that comes with HPX (currently `v2.7.1`) or the `develop` branch. Additional CMake flags include:

* `-DAPEX_WITH_LM_SENSORS=TRUE` to enable [LM sensors](https://hwmon.wiki.kernel.org/lm_sensors) support (assumed to be installed in default system paths)
* `-DAPEX_WITH_PAPI=TRUE` and `-DPAPI_ROOT=...` to enable [PAPI](https://icl.utk.edu/papi/) support
Expand All @@ -23,12 +23,12 @@ The `-DHPX_WITH_APEX_TAG=develop` can be used to indicate a specific release ver

APEX is open source, and available on Github at <http://github.com/UO-OACISS/apex>.

For stability, most users will want to download [the most recent release](https://github.com/UO-OACISS/apex/releases) of APEX (for example, v2.6.5):
For stability, most users will want to download [the most recent release](https://github.com/UO-OACISS/apex/releases) of APEX (for example, v2.7.1):

```bash
wget https://github.com/UO-OACISS/apex/archive/refs/tags/v2.6.5.tar.gz
tar -xvzf v2.6.5.tar.gz
cd apex-2.6.5
wget https://github.com/UO-OACISS/apex/archive/refs/tags/v2.7.1.tar.gz
tar -xvzf v2.7.1.tar.gz
cd apex-2.7.1
```

Other users may want to work with the most recent code available, in which case you can clone the git repo:
Expand Down Expand Up @@ -153,7 +153,7 @@ The process for building APEX is:
2) Enter the repo directory:

```bash
cd apex-2.6.5
cd apex-2.7.1
```

3) configure using CMake:
Expand Down
2 changes: 1 addition & 1 deletion src/apex/CMakeLists_hpx.cmake
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ hpx_info("apex" "Will build APEX")

set (APEX_VERSION_MAJOR 2)
set (APEX_VERSION_MINOR 7)
set (APEX_VERSION_PATCH 0)
set (APEX_VERSION_PATCH 1)

if (NOT APEX_ROOT)
if (EXISTS ${HPX_SOURCE_DIR}/apex)
Expand Down

0 comments on commit 68382dc

Please sign in to comment.