Been fighting with this for far too long. The version on deken had issues with the newer version of a library I have on my computer, so I built it from scratch, which was not much fun since openframeworks has essentially no build instructions for linux, just scripts for a few major distros and Ofelia has minimal build instructions which seem to be out of date and required a fair amount of guess work to get to build. But I got everything installed and the result is that none of the [ofelia] objects load but the [ofXxx] objects do.
This is exactly what I get from the deken version but no more errors about not finding the library because of being a newer version (think it was libglew but I don't remember. and I get a fair amount of errors in the console which I did not get from the deken version.

load_object: Symbol "ofelia_setup" not found
 ofelia d $0-of
... couldn't create
load_object: Symbol "ofelia_setup" not found
 ofelia d $0-of
... couldn't create
load_object: Symbol "ofelia_setup" not found
 ofelia d $0-of
... couldn't create
load_object: Symbol "ofelia_setup" not found
 ofelia f ;
 ofDrawCircle(200 , 200 , 100) ;
... couldn't create

I think Ofelia did create a window once, but it did not draw anything in it. I have searched and searched for a solution or even a hint of the issue, but to no avail.

Edit: same issue on pd 52.1 and 51.4

@oid there are currently some issues with Ofelia and PD 0.52.x: https://github.com/cuinjune/Ofelia/issues/65
Not sure, if that is related. I still use 0.51.x for Ofelia.

I saw that but there was no mention of linux issues or my issue, so figured it was a different problem. Suppose I may as well roll back to 0.51 and see what happens.

Going back to 51.4 did nothing, exact same issues.

@oid btw: I also had issues with pd 0.52.x and Ubuntu: https://github.com/cuinjune/Ofelia/issues/66

@oid said:

But I got everything installed and the result is that none of the [ofelia] objects load but the [ofXxx] objects do.

If the [ofelia] object cannot load, then nothing will work, as all ofelia object are abstractions build with [ofelia].

Edit: running pd 52.1

ofelia window creation have issues with the new pd-52, the author is working on it so better use pd-51-4 now since it should run well on all systems (I use it on MacOS, Linux and Windows now).

@60hz Yeah, i rolled back to 51.4 at @jona suggestion, same problem. It is not working enough to even trigger the 52.1 bug. Updated OP to reflect this.

OK, some progress, it does still throw the error for libglew, but now it only does it if I add ofelia to startup. So this seems to be a bug in the code, it looks for libglew 2.1 and will not accept any other version but will compile with other versions.

@oid I guess you already run this script before compiling the external?
https://github.com/cuinjune/Ofelia/tree/master/scripts/Linux64
And https://github.com/openframeworks/openFrameworks/tree/master/scripts/linux/ubuntu (depending on the linux distro)...

@Jona No, I manually updated the paths which the script updates because I had been dealing with terrible readme's and build instructions all night by the time i got to ofelia and it seems my reading comprehension was seriously degraded by then. Script also seems to add some files to OF, so it might solve the problem, but the deken install having the same issue leaves me doubtful. Thanks for pointing out the obvious, it is often exactly what I need.

The second script is the cause of all my frustration that night, OF's build instructions are just a few scripts for major distros which leave anyone using other distros in the dark, I had to sift through all the scripts and find what packages I was missing, so lots of failed build attempts on OF and a few fun diversions into problems building those dependencies by the time I got to ofelia. 99% certain I got all those, OF did build error free.

Some progress, maybe. I edited the Ofelia makefiles to use the system libraries for runtime paths instead of the OF libs, same problem. This suggests that the two libraries which the Ofelia makefiles explicitly links to the OF libs in the makefiles (kiss and tess2) are the culprit, they are trying to find the libraries they were compiled against. But this raises the question as to why it is a problem for me and not for everyone using archlinux, which uses the same versions or newer of the libraries as I have. So I will try replacing them with my own versions in a few days when I have time to fight with this again. Unless someone else has a bright idea.