3
0
mirror of https://github.com/triqs/dft_tools synced 2024-12-23 04:43:42 +01:00
Go to file
2019-08-27 15:43:37 -04:00
.github/ISSUE_TEMPLATE Add issue templates for bug and feature request 2019-05-22 17:25:28 -04:00
c++/app4triqs [cmake] Use PROJECT_GIT_HASH instead to store git hash and adjust dependent files accordingly 2019-07-16 11:54:32 -04:00
doc [doc] Add cpp2rst and example output generation to doc building 2019-08-27 15:43:37 -04:00
python/app4triqs [cmake] Install all modules by default 2019-08-06 11:14:57 -04:00
share [cmake] Exported targets should live in project namespace 2019-08-06 11:32:06 -04:00
test [cmake] Generate list of all tests through GLOB_RECURSE by default 2019-08-20 14:32:21 -04:00
.clang-format First draft of the triqs application skeleton 2018-03-22 18:16:10 +01:00
.clang-tidy Further cleanining, switching to static library 2018-03-26 00:31:39 +02:00
.dockerignore [jenkins] try to exclude large git packs from build 2019-07-31 12:13:08 -04:00
.travis.yml [travis] Switch to gcc and clang version 8, clean dependency list 2019-07-16 11:29:51 -04:00
ChangeLog.md [doc] Fix few doc problems, add changelog 2018-06-03 22:28:55 -04:00
CMakeLists.txt [cmake] Use PROJECT_GIT_HASH instead to store git hash and adjust dependent files accordingly 2019-07-16 11:54:32 -04:00
COPYING.txt Major cleaning, Synchronize project structure with qmc codes 2019-04-12 16:36:03 -04:00
Dockerfile [jenkins] Make linux builds use requirements.txt 2019-07-31 12:13:28 -04:00
Jenkinsfile [jenkins] Don't trigger PR builds on upstream changes 2019-08-20 16:01:55 -04:00
LICENSE.txt Update License file initially copied from triqs project 2019-04-26 10:00:58 -04:00
README.md Update README file with more detailed instructions 2019-08-27 15:39:03 -04:00
requirements.txt Add requirements.txt for python package dependencies 2019-07-29 14:42:20 -04:00

Build Status

app4triqs

A skeleton for a TRIQS application

Caution: The following instructions require the util-linux rename command. Please confirm that you have the right version by running rename --version. For the Perl rename command see instructions in the following section.

To adapt this skeleton for a new TRIQS application, the following steps are necessary:

github_username=myuser
app_name=mynewapp
capital_name=MYNEWAPP

git clone https://github.com/triqs/app4triqs --branch unstable ${app_name}
cd ${app_name}
git reset $(git commit-tree HEAD\^{tree} -m "Create ${app_name} from github.com/triqs/app4triqs skeleton")
git merge --allow-unrelated-histories -s ours HEAD@{1} -m "Track app4triqs skeleton"
find . -type f | grep -v .git | xargs sed -i 's/app4triqs/${app_name}/g; s/APP4TRIQS/${capital_name}/g'
find . -type d | grep -v .git | xargs rename app4triqs ${app_name}
find . -type f | grep -v .git | xargs rename app4triqs ${app_name}
git add -A && git commit -m "Adjust app4triqs skeleton for ${app_name}"
git remote set-url origin https://github.com/${github_username}/${app_name}
git remote add app4triqs_remote https://github.com/triqs/app4triqs
git remote update && git remote prune origin

You can now push to your github repository

git push origin unstable

Perl rename command

If you are using the Perl-based rename command you will need to

find . -type d | grep -v .git | xargs rename 's/app4triqs/${app_name}/'
find . -type f | grep -v .git | xargs rename 's/app4triqs/${app_name}/'

Github SSH interface

If you prefer to use the SSH interface to the remote repository, replace the http link accordingly

https://github.com/myuser/mynewapp   -->   git@github.com:myuser/mynewapp

Merging app4triqs skeleton updates

You can merge future changes to app4triqs into your project with the following commands

git remote update
git merge app4triqs_remote -m "Merge latest app4triqs skeleton changes"

If you should encounter any conflicts resolve them and git commit.