problem while installing swak4Foam on OF-2.0.1
 

Dear Foamers,

I try to install swak4Foam on OF-2.0.1, but when I run the Makefile I get the following error :

make: ./downloadSimpleFunctionObjects.sh : commande not found

Indeed, the downloadSimpleFunctionObjects.sh script does not exist in my file src/swak4Foam, but it is not present in the downloads I got from svn. At what stage of the installation would possibly lie my mistake? Thank you in advance for your help.

Greetings Laurent,

From which repository did you download swak4Foam? http://openfoamwiki.net/index.php/Co...am#Downloading

Did you use the command:
Best regards,
Bruno

Dear Bruno,

Yes I did. I have made it once again to be sure :
1) downloading with the svn above,
2) 'wmake all' from within the /opt/openfoam201/ directory
3) 'make install' from within the /opt/openfoam201/src/swak4Foam directory
and then the downloadSimpleFunctionObjects.sh is still missing in the /opt/openfoam201/src/swak4Foam directory.

Best regards, and Thank you for your quick help.

Laurent

downloadSimpleFunctionObjects.sh is no longer required (and therefor is no longer in the repository) as the simpleFunctionObjects are now included with swak. Which script is calling it?

The Makefile call this script, at line 23

I run the installation while commenting this line, and then it gave me the following error message (last four lines of a quite long compiling log):

make[1]: *** [Make/linuxGccDPOpt/pythonInterpreterWrapper.o] Erreur 1
make[1]: quittant le répertoire « /opt/openfoam201/src/swak4Foam/Libraries/pythonIntegration »
Requirements for Library not satisfied. I see no sense in going on
make: *** [install] Erreur 42

The recommended way of compiling swak4Foam is "./Allwmake". Installing to global directories can lead to very subtle error conditions (kind of a "DLL-hell". If you don't know what I'm talking about stick with "wmake all"). I will remove this part of the Makefile (and the README). Thanks for drawing my attention to it

Ok ./Allwmake after ./Allwclean works
Thank you for your help, I am now able too enjoy swak4Foam !

Best regards,

Laurent

Great.

On a second thought. Could your previous compilation problems have been caused by you not having write permissions to the global folders? Anyway. In addition to Allwclean try removeSwakFilesFromGlobal.sh from the maintainanceScripts once. Just to be sure that no unwanted residuals lie there from your previous experiments (as you're using a "per user" installation now)

Hello Gerhardt,

Ok, done. Effectively I've been obliged to log as root user to instal swak4Foam ; in order to be able to use swak4Foam from within my regular account as a simple user, I've used successfully copySwakFilesToSite.sh.

Best regards,

Laurent

Hi ,

i'm also having trouble with the swak4Foam installation. it seems that it cudnt find any python.h file, while compiling pythonInterpreterWrapper.C.

could someone pls help me to settle this. i attach part of my log installation file.

thnxomuch!

sori, here's the attachment log file!

another error is while compiling the swakCodedFunctionObject.C !!

thanks!

If you don't need the Python functionality then you can happily forget this problem (although I'm wondering why it tries to compile it because in the distributed sources this is not configured and therefor shouldn't be compiled anyway. Exactly to avoid this kind of question)

Anyway: the location of Python.h depends on your distribution and therefor I can't answer this. If locate is configured then "locate Python.h" might help you. Adapt the swakConfiguration file with the results.
BTW: some toy-distributions (SuSE for instance) don't install the headers with Python. They have them in a special package (python-devel or so)

That is because the codedFunctionObject changed its interface from 2.0 to 2.1. I think I answered this recently somewhere else: remove from Libraries/swakFunctionObjects/Make/files the line with swakCodedFunctionObject.C. You probably won't need it anyway

thanks gscheider!!

that solved the compiling problem for swakFunctionObject!

As for python functionality, i rarely use it, so as u said, i put it aside 1st.

I'm having troubles building swak on OF-2.0.1 as well. It's complaining about missing 'mappedWallFvPatch.H' and related files. Is it possible this was added on by OpenCFD at a later release or is my installation botched? (the file is indeed not to be found in my OF-2.0.1 installation, but is there in OF-2.1)

- Anton

Hi Anton,

I think Bernhard didn't want to waste any more time with such an old version of OpenFOAM ;)

Anyway, I've done some trials+errors+fixes+tests with OpenFOAM 2.0.1, 2.0.x and 2.1.x and the result is in this branch: https://github.com/wyldckat/swak4foam/tree/OF20

The two commits with the necessary changes are here: https://github.com/wyldckat/swak4foam/commits/OF20

I'll open the bug report tomorrow and submit a patch + HG bundle on the bug tracker.

edit: bug report done: http://sourceforge.net/apps/mantisbt...iew.php?id=158

Best regards,
Bruno

Awesome, thanks a ton! I don't quite understand why I got the unmodified version when using 'git clone https://github.com/wyldckat/swak4foam.git', and I had to do 'git checkout ae28e5f76e4c0e8666cf7eb8a35515dba7b4689f' to get the proper version, but now it seems to work (like David, I use google-git...).

By the way, I had a drive-by look at the rest of your repos, and I noticed a typo in the header of interpolateVolumeField.C: I think you intended to write "Interpolate vol*Field to surface*Field".

Ooops, sorry about that... the correct checkout command was:
This way you checkout the branch, instead of a specific commit ;). Although it might not work with older git versions...

I placed it in a separate branch, because that's how I usually use github and its forks: when using a fork, I always make changes in my own branches, to preserve the original branches for reference :)

Many thanks! It's now fixed and I left a breadcrumb in the issue tracker for that project: https://github.com/wyldckat/reconstr...ields/issues/1

Well. It is not the age. It just so happened that I only have projects with versions older and newer than 2.0

I'll put in my repo ASAP (currently I'm a bit handicapped) and push it to the public repo