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

miniaudicle patch to conpile on recent linux
by Ricardo Fabbri 20 Oct '11

20 Oct '11

Hi, I wrote a patch to get miniaudicle svn to compile on some recent linux setups. I can now compile miniaudicle on Ubuntu 11.10. I tested it with Gcc 4.6.1 wxwidgets 2.8 chuck from svn The patch has further comments. I hope it is useful to you and not just a bunch of hacks. Let me know if you want me to break it apart into even smaller patches. I feel like sometimes it can be a hassle to receive tiny patches one after the other. The way I've done it I guess you can reasonably cherry-pick what will make into the official repo. PS: this patch is dedicated to mighty greenkobold, it's his birthday today!!! Fabbri

2 3

small patch
by Ricardo Fabbri 19 Oct '11

19 Oct '11

Hi, all, I would like to propose a small patch to chuck, which is just better error handling for write() system calls in util_hid.cpp. I tried to use the EM_log functions instead of fprintf(stder,....). I hope to have used them correctly. I hope to be producing more significant contributions in the near future. Meanwhile, I thought I shouldn't let these little patches accumulate. The attached patch is agains the latest SVN as of this date, and I tested it with gcc 4.6.1 from Ubuntu 11.10 Best regards, Fabbri

1 0

Resignation and transition
by Adam Tindale 02 Jun '11

02 Jun '11

Hi All, I would like to send my official resignation as a core member of the documentation team. I no longer use ChucK to the extent that I am an expert and I have not committed to the documentation in at least a year. I want to see the community flourish, as I see on the list, and as such I am serving as a gatekeeper to updating and improving the manual. Last year we tried a documentation push that had some interesting developments and I think was ultimately a failure because we did not push enough traffic there. Their export to PDF was ( and in my opinion still is) inadequate for generating a manual that can be shipped with ChucK. My suggestion moving forward is to move to Markdown or asciidoc for generating files that can be easily turned into html or pdf with appropriate style files for each. Github has proved to be an excellent place for collaborating on these types of projects and I would suggest that as a place to get the migrating going. I would be more than happy to help with the migration to a new platform or to help a new person get up to speed on how I generated the PDF manual so they can continue to update it with all of the great discoveries and suggestions on the list. I would also be happy to do some actual porting work of the documentation to a new system that can be more easily maintained if that is what is deemed necessary by the community or new point person. For history, the original manual was generated by me with help from Ge and Phil sometime in 2005 or so. I got into ChucK very seriously at that point and emailed the list or Ge personally to figure out how to do certain things in the language. For every email Ge sent me I created a tutorial or reference and compiled it into a document. Ge, Phil, and I spent many a night generating web references, then I would port that to LaTeX for the PDF manual. Since that time many other people have contributed references that have since been included in the manual and it has grown to the document we know today. It was a lot of fun and I think it had a significant impact on getting new users into ChucK. I want to thank the ChucK team and community, and I look forward to helping you get to the next place. Adam (--art)

1 0

Chuck Dynamic Linking?
by mike clemow 06 Dec '10

06 Dec '10

Dear Dev'rs: >From the documentation here: http://chuck.cs.princeton.edu/doc/program/stdlib.html "ChucK Standard Libraries API these libraries are provide by default with ChucK - ****new ones can also be imported with ChucK dynamic linking (soon to be documented...).***" (emphasis mine) Does "soon to be documented" mean that the functionality already exists in the current version or in CVS or at all? And the obvious follow up: If it's in the current version or CVS, can we have a hint? Is there a secret Chuck pre-processor? Cheers, Mike -- http://michaelclemow.com http://semiotech.org

1 0

Chuck on beagleboard
by Edgar Berdahl 06 Aug '10

06 Aug '10

Hi, I just started trying to compile chuck for the beagleboard. However, I get the following error message. Has anyone seen this before? root@beagleboard:~/chuck-1.2.1.3/src# make linux-alsa make -f makefile.alsa make[1]: Entering directory `/home/root/chuck-1.2.1.3/src' bison -dv -b chuck chuck.y make[1]: *** [chuck.tab.c] Broken pipe make[1]: Leaving directory `/home/root/chuck-1.2.1.3/src' make: [linux-alsa] Error 2 (ignored) BTW I've already gotten the libsndfile-dev package installed as well as packages for alsa, jack, gcc, lex, yacc, make, etc. Thanks, Ed

1 0

compiling with gcc -Wparentheses
by Steve M. Robbins 30 Dec '09

30 Dec '09

Hi, This list doesn't show much traffic lately ... is it still active? I'd like to play around with chuck on my amd64 linux machine. The download page warned me that chuck isn't 64-bit clean at present and indeed, it coredumps. :-( I'd like to help make it 64-bit clean. As a first step, I'm trying to make it compile cleanly with "gcc -Wall". As a first pass to /that/, I looked at warnings generated by -Wparentheses. Below is my patch to avoid these warnings. Incidently: is this the right place to send patches? I'm working off the 1.2.1.3 sources. I'd prefer to work off the development stream if I could; is there any public access to it? Thanks, -Steve

1 2

Sporking til you drop (wake time is past, wake_time < (now_system - .5) )
by Andrew C. Smith 25 Oct '09

25 Oct '09

