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

Configure Fluidity in a separate build directory #219

Open
espinozahg opened this issue Oct 24, 2018 · 2 comments
Open

Configure Fluidity in a separate build directory #219

espinozahg opened this issue Oct 24, 2018 · 2 comments
Assignees

Comments

@espinozahg
Copy link

I am trying to configure fluidity in a separate build directory using the command:
../fluidity-4.1.15/configure --prefix=/home/username/fluidity-4.1.15 --srcdir=../fluidity-4.1.15 --enable-sam ;
but it cannot find petsc_makefile
I propose to add $srcdir/ to all references of petsc_makefile and petsc_makefile_old in lines 12641 and 12645 of configure file.
Adding that resolves that error but appears another downstream the configure file in line 12814
which can be resolved modifying lines 12646 and 12647 to
CPPFLAGS="$CPPFLAGS $PETSC_INCLUDE_FLAGS -I$srcdir/include/"
FCFLAGS="$FCFLAGS $PETSC_INCLUDE_FLAGS -I$srcdir/include/"
Adding that resolves that error but appears another downstream the configure file in line 14243 which I dont know how to fix.

@stephankramer
Copy link
Contributor

This is something that indeed ought to work, but it doesn't (and probably hasn't since early days). I think your approach is correct but unfortunately there's quite a lot more places this needs to get fixed for this to work.

A while ago I got quite far at fixing this, see #7
I think I was nearly there, but unfortunately didn't have the time to finish it then. If you want to spent some time on this (again I currently don't have the time) you could try to see if you can merge current master easily into this branch. If so (depending on how many things have changed in the mean time, conflicts, etc.) we can probably quite easily resurrect it and finish it off.

Before you go ahead, we should probably first resolve the discussion in #217 though as that may have consequences here.

@tmbgreaves
Copy link
Contributor

Sorry I'm coming to this late - I was working on #217 back in the Autumn then got derailed by a large number of other jobs that soaked up the best part of three months of my time. I'm now back to Fluidity again and will take a look at this. I'll split #217 up into a couple of smaller PRs, as I think sorting out removing supporting software from the build would help with out-of-tree builds and seems to be the more tractable part of the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants