October 2004 - chuck-dev - lists.cs.princeton.edu

ChucK, Supercollider and current development
by Eric Gilbert 26 Oct '04

26 Oct '04

Hi all, Does ChucK play well with Supercollider? Are there interfaces out that enable the two of them talk? I know that Supercollider can accept OSC. Does ChucK support or have plans to support this feature? Since I'm new to the list (and considering getting involved in the development effort), I would like to know what is currently being worked on in ChucK. Thanks, Eric

2 1

chuck-1.1.5.2 build problems on OSX with FFS root filesystem
by chris turner 17 Oct '04

17 Oct '04

Hello, First let me thank you for this fine software.. I had some build problems on OSX 10.3 based on my choice of root filesystems.. attached is the build output. Initially, I was quite puzzled by this, but then I recalled some discussion I'd had with the fink (http://fink.sourceforge.net/) developers about some build problems for gnome libraries. Basically, it seems as though apples HFS/HFS+ filesystems are case insensitive, allowing a programmer to write things such as "#include <CoreMidi/CoreMidi.h>" instead of "#include <CoreMIDI/CoreMIDI.h>" as the file is actually called. The same is true of the link line e.g. LIBS=-framework CoreAudio -framework CoreMIDI -framework CoreFoundation -lstdc++ -lm Changing these allowed me to build with no problems. Thanks again.. it sounds great!!! looking through the language, I don't see any notation for e.g. synchronization keywords / rhythmic markup. Any plans for that? Thanks, -Chris [chris@eyebook:src]$ uname -a Darwin eyebook.local 7.5.0 Darwin Kernel Version 7.5.0: Thu Aug 5 19:26:16 PDT 2004; root:xnu/xnu-517.7.21.obj~3/RELEASE_PPC Power Macintosh powerpc [chris@eyebook:src]$ make osx make -f makefile.osx bison -dv -b chuck chuck.y gcc -D__MACOSX_CORE__ -O3 -c chuck.tab.c flex -ochuck.yy.c chuck.lex gcc -D__MACOSX_CORE__ -O3 -c chuck.yy.c gcc -D__MACOSX_CORE__ -O3 -c chuck_main.cpp In file included from chuck_bbq.h:65, from chuck_main.cpp:49: midiio_osx.h:37:31: CoreMidi/CoreMidi.h: No such file or directory In file included from chuck_bbq.h:65, from chuck_main.cpp:49: midiio_osx.h:83: error: 'MIDIClientRef' is used as a type, but is not defined as a type. midiio_osx.h:84: error: 'MIDIEndpointRef' is used as a type, but is not defined as a type. midiio_osx.h:85: error: 'MIDIPortRef' is used as a type, but is not defined as a type. midiio_osx.h:111: error: parse error before `*' token midiio_osx.h:118: error: 'MIDIClientRef' is used as a type, but is not defined as a type. midiio_osx.h:119: error: 'MIDIEndpointRef' is used as a type, but is not defined as a type. midiio_osx.h:120: error: 'MIDIPortRef' is used as a type, but is not defined as a type. make[1]: *** [chuck_main.o] Error 1 make: [osx] Error 2 (ignored)

2 1

Developing chuck - from chuck@
by Ge Wang 17 Oct '04

17 Oct '04

Let's figure out how to approach these issues. anyone else have cycles to contribute on these? Best, Ge! ---------- Forwarded message ---------- Date: Sun, 17 Oct 2004 14:21:17 -0400 From: Scott Robert Ladd <coyote(a)coyotegulch.com> Reply-To: Mailing list for programming language 'ChucK' <chuck(a)lists.cs.princeton.edu> To: Mailing list for programming language 'ChucK' <chuck(a)lists.cs.princeton.edu> Subject: [chuck] Developing chuck Hello, I'm playing with chuck 1.1.5.2 on Linux-based Pentium 4 and dual-Opteron systems. First of all, chuck is fascinating and entertaining. Please accept the following comments as an offer of assistance for improving chuck: 1) The current build system is very simple, but also very non-traditional and inflexible for a Unix environment. An autoconf build might be more effective, along the lines of ../configure --sound=alsa --prefix=/usr/local/bin make make install 2) Chuck is sometimes balky (e.g., it can't find the sound card) on my Pentium 4, but it works fine most of the time. On my AMD64, I get the same segmentation fault mentioned by Mark Constable. 3) During a build with -Wall -pedantic, I see quite a few warnings, ranging from portability problems to casting problems. Are any of these issues something you are interested in having someone such as myself take a look at? If so, what is the best procedure for providing patches to chuck? Is the developer's mailing list working? I haven't seen any messages therein. -- Scott Robert Ladd site: http://www.coyotegulch.com blog: http://chaoticcoyote.blogspot.com _______________________________________________ chuck mailing list chuck(a)lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck

1 0