Problem building appleseed (undefined reference to `typeinfo for OSL_v1_9::RendererServices')


#21

What the… Let me check.

Edit: Should be fixed.


#22

Ahhh… our qt4 is built with clang/llvm 3.9, but I’ve built OSL with clang/llvm 3.8


#23

Ok, segfault corrected…

Now I’m getting :
[[email protected] ~]$ appleseed.studio
terminate called after throwing an instance of 'boost::filesystem::filesystem_error’
what(): boost::filesystem::canonical: No such file or directory: "/home/mboisson/.local/easybuild/software/2017/avx2/Compiler/gcc5.4/appleseed/1.8.1-beta/studio/plugins"
Abandon


#24

Nice.

Does a /home/mboisson/.local/easybuild/software/2017/avx2/Compiler/gcc5.4/appleseed/1.8.1-beta/studio/plugins directory exist?


#25

Actually, follow-up question:

Where are you running appleseed.studio from?

Developer builds contain a sandbox/ directory containing a complete deployment of appleseed with all its support files. Binaries are automatically copied to sandbox/bin/ by the build system.

This is where you’re supposed to run appleseed from, if you built it from source. Running appleseed from build/ is unlikely to work, and if it does, it’s by accident.


#26

No, that directory does not exist. Is it supposed to be created by the install procedure ?

Why does it matter where I’m running appleseed from ? I’m doing a central installation, users will run it from wherever they want.


#27

Hi,

are you using make install?

Est.


#28

Yes, running make install


#29

Creating the directory manually after the install allows me to launch it. However, is there an environment variable that we can set which would point somewhere else for each user ?


#30

Ah, glad that you could make it work. We’re investigating the issue, this isn’t normal. Hold on.


#31

We’ve identified a small omission in the installation script: studio/plugins was not deployed by make install. We’ve fixed the issue:

Additionally, the next version of appleseed.studio will no longer crash if the studio/plugins/ directory is missing.

Yes, that would be APPLESEED_STUDIO_PLUGIN_PATH. If defined, the directory it points to will be search for appleseed.studio Python plugins.

Hope this answers your questions. Let us know if we can be of any further assistance!


#32

Thanks, I have all I need now.

Great response time by the way!