Package Details: openfoam-org 12.20250206-8

Git Clone URL: https://aur.archlinux.org/openfoam.git (read-only, click to copy)
Package Base: openfoam
Description: The open source CFD toolbox (www.openfoam.org)
Upstream URL: http://www.openfoam.org
Licenses: GPL-3.0-or-later
Provides: openfoam
Submitter: None
Maintainer: envolution
Last Packager: envolution
Votes: 66
Popularity: 1.34
First Submitted: 2009-07-02 09:16 (UTC)
Last Updated: 2025-06-11 06:13 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 31 Next › Last »

Shinmen commented on 2025-05-22 19:38 (UTC)

Getting following errro when try to build now, I trying to reinstall paraview and parmetis(Since you update the package) and still getting the error. I trying now installing with qt5-xmlpatterns, maybe a dependency

CMake Error at /opt/paraview/lib/cmake/paraview/ParaViewClient.cmake:577 (message): Cannot find the xmlpatterns executable. Call Stack (most recent call first): /opt/paraview/lib/cmake/paraview/ParaViewPlugin.cmake:1322 (paraview_client_documentation) PVblockMeshReader/CMakeLists.txt:57 (PARAVIEW_ADD_PLUGIN)

envolution commented on 2025-05-22 17:43 (UTC) (edited on 2025-05-22 17:52 (UTC) by envolution)

if you've done building rel5 it's not necessary to build rel6 - it's mostly just fixes for maintaining the PKGBUILD file

@Shinmen thanks - the whole bash call is probably over complicated anyways - I've cleaned up the build process in rel 6 including the jval fix

if you'd like to upgrade from rel5->rel6 and retain rel5 build cache, echo 12.20250206 > <PKGBUILD_PATH>/src/Openfoam-12/.arch_cache then run makepkg

Shinmen commented on 2025-05-22 14:11 (UTC) (edited on 2025-05-22 14:54 (UTC) by Shinmen)

@envolution, jval isn't working correctly on my end, but I managed to fix it by moving it outside of bash -c "". Before, I think it wasn't able to instantiate jval; moving it to the line above solved it.

envolution commented on 2025-05-21 20:50 (UTC)

This release includes some (previously non-compiled) binaries (like setFields mentioned in the comments below) as well as avoiding paraview detection logic problems that was causing some cmake configuration failures.

@Shinmen if you use the MAKEFLAGS='j16' in /etc/makepkg.conf this package will pass it to Allwmake in this new release

Shinmen commented on 2025-05-20 11:09 (UTC)

Thanks, I will wait for the update. I reinstalled OpenFOAM, editing the pkgbuild to run the allwmake with -s -j -q 16, and somehow this makes the setFields appear. I see that in your gist, you implemented this too. I don't check if all the other bins are here too.

envolution commented on 2025-05-19 21:19 (UTC) (edited on 2025-05-19 21:23 (UTC) by envolution)

I'm a bit stuck with (what I think is) a problem on arch upstream paraview - I posted an issue with more details here: https://gitlab.archlinux.org/archlinux/packaging/packages/paraview/-/issues/7

This should explain why this header file is not being found suddenly. I've a few changes to this package (https://gist.github.com/envolution/a8ed98a5fd63dbb7256f618c8e012490) waiting on an update from the paraview maintainers before bumping

envolution commented on 2025-05-19 13:12 (UTC)

@shinmen It's taking a while to diagnose but I think I know why setFields is missing. I should have a fix coming later today when things finish compiling for me to test

Shinmen commented on 2025-05-19 12:48 (UTC)

trying to reinstall also getting following error, the installation continues but it's is show on terminal, I don't know if there's another similar error, I have the vtk installed

vtk/vtkPVblockMeshReader.h:42:10: fatal error: vtkMultiBlockDataSetAlgorithm.h: No such file or directory 42 | #include "vtkMultiBlockDataSetAlgorithm.h"

Shinmen commented on 2025-05-19 11:40 (UTC)

Yes, i using the ofoam alias, and setFields manually in terminal, blockMesh and another commands are okay, also the setFields is not listed in the bin folder

envolution commented on 2025-05-19 04:01 (UTC)

I don't have a lot to go on. Are you using the ofoam alias? is /opt/OpenFOAM/OpenFOAM-12/bin in your $PATH? are you running setFields manually in your terminal?

« First ‹ Previous 1 2 3 4 5 6 7 .. 31 Next › Last »