Arch Linux User Repository

I know @damir, for some reason it's a path problem with aur-helpers, it seems that if the helper saves the package in a hidden folder then the Makefile fails.

For example yay saves this package in $HOME/.cache/yay/openframeworks (which is awful IMO) and start building it. If you move the package folder to a non hidden folder (like your $HOME folder for example) then the build works.

It's a bug with OpenFrameworks, hopefully will be resolved.

For now clone this package and build it with makepkg.

--- Build fails with PAMAC, this is an issue with the GUI package manager

The makepkg defaults seem wrong:

from PKGBUILD

build() { cd ${srcdir}/${_name}

cd libs/openFrameworksCompiled/project

msg2 "Building openFrameworks Debug version" make -j$cores Debug

msg2 "Building openFrameworks Release version" make -j$cores_JOBS Release

cd ${srcdir}/${_name}

msg2 "Building OF Project Generator tool..." cd apps/projectGenerator/commandLine make -j$cores Release

cd ${srcdir}/${_name}

msg2 "Building OF Project Generator interface..." cd libs/openFrameworksCompiled/project make -j$cores Release }

setting jobs/threads (-j) to cores i.e. 4 in my case kills the OS/computer. I spent 2 hours repeatedly trying to build this, only for my computer to freeze become unresponsive. When I turned jobs (-j) down to 2 the build took less than 10 minutes and didn't crash my computer.

https://wiki.archlinux.org/index.php/Makepkg#Parallel_compilation

Some PKGBUILDs specifically override this with -j1, because of race conditions in certain versions or simply because it is not supported in the first place. Packages that fail to build because of this should be reported on the bug tracker (or in the case of AUR packages, to the package maintainer) after making sure that the error is indeed being caused by your MAKEFLAGS.

Lastly, more of a warning to others who may wish to try this package: The basic example with no user code, and the gui plugin alone compiles on QtCreator to generate a 54Mb executable (WTF indeed).

Patch added to build.

To fix compilation with make 4.3, there's commit https://github.com/openframeworks/openFrameworks/pull/6564/commits/cc8a44a3a26d8356dfd869f9328a01646668d2ca

Here's a gist: https://gist.github.com/mrshpot/7e10e213b394ee547c821a0e97a2c048

Save the first part as "make_fix.patch" next to the PKGBUILD, and apply changes from the second part to your PKGBUILD.

Am I the only one getting this error:

Compiling projectGenerator for Release
make[1]: Entering directory '/home/kf/build/openframeworks/src/of_v0.11.0_linux64gcc6_release/apps/projectGenerator/commandLine'
/home/kf/build/openframeworks/src/of_v0.11.0_linux64gcc6_release/libs/openFrameworksCompiled/project/makefileCommon/config.addons.mk:210: *** missing separator.  Stop.
make[1]: Leaving directory '/home/kf/build/openframeworks/src/of_v0.11.0_linux64gcc6_release/apps/projectGenerator/commandLine'
make: *** [/home/kf/build/openframeworks/src/of_v0.11.0_linux64gcc6_release/libs/openFrameworksCompiled/project/makefileCommon/compile.project.mk:129: Release] Error 2

I had the same problem with the nightly build as well as the 0.11.0. All of a sudden, out of the blue, any addon with addon_config.mk in it fails to build. They worked fine two days ago.

EDIT: The (temporary) solution is to downgrade make to 4.2.1. Now everything compiles again.

I know @damir, for some reason it's a path problem with aur-helpers, it seems that if the helper saves the package in a hidden folder then the Makefile fails.

For example yay saves this package in $HOME/.cache/yay/openframeworks (which is awful IMO) and start building it. If you move the package folder to a non hidden folder (like your $HOME folder for example) then the build works.

It's a bug with OpenFrameworks, hopefully will be resolved.

For now clone this package and build it with makepkg.

openframeworks 0.11.0-1 fails compiling with

Compiling projectGenerator for Release
make[1]: Entering directory '/home/damir/.cache/yay/openframeworks/src/of_v0.11.0_linux64gcc6_release/apps/projectGenerator/commandLine'
Linking bin/projectGenerator for linux64
g++ -o bin/projectGenerator     /home/damir/.cache/yay/openframeworks/src/of_v0.11.0_linux64gcc6_release/libs/openFrameworksCompiled/lib/linux64/libopenFrameworks.a   -Wl,-rpath=./libs:./bin/libs -Wl,--as-needed -Wl,--gc-sections -fuse-ld=gold -lPocoNetSSL -lPocoNet -lPocoCrypto -lPocoUtil -lPocoXML -lPocoFoundation -lcrypto -lssl    -lgstapp-1.0 -lgstvideo-1.0 -lgstbase-1.0 -lgstreamer-1.0 -ludev -lfontconfig -lfreetype -lsndfile -lopenal -lcurl -lglfw -lrtaudio -ljack -lpulse-simple -lpulse -pthread -lasound -lGLEW -lGLU -lGL -lgtk-3 -lgdk-3 -lz -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lmpg123  -lglut -lX11 -lXrandr -lXxf86vm -lXi -lXcursor -ldl -lpthread -lfreeimage -lboost_filesystem -lboost_system -lpugixml -luriparser -lXinerama
/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../lib/Scrt1.o:init.c:function _start: error: undefined reference to 'main'
collect2: error: ld returned 1 exit status

Scrt1.o comes from glibc:

$ pacman -Qo /usr/lib/Scrt1.o
/usr/lib/Scrt1.o is owned by glibc 2.30-3

arch openAL is too new for last openframeworks release, see here: https://forum.openframeworks.cc/t/compilation-failing-due-to-confliting-definition-in-openal/33927/2

here's the patch that is required to get it to build:

--- libs/openFrameworks/sound/ofOpenALSoundPlayer.back  2019-12-18 17:55:57.441746039 +0100
+++ libs/openFrameworks/sound/ofOpenALSoundPlayer.h 2019-12-18 18:01:11.838392042 +0100
@@ -10,9 +10,9 @@

 typedef unsigned int ALuint;
 /** Opaque device handle */
-typedef struct ALCdevice_struct ALCdevice;
+struct ALCdevice;
 /** Opaque context handle */
-typedef struct ALCcontext_struct ALCcontext;
+struct ALCcontext;

Even with installing pugixml flfw and building in the /tmp/yay directory, I still get this error: Compiling /tmp/yay/openframeworks/src/of_v0.10.1_linux64gcc6_release/libs/openFrameworks/graphics/ofGraphics.cpp g++: fatal error: Killed signal terminated program cc1plus compilation terminated.

This stops the build from happening.

Any suggestions on how to get this to build?

Another missing dependency seems to be pugixml.

Also, using YAY it is possible to change the builddir on the fly like: yay -S openframeworks --builddir=/tmp/yay/