I've discovered a slightly strange bug, or possibly my computer is just running out of resources. I got chuck working as a dynamic library in an external program, and have circles orbiting around other circles sending the areas of all possible triangles made from the orbit points to global buses. Basically, this requires an update every frame tick, at 30::ms (arbitrary, judged by what frame rate looks adequate on most video games) and then one of my chuck files interpolates between the points at a control rate. I've gotten it down to where I just append "Bus.setChan(x, y); \n" to the end of a string (I use a method "setChan" so that it can broadcast an event to waiting shreds, rather than just having the receiving shreds update constantly) then right at the end of every frame tick (assuming that my string has contents) I spork the shred. This means that only ONE shred is sporked every tick, no matter the number of buses or global variables I've changed. The problem is that I consistently get this message: internal sanity check failed in shredule() / (wake time is past) - x : y (where x and y are numbers referring to time passed in the VM, I believe). I checked it out, and x is SET to y just two function calls earlier, with nothing much happening in between. It calls

1 1

Re: [chuck-dev] Fwd: Oh no, I fixed it: log level bug.
by Spencer D Salazar 25 Oct '09

25 Oct '09

Hi Andrew, Thanks for your feedback and looking in to this. - The "crazy" log level worked at some point -- that it crashes now is most definitely a regression. - The Xcode project file is provided for developer (in)convenience, but hasn't been kept up to date lately. The official method to compile miniAudicle on Mac OS X is the makefile ('make osx' or 'make osx-ub' for a Universal Binary). I'll take a look at fixing the Xcode project file in the way you've described, though. - In the 0.2.0 release, miniAudicle has been updated with the intent of full Snow Leopard compatibility. Please let us know if any other potential problems in this area arise. spencer ----- "Andrew C. Smith" <acsmith(a)willamette.edu> wrote: > The first part, about it not compiling unless > "-D__ALTER_ENTRY_POINT__ > is added to the tag still stands. However, the other one, about the > mini hanging does not. > > So, here's the issue: > > I had "Default Log Level" under Preferences -> Miscellaneous set to > "10", which crashes it. It's like someone set the log level name to > "Crazy" as a kind of decoy... > > (either way, maybe this option should just be disabled. I know it's > supposed to have spectacular crashes, but this seems a bit > overboard.) > > Andrew > _______________________________________________ > chuck-dev mailing list > chuck-dev(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev

6 11

for loop, empty conditional statement, possible fix
by Szilveszter Tóth 24 Oct '09

24 Oct '09

Hello All, I found that the following code crashes ChucK: 0 => int i; for (; ; ) { <<<i>>>; if (i == 100) { break; } i++; } If I put a "true" keyword in the second part of the statement, it works. 0 => int i; for (; true; ) { <<<i>>>; if (i == 100) { break; } i++; } I also checked out the source code and made a change which made this loop work: at chuck_dev\v2\chuck_type.cpp:873: I enclosed the switch() block in a conditional: if (stmt->c2) { ... } Now it seems to work. Regards, Szilveszter aka Hillaby

3 8

Re: [chuck-dev] Compiling under FreeBSD
by benny 22 Oct '09

22 Oct '09

Ok Raimundo, thank you for your feedback. You motivated me to try to patch chuck-1.2.1.3. And while it took a bit of time, I finally got it to compile :) Be aware that near to nothing from the util_hid.cpp file will work (mouse-support, keyboard, joystick etc) Please try it out on Freebsd 8 (I have tried 7.2 only) and see if it works for you (didn't check FileIO). BTW: I am running on 32bit and you? Please keep in mind, that I did this only by accident and have almost no clue of the consequences of my changes except that the hid methods are simply disabled in order to compile. So the procedure is now: wget http://chuck.cs.princeton.edu/release/files/chuck-1.2.1.3.tgz gtar -xzf chuck-1.2.1.3.tgz wget http://stridor.net/upload/chuck-1.2.1.3.freebsd.patch cd chuck-1.2.1.3 && patch -d src -u -p1 < ../chuck-1.2.1.3.freebsd.patch cd src && gmake freebsd # you might omit this step and copy the chuck file somewhere else gmake install Best Regards, Benny > Hey, Benny!!! > > Many Many Thanks > To Benny > Who Make The Patch! > > :) > > It compiled well under fbsd8.0rc1 in the chuck 1.2.1.2, but the .ck > scripts I have to run use FileIO like a class, and, as I got it, this > feature exists only from 1.2.1.3. =/ > >> I got chuck-1.2.1.2 (the cli program) working for FreeBSD 7.2 by >> disabling >> the gui stuff and some other changes. >> > Nice to know it. >> You can do the following to check it out: >> >> >> wget http://stridor.net/upload/chuck-1.2.1.2.tgz >> gtar -xzf chuck-1.2.1.2.tgz >> cd chuck-1.2.1.2 && wget http://stridor.net/upload/freebsd.patch >> patch -d src -u -p1 < freebsd.patch >> cd src && gmake freebsd >> # and as root (copies the binary to /usr/bin) >> gmake install >> > I prefer not to put things system-wide, when I can. I have put it in > ~/bin :D >> It should work - at least on FreeBSD 7.2 >> Perhaps someone (you?) could review the patch and put it upstream / >> integrate it with chuck-1.2.1.3 >> > Hey, it is a big adventure for me!!! I will try for some weeks. How I > have said: I am not so practice on hacking and programming SO > especific things. But in the BSD way, I think it could be easy. >> I am not really familiar with C nor make, just did a bit trial and >> error >> (mixing of the MacOSX and linux-oss options) that happened to work. >> >> You need libsndfile on FreeBSD >> Hope that helps. >> >> Perhaps you want to make a regular port of it? > > Not yet, I am rawraw-boy... ;) > The best for us all, > raitech

2 1