I don't think using the aclient is the better way to make it work on
Debian. This client was build very tight to save cpu cycles on the
XO. The better way is to use the Python API for Csound... (with the
API, don't forget to remove -n flag (no sound) in tamtamorc.csd).
Maybe James can tell
. Examining the csd
tamtam generated might give us a clue.
Victor
- Original Message -
From: Jani Monoses [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, April 19, 2008 3:10 PM
Subject: Re: TamTam packaging
New packages have made into debian testing. You might want to try
those
-why are the cpp sources in the MANIFEST and consequently in the xo?
At the beginning we TamTam was only one activity with a welcome
screen to choose which component to play with. When we were aksed to
spilt the activities it was the simplest way for us to manage all
activities from
Le 08-04-17 à 02:49, Jani Monoses a écrit :
-why are the cpp sources in the MANIFEST and consequently in the xo?
At the beginning we TamTam was only one activity with a welcome
screen to choose which component to play with. When we were aksed to
spilt the activities it was the simplest way
Hi Jani,
On Wed, Apr 16, 2008 at 6:44 PM, Jani Monoses [EMAIL PROTECTED] wrote:
The lib is acsound64 not acsound in debian/ubuntu so the link flag
needed a change to rebuild the aclient.so instead of using the one in git.
the lib will have a 64 if csound was built for double (64 bits)
Hi Andres,
the lib will have a 64 if csound was built for double (64 bits)
precision. Since the OLPC uses the float build it uses a different
file (this setup allows a system to have both floats and doubles
version of csound without conflicts).
Changing the makefile to link agains
Hi Jani,
On Thu, Apr 17, 2008 at 9:43 AM, Jani Monoses [EMAIL PROTECTED] wrote:
Changing the makefile to link agains libcsound64.so made it build so
that is fine. Are there runtime incompatibilities I should be aware of
and which could make it not run on debian?
No incompatbilites as long
Hi Olivier,
I have a few questions regarding the .deb packaging of the four TamTam
activities.
-why are the cpp sources in the MANIFEST and consequently in the xo?
-which versions do you recommend for packaging. Latest are 48 and 49 ,
depending on the activity
I got them to build and start on
Hi Jani,
First of all, our main goal is to make TamTam runs on the XO. We
didn't think yet about porting it to others system...
Le 08-04-16 à 17:44, Jani Monoses a écrit :
Hi Olivier,
I have a few questions regarding the .deb packaging of the four TamTam
activities.
-why are the cpp
