Build & run from qtCreator :

cannot run from qtCreator with error message

error while loading shared libraries: cannot open shared object file: No such file or directory

it’s been working but I can’t remember when the error been occurred.

environment :

arch linux
OF 0.11.2
qtCreator v4.6.2

fmod shouldn’t be enabled by default on linux.

Are you trying to enable the ofFmodSoundPlayer or is this happening with the examples too?

no. I don’t.
I’ve tested two linux machine. one is new linux setup done fresh.

Could you try changes these lines in ofConstants.h and see if which warning you get when you compile?

//------------------------------------------------ soundplayer
// check if any soundplayer api is defined from the compiler
  #ifdef TARGET_OF_IOS
  #elif defined(TARGET_LINUX) || defined(TARGET_MINGW)
  #elif defined(TARGET_EMSCRIPTEN)
  #elif !defined(TARGET_ANDROID) && (!defined(USE_FMOD) || USE_FMOD)
	#pragma message("WARNING: AUTO SELECTING FMOD")

#pragma message("WARNING: USING FMOD")

#pragma message("WARNING: USING OPENAL")

I think OPENAL selected.

btw, if I compile and run by make, make RunRelease, I don’t have issue. it only happen run from qtCreator

In file included from /home/icq4ever/oF/addons/ofxGui/src/ofxBaseGui.h:3,
                 from /home/icq4ever/oF/addons/ofxGui/src/ofxGuiGroup.h:2,
                 from /home/icq4ever/oF/addons/ofxGui/src/ofxGuiGroup.cpp:1:
/home/icq4ever/oF/libs/openFrameworks/utils/ofConstants.h:383:50: note: ‘#pragma message: WARNING: AUTO SELECTING OPENAL’
  383 |  #pragma message("WARNING: AUTO SELECTING OPENAL")
      |                                                  ^
/home/icq4ever/oF/libs/openFrameworks/utils/ofConstants.h:397:40: note: ‘#pragma message: WARNING: USING OPENAL’
  397 | #pragma message("WARNING: USING OPENAL")

Ah okay - that makes more sense.
It must be something in the switch from libfmodex to libfmod with the QtCreator files.

Not really an ideal fix but you could try adding a line for fmod here:

This would disable linking fmod on linux.

Another fix would be to rename in libs/fmod/lib/linux64/ to and make a symlink to it named

If that second approach works for you we can fix this in the next release.

hmm… second approach I tried. but nothing changed.

is this right?

icq4ever@p340:~/oF(master⚡) » cd libs/fmod/lib/linux64 
icq4ever@p340:~/oF/libs/fmod/lib/linux64(master⚡) » ls
icq4ever@p340:~/oF/libs/fmod/lib/linux64(master⚡) » mv
icq4ever@p340:~/oF/libs/fmod/lib/linux64(master⚡) » ln -s ~/oF/libs/fmod/lib/linux64/
icq4ever@p340:~/oF/libs/fmod/lib/linux64(master⚡) » ls -al
total 1604
drwxr-xr-x 2 icq4ever icq4ever    4096  4월  9 02:40 .
drwxr-xr-x 3 icq4ever icq4ever    4096  1월  3 09:25 ..
-rwxr-xr-x 1 icq4ever icq4ever     212  1월  3 09:25
lrwxrwxrwx 1 icq4ever icq4ever      13  4월  9 02:40 ->
-rwxr-xr-x 1 icq4ever icq4ever 1627616  1월  3 09:25

Hmm - yeah I think that is what I was hoping would work. :slight_smile:
I wonder if you have to copy both to the bin/ folder where your executable lives?

btw I think the ln command should be:
ln -s

I’ll see if I can recreate the issue on Ubuntu. I think it is an issue I am seeing on other forums with the latest fmod.

1 Like

I copied, generate symlink in bin folder. but not resolved.