Osc build tools

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Osc build tools

jhearon

Thanks Davd.

Was there a particular version or something.  As usual I get build errors
for liblo on the make.

$ make
make  all-recursive
make[1]: Entering directory `/c/utah/usr/liblo-0.22'
Making all in src
make[2]: Entering directory `/c/utah/usr/liblo-0.22/src'
if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.
-I..    -Wall -I.. -g -O2 -MT liblo_la-address.lo -MD -MP -MF
".deps/liblo_la-address.Tpo" -c -o liblo_la-address.lo `test -f 'address.c'
|| echo './'`address.c; \
then mv -f ".deps/liblo_la-address.Tpo" ".deps/liblo_la-address.Plo"; else
rm -f ".deps/liblo_la-address.Tpo"; exit 1; fi
gcc -DHAVE_CONFIG_H -I. -I. -I.. -Wall -I.. -g -O2 -MT liblo_la-address.lo
-MD -MP -MF .deps/liblo_la-address.Tpo -c address.c  -DDLL_EXPORT -DPIC -o
.libs/liblo_la-address.o
In file included from address.c:31:
lo_types_internal.h:11:21: pthread.h: No such file or directory
In file included from address.c:31:
lo_types_internal.h:72: parse error before "pthread_t"
lo_types_internal.h:72: warning: no semicolon at end of struct or union
lo_types_internal.h:75: parse error before '}' token
lo_types_internal.h:75: warning: type defaults to `int' in declaration of
`lo_server_thread'
lo_types_internal.h:75: warning: data definition has no type or storage
class
In file included from ../lo/lo.h:32,
from address.c:32:
../lo/lo_lowlevel.h:542: parse error before "st"
In file included from address.c:32:
../lo/lo.h:135: parse error before "lo_server_thread_new"
../lo/lo.h:135: warning: type defaults to `int' in declaration of
`lo_server_thread_new'
../lo/lo.h:135: warning: data definition has no type or storage class
../lo/lo.h:142: parse error before "st"
../lo/lo.h:158: parse error before "st"
../lo/lo.h:169: parse error before "st"
../lo/lo.h:177: parse error before "st"
../lo/lo.h:184: parse error before "st"
../lo/lo.h:189: parse error before "st"
../lo/lo.h:196: parse error before "st"
../lo/lo.h:200: parse error before "st"
make[2]: *** [liblo_la-address.lo] Error 1
make[2]: Leaving directory `/c/utah/usr/liblo-0.22/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/c/utah/usr/liblo-0.22'
make: *** [all] Error 2


--
Send bugs reports to this list.
To unsubscribe, send email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Osc build tools

jpff
You need the pthreads library and header.  I found it easily on the
net.  btw building on Windows is slightly broken, which is why I made
a binary available.
==John ffitch
--
Send bugs reports to this list.
To unsubscribe, send email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Osc build tools

Istvan Varga
[hidden email] wrote:

> You need the pthreads library and header.  I found it easily on the
> net.  btw building on Windows is slightly broken, which is why I made
> a binary available.

Speaking of which, would it be possible to move large binary files
from the CVS sources ? It would be nice to have a collection of
precompiled libraries needed for building Csound (particularly DLLs
for the Win32 platform, for example PortAudio with all interfaces
compiled in), but the csound5 CVS module is not necessarily the best
place for them. This topic was brought up a few times earlier, but
there is still no agreement on where such libraries should be made
available.
--
Send bugs reports to this list.
To unsubscribe, send email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Osc build tools

Michael Gogins
In reply to this post by jhearon
I think it is common practice to create a "file release package" in CVS for
such third party precompiled libraries. This can contain headers, have the
appropriate directory structure to be unzipped over the build directory,
etc.

Regards,
Mike

----- Original Message -----
From: "Istvan Varga" <[hidden email]>
To: <[hidden email]>
Sent: Sunday, October 30, 2005 12:01 PM
Subject: Re: [Csnd] Osc build tools


> [hidden email] wrote:
>
>> You need the pthreads library and header.  I found it easily on the
>> net.  btw building on Windows is slightly broken, which is why I made
>> a binary available.
>
> Speaking of which, would it be possible to move large binary files
> from the CVS sources ? It would be nice to have a collection of
> precompiled libraries needed for building Csound (particularly DLLs
> for the Win32 platform, for example PortAudio with all interfaces
> compiled in), but the csound5 CVS module is not necessarily the best
> place for them. This topic was brought up a few times earlier, but
> there is still no agreement on where such libraries should be made
> available.
> --
> Send bugs reports to this list.
> To unsubscribe, send email to [hidden email]
>



--
Send bugs reports to this list.
To unsubscribe, send email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

csoundapi~ again

Martin Peach
In reply to this post by Istvan Varga
I still think this is a good idea but I'm having a hell of a time
getting it to work :(
I just finished cleaning all the nonfunctional attempts at buiding
csounds 4 and 5 from my WinXP machine.
Now when I run pd_0_39_0test7 and load help-csoundapi~.pd I get:

csoundapi~ 1.0
A PD csound class using the Csound 4.23 API
(c) V Lazzarini, 2005

csapi_demo.csd
csoundapi~ warning: could not compile
help-csoundapi~.pd 5 1 40 1 (adc~->csoundapi~) connection failed
help-csoundapi~.pd 40 3 25 0 (csoundapi~->bng) connection failed
csoundapi~ run: 1

This worked just fine a couple of days ago.

It might be useful if line 170 of the csoundapi_tilde.c were changed from:
else post("csoundapi~ warning: could not compile");
to:
else post("csoundapi~ warning: could not compile: %d", x->result);
to give some indication as to why exactly...

...but I'm guessing that csoundapi~ does _not_ contain the csound engine
and is linking to a libcsound.dll found somewhere else and that I have
erased it. Is this correct?

BTW I still can't get the csound5 version to work. First it can't find
libsndfile and when I copy one in from a precompiled csound5, pd just
crashes.

It would be nice to know how to build a _minimal_ csound for this
purpose, i.e. no FLTK, OSC, etc., but realtime enabled.


Martin



--
Send bugs reports to this list.
To unsubscribe, send email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: csoundapi~ again

Chuckk Hubbard
I had the same issue.  I believe I included the libcsound.dll and the PD patch and the csd file all in the same folder, and then it worked.
I have a hell of a time getting my own csd's to run with it.

On 10/30/05, Martin Peach <[hidden email]> wrote:
I still think this is a good idea but I'm having a hell of a time
getting it to work :(
I just finished cleaning all the nonfunctional attempts at buiding
csounds 4 and 5 from my WinXP machine.
Now when I run pd_0_39_0test7 and load help-csoundapi~.pd I get:

csoundapi~ 1.0
A PD csound class using the Csound 4.23 API
(c) V Lazzarini, 2005

csapi_demo.csd
csoundapi~ warning: could not compile
help-csoundapi~.pd 5 1 40 1 (adc~->csoundapi~) connection failed
help-csoundapi~.pd 40 3 25 0 (csoundapi~->bng) connection failed
csoundapi~ run: 1

This worked just fine a couple of days ago.

It might be useful if line 170 of the csoundapi_tilde.c were changed from:
else post("csoundapi~ warning: could not compile");
to:
else post("csoundapi~ warning: could not compile: %d", x->result);
to give some indication as to why exactly...

...but I'm guessing that csoundapi~ does _not_ contain the csound engine
and is linking to a libcsound.dll found somewhere else and that I have
erased it. Is this correct?

BTW I still can't get the csound5 version to work. First it can't find
libsndfile and when I copy one in from a precompiled csound5, pd just
crashes.

It would be nice to know how to build a _minimal_ csound for this
purpose, i.e. no FLTK, OSC, etc., but realtime enabled.


Martin



--
Send bugs reports to this list.
To unsubscribe, send email to [hidden email]



--
"It is not when truth is dirty, but when it is shallow, that the lover of knowledge is reluctant to step into its waters."
-Friedrich Nietzsche, "Thus Spoke Zarathustra"
Reply | Threaded
Open this post in threaded view
|

Re: csoundapi~ again

Victor Lazzarini
In reply to this post by Martin Peach
The windows libcsound 4 csoundapi~ binary is linked
statically, it contains the csound library OK. The
csound5 also does, if libcsound was built statically.

The reason the precompiled binary (cs5) might not be working
might be that it is built for pd.0.37. Also it is a bit
old and is incompatible with the latest csound5 plugins,
so if you have both old and new installations, it might
be a problem. I'll try to package a csound5 csoundapi~
distribution with instructions in a week's time when
I am back at the office.

Victor

> ..but I'm guessing that csoundapi~ does _not_ contain the
> csound engine  and is linking to a libcsound.dll found
> somewhere else and that I have  erased it. Is this
> correct?
>
--
Send bugs reports to this list.
To unsubscribe, send email to [hidden email]