You need the "dev" package for each dependency of Csound. "dev" means that 
you get no only any shared libraries, which need to RUN with the third party 
dependency, but you also get the header files, which you need to COMPILE 
software that uses the third party dependency.

Csound unfortunately comes in two versions, one built for 32 bit samples and 
one built for 64 bit samples. Because of this, opcodes for the 32 bit 
version won't work for the 64 bit version. Hence, we have OPCODEDIR which 
points to the directory containing 32 bit opcodes and OPCODEDIR64 which 
points to the directory containing 64 bit opcodes. This enables 2 versions 
of Csound to co-exist on the same computer.

Hope this helps,
Mike
----- Original Message ----- 
From: "menno" 
To: 
Sent: Sunday, February 21, 2010 9:31 AM
Subject: [Csnd] Re: Re: Re: sloppy packaging


>
> Hi
> I am using UbuntuStudio9.10 and do not want to wait passively any longer 
> for
> an Ubuntu Csound package to be updated. I am not a programmer but a user -
> today the sun was shining brightly after 2 months of snow, so i said to
> myself: today is a good day to build Csound myself!
>
> I would like to share my experience in doing so and some questions that go
> along with this experience.
> Now, you will have to know that there is a package in my system
> (python-imaging-tk) and there is a problem with that. And because there is
> an internal problem with that package I can not get rid of it - it refuses
> to get uninstalled even with: sudo apt-get -f install. This is not good
> because now i can not uninstall the old csound. I can install new packages
> but cannot uninstall anything because of this constant error i am getting
> with this python-imaging-tk package. Packages refuse to get uninstalled.
>
> Back to Csound.
> What did i do to get the latest Csound:
> - went to Building Csound page in the manual:
> - installed Scons
> - got the CVS version
> - in the manual there is talk about libdsndfile 1.0.13 or later, but
> Synaptic shows libsndfile, so without the -d.
> Ubuntu has version 1.0.20 so this must be the right one. Installed -dev as
> well
> - i had Python2.6 already installed
> - portaudio19 and -dev are installed
> - portmidi and -dev
> - libfltk1.1 installed but not the -dev because there were a lot of 
> packages
> that has to get installed too. Will FLTK work when the dev file is not
> installed?
> - swig 1.3.36
> - libfluidsynth but not the dev file because of all these packages that 
> come
> along with it. Same question as above.
> - liblo0-dev
> - alsa of course is already installed but installed libasound2-dev too -
> dont know why
> - installed DDSI
>
> I do not understand the part in the manual about OPCODEDIR64
>
> CVS created Csound5 in my HOME.
> then i build Csound with these arguments:
> scons buildDSSI=1 buildImageOpcodes=1 buildJavaWrapper=1
> buildPythonOpcodes=1 buildUtilities=1 buildVirtual=1 Lib64=1 useDouble=1
> useALSA=1 useFLTK=1 usePortAudio=1 useJack=1 usePortMidi=1
>
> and yes - it did build without errors. Great!
> Now i still have the old Csound installed but want to get rid of it. And 
> the
> latest version is in my Home. And i can run it from there.
> What is the convention to get Csound in the right place and not in my 
> home?
>
> thaks,
> Menno
>
>
>
> -- 
> View this message in context: 
> http://old.nabble.com/sloppy-packaging-tp27473586p27676062.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound"
>