Dragan Noveski:
You need a compiled JUCE, and libjuce.so maybe in a directory that is
known in /etc/ld.so.conf, so -ljuce finds it.
ok, but how to tell to juce that it builds libjuce.so at all
i am running 'make' in the juce/build/linux successfully, but after
that running updatedb first, and than:
Yes, that part is not documented very well. You need to build juce like
this: "make CONFIG=Release".
nowhiskey@murija2:~/software/nove/mammut/juce/build/linux$ locate
libjuce.so
nowhiskey@murija2:~/software/nove/mammut/juce/build/linux$
so i think .so is not build?
Yes. It doesn't make dynamic libraries, just static ones. So the
file you have build is called libjuce_debug.a . If you set CONFIG=Release,
you will get a file called libjuce.a
also, since there is no 'make install' in juce, i understood you that it
is enough to cp libjuce.so /usr/local/lib ??
Don't bother with that. Just let JUCEPATH in mammut's makefile point to
the directory you unpacked juce into.
hope that i get some help, really interested to get mammut working here!
If everything else fails, you can use Mammut 0.22 instead, which requires
gtk1. Its not that much different.
