Csound Csound-dev Csound-tekno Search About

[Csnd] Re: Re: Re: Re: Re: FLTK Opcodes not found

Date2008-02-12 06:43
FromLuís Antunes Pena
Subject[Csnd] Re: Re: Re: Re: Re: FLTK Opcodes not found
 yes, I've tried re-installing
- luis
victor schrieb:
> In OSX you do not normally need to set OPCODEDIR,
> because it defaults to the right place. I find it
strange, because
> I don't remember anyone with this problem using
> the installer.
>
> libfltk.dylib is there, so you should not have a
problem
> with it missing. I can only think there is an error
with
> the loading with libwigets.dylib. Did you try
re-installing?
>
> Victor
>
>
> ----- Original Message ----- From: "Luís Antunes
Pena" 
> To: 
> Sent: Monday, February 11, 2008 10:15 PM
> Subject: [Csnd] Re: Re: Re: FLTK Opcodes not found
>
>
>> Thanks Victor and Anthony for the answers.
>> I'm running Mac OSX 10.4.11 (Intel) and installed
>> Csound5.07-OSX10.4-Intel.
>> csound -z lists  opcodes like eqfil, granule and
all
>> the opcodes you've written.
>> Listing the /usr/local/lib/ I get this:
>> ao                              libmad.dylib
>> jack                            libmad.la
>> lib_csnd.dylib                 
libmp3lame.0.0.0.dylib
>> libao.2.1.2.dylib               libmp3lame.0.dylib
>> libao.2.dylib                   libmp3lame.a
>> libao.dylib                     libmp3lame.dylib
>> libao.la                        libmp3lame.la
>> libcsnd.dylib                   libogg.0.5.0.dylib
>> libfltk.1.1.dylib               libogg.0.dylib
>> libfltk.dylib                   libogg.a
>> libfltk_forms.1.1.dylib         libogg.dylib
>> libfltk_forms.dylib             libogg.la
>> libfltk_gl.1.1.dylib
>> libportaudio.0.0.19.dylib
>> libfltk_gl.dylib                libportaudio.dylib
>> libfltk_images.1.1.dylib        libportmidi.dylib
>> libfltk_images.dylib
>> libsndfile.1.0.17.dylib
>> libfluidsynth.1.1.1.dylib       libsndfile.1.dylib
>> libfluidsynth.1.dylib           libsndfile.dylib
>> libfluidsynth.dylib            
libvorbis.0.3.0.dylib
>> libfluidsynth.la                libvorbis.0.dylib
>> libid3tag.0.3.0.dylib           libvorbis.a
>> libid3tag.0.dylib               libvorbis.dylib
>> libid3tag.a                     libvorbis.la
>> libid3tag.dylib
>> libvorbisenc.2.0.0.dylib
>> libid3tag.la                   
libvorbisenc.2.dylib
>> libjack.0.0.23.dylib            libvorbisenc.a
>> libjack.0.dylib                 libvorbisenc.dylib
>> libjack.dylib                   libvorbisenc.la
>> liblo.0.6.0.dylib
>> libvorbisfile.3.1.0.dylib
>> liblo.0.dylib                  
libvorbisfile.3.dylib
>> liblo.dylib                     libvorbisfile.a
>> liblo.la                        libvorbisfile.dylib
>> libmad.0.2.1.dylib              libvorbisfile.la
>> libmad.0.dylib                  pkgconfig
>> libmad.a                        tclcsound.dylib
>>
>> Is there anything missing here? The strange thing
is
>> that it used to work and I never needed to set the
>> OPCODEDIR variable. In OSX where should the
variable
>> point to when I make the standard installation with
>> the Csound5.07-OSX10.4-Intel. package?
>>
>> I also found the libwidgets.dylib here:
>>
/Library/Frameworks/CsoundLib.framework/Versions/5.1/Resources/Opcodes
>>
>> -Luis
>>
>>
>>
>> Anthony Kozar schrieb:
>>> It would help to know what platform you are
running
>> on and whether this is a
>>> new installation or a different computer than you
>> used before or is it an
>>> existing installation that used to work.  Also,
>> which Csound package did you
>>> install or did you build from sources?
>>>
>>> Usually this sort of problem is a result of the
>> OPCODEDIR environment
>>> variable not being set correctly.  But from the
>> output messages, it appears
>>> that the portmidi and portaudio plugins are being
>> found so this explanation
>>> seems less likely.  Can you confirm that the other
>> opcode libraries are
>>> being loaded by typing "csound -z" at the
>> commandline.  This lists all
>>> available opcodes and should include (for example)
>> eqfil, granule, max, min,
>>> pan2, partikkel, etc. if the other plugins are
>> loading correctly.
>>>
>>> Also, when you say that you found the
fltk-libraries
>> in /usr/local/lib/, do
>>> you mean the Csound fltk opcode library?  I am
>> assuming not, since it would
>>> usually be somewhere else (possibly
>> /usr/local/lib/csound/).  I think that
>>> the Csound FLTK opcode library is usually called
>> something like
>>> libwidgets.so (on Linux) or libwidgets.dylib
(MacOS
>> X).  Can you find a file
>>> with this name?
>>>
>>> Anthony Kozar
>>> mailing-lists-1001 AT anthonykozar DOT net
>>> http://anthonykozar.net/
>>>
>>> Luís Antunes Pena wrote on 2/11/08 10:42 AM:
>>>> how exactly links csound to the fltk-opcodes? I
>> found
>>>> the fltk-libraries in /usr/local/lib/. It seams
to
>> be
>>>> OK, but stil csound does not found the
FL-Opcodes.
>>>> Any idea what can be wrong?
>>>> Thanks for any help.
>>>> Luis
>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk
>> with body "unsubscribe csound"
>>
>>
>> -- 
>>
>>
>


-- 

l u i s   a n t u n e s   p e n a
http://icem.folkwang-hochschule.de/~pena
http://www.myspace.com/kaurimusik



       __________________________________  Ihre erste Baustelle? Wissenswertes für Bastler und Hobby Handwerker. www.yahoo.de/clever