Skip to content

Commit

Permalink
Add make.inc file for NVHPC (#41)
Browse files Browse the repository at this point in the history
  • Loading branch information
@ImanHosseini
ImanHosseini authored Sep 9, 2023
1 parent 3fef0a3 commit 31173b2
Showing 1 changed file with 16 additions and 0 deletions.
16 changes: 16 additions & 0 deletions make.inc.nvhpc
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
CC=nvc
CXX=nvc++
FC=nvfortran
FFLAGS= -fPIC -O3
LIBS=-lm
CLIBS = -lm -ldl -lifcore

ifeq ($(FAST_KER),ON)

CXXFLAGS = $(FFLAGS)
CXXFLAGS += -std=c++11 -DSCTL_HAVE_SVML -DSCTL_PROFILE=-1
LIBS += -cxxlib
endif

OMPLIBS =
OMPFLAGS = -mp

2 comments on commit 31173b2

@lu1and10
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator register subdir=julia

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/98072

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a julia-v1.0.1 -m "<description of version>" 31173b219a6f3a730f1454e7edfaeeb47f4d675c
git push origin julia-v1.0.1

Also, note the warning: This looks like a new registration that registers version 1.0.1.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

Please sign in to comment.