Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge master into v2.16 #68

Merged
merged 50 commits into from
Sep 13, 2021
Merged

Merge master into v2.16 #68

merged 50 commits into from
Sep 13, 2021

Conversation

KyleDavisSA
Copy link
Contributor

@KyleDavisSA KyleDavisSA commented Sep 12, 2021

This PR merges the current master branch into branch v2.16.

Recently many changes have been made to the master branch, which currently supports CalculiX v2.16. The branch v2.16 must always remain up-to-date with the latest developments for CalculiX v2.16. The latest version of CalculiX is v2.17. Therefore, the master branch should support v2.17. This requires first that the master branch is merged into v2.16 to keep v2.16 adapter up-to-date.

A follow-up PR will be made to merge the new changes into v2.17.

KyleDavisSA and others added 30 commits June 9, 2020 18:21
Update the develop branch
The current default does not work without modifications in any scenario.

This makes it easier to build the adapter in a Debian-based system, after simply getting SPOOLES, ARPACK, and yaml-cpp from APT. For users that have these dependencies elsewhere, they still need to set the dependencies themselves.

Furthermore, it sets the suggested location for CCX and the dependencies to `$(HOME)`, a pattern often observed among new users.

This also splits each dependency to an *_INCLUDE and an *_LIBS part, making it more flexible.
Use develop branch of systemtests
Add -fallow-argument-mismatch to support GCC 10
Update master with improved Makefile and GCC 10 support
Remove -fallow-argument-mismatch (revert #45)
Bugfix: remove -fallow-argument-mismatch from Makefile (add manually for GCC 10)
@KyleDavisSA
Copy link
Contributor Author

I currently use the master branch and it all works as it should for me.

Copy link
Member

@IshaanDesai IshaanDesai left a comment

Choose a reason for hiding this comment

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

Makes sense to keep the v2.16 branch synced with master

Copy link
Member

@MakisH MakisH left a comment

Choose a reason for hiding this comment

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

This works fine for me with CalculiX 2.16. This update is also important so that CalculiX 2.16 can work with our 2D tutorials and so that the building instructions correspond to the documentation.

By the way, since #41 (I guess), I cannot directly build the adapter with CalculiX built from source in its own folder and not installed (my usual development environment). I needed to add:

LIBS = \
	$(SPOOLES_LIBS) \
	$(PKGCONF_LIBS) \
+	-lprecice \
	-lstdc++ \

If more of you have a similar issue, maybe we should add it anyway.

@IshaanDesai
Copy link
Member

@MakisH

If more of you have a similar issue, maybe we should add it anyway.

I dont need to add -lprecice to LIBS for successful compilation. Even if CalculiX is installed from source in its own folder you can just add the CCX path in the Makefile for it to be found right?

@MakisH
Copy link
Member

MakisH commented Sep 13, 2021

I dont need to add -lprecice to LIBS for successful compilation. Even if CalculiX is installed from source in its own folder you can just add the CCX path in the Makefile for it to be found right?

I am talking about preCICE here, not CalculiX. This is just a problem we need to fix in the pkg-config of preCICE, but it is rather complicated. But maybe it only affects me.

@IshaanDesai
Copy link
Member

I am talking about preCICE here, not CalculiX. This is just a problem we need to fix in the pkg-config of preCICE, but it is rather complicated. But maybe it only affects me.

Okay I misunderstood you previously 😅 still if anything needs to be tested before standardizing the Makefile then I can test it.

@KyleDavisSA
Copy link
Contributor Author

But it seems that adding -lprecice solves the problem when preCICE is installed in its own directory? I don't think this impacts merging this PR?

@MakisH
Copy link
Member

MakisH commented Sep 13, 2021

But it seems that adding -lprecice solves the problem when preCICE is installed in its own directory? I don't think this impacts merging this PR?

It does not impact this PR at all. I just noticed it while reviewing this one. I should have asked on Gitter / open an issue.

@KyleDavisSA KyleDavisSA merged commit f472fc7 into v2.16 Sep 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants