-
Automated scripts for building gcc 4.4.x and 4.5.x for using with OpenFOAM 1.7 series
Hi MLD,
I suggest that you first try CentFOAM: http://sourceforge.net/apps/mediawik...itle=Main_Page
Best regards and good luck!
BrunoPosted April 13, 2011 at 07:25 by wyldckat -
Automated scripts for building gcc 4.4.x and 4.5.x for using with OpenFOAM 1.7 series
Hi Bruno,
I am trying to install OpenFOAM 1.7.1 on Redhat 5 linux. It has Gcc4.1.x. Would the steps given above of ubuntu linux will work in my case. Are the steps of checking the flex, flex++, FlexLexer.h., libreadline5-dev, texinfo, byacc and bison would be the same as given above. I am a new user of linux and know only basic commands and operations. Could you please help me or please give me the systematic steps to install OF1.7.1 on RHEL5 Linux.
Thanks in advance
MLDPosted April 13, 2011 at 00:33 by run_cfd -
Automated scripts for building gcc 4.4.x and 4.5.x for using with OpenFOAM 1.7 series
Hi Bruno,
I figured it out. All I had to do was to type 'wmake libso' in the src.
Thanks,
NamPosted March 4, 2011 at 02:01 by namCFD -
Automated scripts for building gcc 4.4.x and 4.5.x for using with OpenFOAM 1.7 series
Hello Bruno,
How do you make scotch decomposition method work? The log file indicate that the libscotch.so was not copy to appropriate folder. So I copy them over after finish installation, but metis/scotch still not working. Thank you for your time and help.
Nam
------------------
have OPENMPI shared library
========================================
Build Scotch decomposition library
have scotch shared libraries in scotch_5.1/lib
+ cp scotch_5.1/lib/libscotch.so scotch_5.1/lib/libscotcherrexit.so /home/hnguyen/OpenFOAM/OpenFOAM-1.7.1/lib/linux64GccDPOpt
cp: target `/home/hnguyen/OpenFOAM/OpenFOAM-1.7.1/lib/linux64GccDPOpt' is not a directory
--------------------------------------------Posted March 3, 2011 at 18:46 by namCFD -
Using the official pre-built ParaView 3.8.0 version with OpenFOAM...
paraview cause folders opening problem
Dear Bruno,
Thanks for your comments. now my paraFoam works properly.Posted February 24, 2011 at 04:48 by maysmech
Updated February 24, 2011 at 06:13 by maysmech -
Using the official pre-built ParaView 3.8.0 version with OpenFOAM...
Hi Nam,
Quote:Just a comment, my system (Scientific Linux 5.5 64 bit) this line does not exist: "$WM_PROJECT_DIR/bin/apps/paraview3/bashrc".
Instead, I have "$WM_PROJECT_DIR/etc/apps/paraview3/bashrc". Edited this file as you suggested above and blockMesh works.
Thank you for your post and insight.
I'll fix it right away before I forget to fix it...
And you're welcome
Best regards,
BrunoPosted February 9, 2011 at 19:19 by wyldckat -
Using the official pre-built ParaView 3.8.0 version with OpenFOAM...
Hello Bruno,
Just a comment, my system (Scientific Linux 5.5 64 bit) this line does not exist: "$WM_PROJECT_DIR/bin/apps/paraview3/bashrc".
Instead, I have "$WM_PROJECT_DIR/etc/apps/paraview3/bashrc". Edited this file as you suggested above and blockMesh works.
Thank you for your post and insight.Posted February 9, 2011 at 17:57 by namCFD -
Using the official pre-built ParaView 3.8.0 version with OpenFOAM...
Hi Sahm,
I'm sorry for taking so long to reply to you, but I didn't receive any email from cfd-online server when you posted the comments
OK, first thing, the following command tells you if you have i?86 or x86_64:Code:uname -m
Second thing, the error you got at the end, happened to me today as well - this is why I only saw your comments today!!
The fix is quite simple:
- Make sure that a certain line in "$WM_PROJECT_DIR/bin/apps/paraview3/bashrc" is like this:Code:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ParaView_DIR/lib/paraview-$ParaView_MAJOR
- Make sure which architecture your system is, by running:Code:
uname -m
- Now, edit the file "$HOME/.bashrc" file. Now, this is where things get a bit confusing:
- Search for the first line where you placed something related to OpenFOAM.
- Now, before that first line, put this line before it, depending on your architecture - for i?68:
Code:#For i?68 export LD_LIBRARY_PATH=/lib:/usr/lib:$LD_LIBRARY_PATH
Code:#For x86_64 export LD_LIBRARY_PATH=/lib64:/usr/lib64:$LD_LIBRARY_PATH
- Start a new terminal. If necessary, activate the OpenFOAM environment. And test if all is working!
Best regards,
BrunoPosted January 25, 2011 at 18:49 by wyldckat - Make sure that a certain line in "$WM_PROJECT_DIR/bin/apps/paraview3/bashrc" is like this:
-
Using the official pre-built ParaView 3.8.0 version with OpenFOAM...
Interesting Problem occured:
I did what I've written above, and parafoam works,
but other openfoam programs don't work as I get the following message:
blockMesh: /home/sahm/OpenFOAM/ParaView-3.8.1-Linux-x86_64/lib/paraview-3.8/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /home/sahm/OpenFOAM/OpenFOAM-1.7.0/lib/linux64GccDPOpt/libfiniteVolume.so)
and many other things. any idea for that?Posted January 14, 2011 at 03:07 by sahm -
Using the official pre-built ParaView 3.8.0 version with OpenFOAM...
Hi, I created the following note which is very similar to your notes above. sorry I understood this better
It says the same thing, the only difference is that it is the same for all architectures and linux versions ( not sure about that ). And this installs the paraview in the main OpenFOAM folder, so that it would be the same paraview for all OF versions, if you have several versions (like 1.5 , 1.5.x , 1.6 , 1.7) on your computer simultaneously, you just have to do the step 1 and 2 for each version, after calling that version.
I'm trying to make a shell script to do everything automatically. Should you need the script, don't hesitate to contact.
Thank You Wyldckat for your good note. you can edit your notes and remove mine.
1- Remove The Old ParaView Folder. This folder is usually set with OpenFOAM Installation.
The following file defines every parameter regarding ParaView and ParaFOAM:$WM_PROJECT_DIR/etc/apps/paraview3/bashrc
and this file is sourced from main OpenFOAM bashrc file:
$WM_PROJECT_DIR/etc/bashrc
- Look if Old ParaView Folder exists:Code:
ls $ParaView_DIR
- If it says something like Quote:ls: cannot access /home/..../paraview-3.8.0: No such file or directory
If it doesn't say something like that , then remove the folder:
Code:rm -rf $ParaView_DIR
$WM_PROJECT_DIR/etc/apps/paraview3/bashrc
set the paraview version and folders by finding the similar lines and changing to new version and folders:
ParaView_VERSION=3.8.1
paraviewInstDir=$WM_PROJECT_INST_DIR/ParaView-$ParaView_VERSION-Linux-$KUSU_DIST_ARCH
3- Set the ParaView Reader format inside paraFoam command:
export ParaView_DIR=$WM_PROJECT_INST_DIR/ParaView-$ParaView_VERSION-Linux-$KUSU_DIST_ARCH
Open the file "$WM_PROJECT_DIR/bin/paraFoam" in your favorite simple text editor and replace every entry ".OpenFOAM" with ".foam". Now save and close the file.
The following code does the same thing:
Code:sed -i -e 's=\.OpenFOAM=\.foam=' $WM_PROJECT_DIR/bin/paraFoam
Code:wget http://www.paraview.org/files/v3.8/ParaView-$ParaView_VERSION-Linux-$KUSU_DIST_ARCH.tar.gz tar -xzf ParaView-$ParaView_VERSION-Linux-$KUSU_DIST_ARCH.tar.gz
Code:mv ParaView-$ParaView_VERSION-Linux-$KUSU_DIST_ARCH/ $WM_PROJECT_INST_DIR/
Posted January 14, 2011 at 02:13 by sahm - Look if Old ParaView Folder exists:
-
Building ParaView 3.8.0 with custom Qt 4.6.3
Hi Francois,
Quote:As I said on the Openfoam bug-report website, the compilation of ParaView itself and the reason why the additional PV3FoamReader Modules can only be added to the locally compiled version of ParaView are two things which continue to baffle me no matter how much effort I put in understanding them..
Quote:
Quote:By the way, I also had an other question related to Paraview, albeit slightly off-topic.. A friend of mine was also using paraview, but he had the possibility to export videos directly to avi format within Paraview, without having to use a third party software.. Any tips/ideas on how to get this nifty add-on? (he said he had it from the start, so he didn't know better) I have to export the animations as images, and then make a movie out of them, a process I would like to make more efficient..
Best regards and good luck!
BrunoPosted January 13, 2011 at 18:31 by wyldckat -
Building ParaView 3.8.0 with custom Qt 4.6.3
Dear Bruno,
Thank you for the link, the effort and the good work! It works! (On Archlinux x86_64, for the people interested)
As I said on the Openfoam bug-report website, the compilation of ParaView itself and the reason why the additional PV3FoamReader Modules can only be added to the locally compiled version of ParaView are two things which continue to baffle me no matter how much effort I put in understanding them..
I wish there was an easy way of adding the PV3FoamReader Modules to a repository version of Paraview..
I also tried your forum thread:
"Using the official pre-built ParaView 3.8.0 version with OpenFOAM..." but that didn't work for some reason I didn't understand.
By the way, I also had an other question related to Paraview, albeit slightly off-topic.. A friend of mine was also using paraview, but he had the possibility to export videos directly to avi format within Paraview, without having to use a third party software.. Any tips/ideas on how to get this nifty add-on? (he said he had it from the start, so he didn't know better) I have to export the animations as images, and then make a movie out of them, a process I would like to make more efficient..
Kind regards,
Francois.Posted January 10, 2011 at 09:24 by Fransje -
Using the official pre-built ParaView 3.8.0 version with OpenFOAM...
This helped me a lot, thank you. Replacing .OpenFOAM by .foam got rid of the "assertion 'extent !=0' failed" that I got when running paraFoam from a case dir. Now I believe I can finally run the first tutorial example of OpenFOAM in its full glory. :')Posted December 14, 2010 at 05:55 by Aneirin -
Using the official pre-built ParaView 3.8.0 version with OpenFOAM...
Hi kprzysowagmailcom,
Did you read the point 7Quote:7. Now open the file "$WM_PROJECT_DIR/bin/paraFoam" in your favorite simple text editor and replace every entry ".OpenFOAM" with ".foam". Now save and close the file.Code:gedit $WM_PROJECT_DIR/bin/paraFoam
BrunoPosted October 15, 2010 at 10:57 by wyldckat
Updated October 15, 2010 at 10:58 by wyldckat (added example) -
Using the official pre-built ParaView 3.8.0 version with OpenFOAM...
Thanks!!! Works great. I have saved plenty of time on debugging the compilation.
Do you know how to make OpenFoam reader default? The window on paraView start-up.Posted October 15, 2010 at 10:50 by kprzysowagmailcom -
Using the official pre-built ParaView 3.8.0 version with OpenFOAM...
Thanks!!
You help me a lot.Posted September 5, 2010 at 12:04 by ulisses -
List of threads useful for building OpenFOAM and other Third Party tools
Building ParaView 3.8 in a MacBook OS X 10.6.3
Greetings masuarez,
Unfortunately, Mac OS X is out of my expertise If Apple wasn't so uptight, I could have some experience running it in Virtual Machines, but Macs are as closed as gaming consoles Long Live Linux
Anyway, you might want to head on to the thread for Macs: http://www.cfd-online.com/Forums/ope...7-macos-x.html
Best regards and good luck!
BrunoPosted August 8, 2010 at 10:39 by wyldckat -
List of threads useful for building OpenFOAM and other Third Party tools
Building ParaView 3.8 in a MacBook OS X 10.6.3
I'm installing ParaView 3.8. I already downloaded and installed successfully (I HOPE!!!) QT 4.6. when building ParaView 3.8, i get the following error message:
/usr/local/Trolltech/Qt-4.6.0/include/QtCore/qglobal.h:288:2: error: #error "You are building a 64-bit application, but using a 32-bit version of Qt. Check your build configuration."
I looked in the qglobal.h file (line 288).. but since i have close to no experience with code, i didn't know how to fix it.
I also get the following error, and i don't know if they are related:
/usr/local/Trolltech/Qt-4.6.0/include/QtGui/qregion.h: In member function ‘OpaqueRgnHandle* QRegion::handle(bool) const’:
/usr/local/Trolltech/Qt-4.6.0/include/QtGui/qregion.h:160: error: ‘toQDRgn’ was not declared in this scope
I'm new at the whole compiling/configuring/make install lingo... usually I just double click and wait for programs to install. If you could please help me!!!! Thanks.
correction... i just learned that my macbook is a 64-bit.Posted August 8, 2010 at 00:52 by masuarez
Updated August 8, 2010 at 01:53 by masuarez (wrong information)