Package Details: openframeworks 0.11.0-1

Git Clone URL: (read-only, click to copy)
Package Base: openframeworks
Description: An open source C++ toolkit for creative coding.
Upstream URL:
Keywords: coding creative dev graphics toolkit
Licenses: MIT
Submitter: marcs
Maintainer: marcs
Last Packager: marcs
Votes: 15
Popularity: 0.36
First Submitted: 2015-09-27 13:41
Last Updated: 2020-01-01 12:57

Latest Comments

1 2 3 4 Next › Last »

kflak commented on 2020-02-08 15:37

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/ *** 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/ 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 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.

marcs commented on 2020-01-02 12:43

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.

damir commented on 2020-01-01 13:29

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

s-ol commented on 2019-12-19 00:09

arch openAL is too new for last openframeworks release, see here:

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;

brandflake11 commented on 2019-11-21 16:13

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?

madc commented on 2019-08-13 18:56

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/

dum commented on 2019-08-06 15:46

Version 0.10.1 needs glfw in order to build, it should be added as a dependency.

yair commented on 2019-02-16 23:12

thanks @madprog, same issue with YAY and same solution

uncomment the BUILDDIR and assign it to a non dot directory.

madprog commented on 2019-01-12 11:12

The Makefiles provided by OpenFrameworks are filtering out any path or file that is under a directory whose name starts with a dot (.). Some package managers are building the packages under such a directory. For example, pikaur is building under ~/.cache/pikaur/build/openframeworks. When the Makefiles look for source files, all the files are filtered out because the path matches that exclusion. What happens in @nakednous case is that the projectGenerator is linked from the libraries only, hence the missing «main» symbol. For the same reason, the generated libopenFrameworks.a is empty. However the build doesn't fail because this is allowed for a library.

A workaround would be to build the package in a separate folder. For example, pikaur supports setting the BUILDDIR configuration option in /etc/makepkg.conf to something like '/tmp/makepkg':

In order to complete the compilation, I have also had to add these dependencies: 'pugixml' 'glfw-x11'

nakednous commented on 2019-01-03 15:38

Hi, thanks for the package. I got this error when building it as of today: /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../lib/Scrt1.o:init.c:función _start: error: referencia sin definir al «main»