chuck _ [building chuck]

Upload: xxxx

Post on 07-Jul-2018

223 views

Category:

Documents


0 download

TRANSCRIPT

  • 8/18/2019 ChucK _ [Building ChucK]

    1/3

    ChucK : Build/Install Instructions

    version: 1.3.x.x (chimera)

    home: http://chuck.cs.princeton.edu/

    Installing the Executable

    If you are using the executable, you only need to put chuck (osx) or chuck.exe (win32) in

    your path...

    In MacOS X: in Terminal, go to the bin/ directory and type:

      %> sudo cp chuck / usr / bi n/  ( ent er your password when prompted)

      %> sudo chmod 755 / usr / bi n/ chuck

    (Now you should be able to run chuck from any directory using Terminal. Skip to step 7 

    below and try it out!)

    On Windows: put bin\chuck.exe in c:\windows\system32\. To run under windows: use

    start->run: cmd (or use cygwin)

    At this point, you should be able to invoke 'chuck' from either Terminal (in OSX) or 'cmd'

    under windowsm, from any directory:

    %> chuck[ chuck] : no i nput f i l es . . . ( t r y - - hel p)

    (this is the correct output, since we didn't specify the files to run)

    Have a question? Post to the mailing lists or email us...

    Graphical editors and environments for chuck coming soon!

    If you are using the executable, you can skip to step 7 below...

    Building ChucK from source

    To build chuck from the source (from scratch):

    Follow instructions for your platform on the download page.

    Note that you can also download the executable for Windows and OS X (10.3 and up -

    10.2 and earlier need build.). If you get the executable, then you can ignore the rest of 

    this page.

    1.

    If you are building in Windows with Visual C++ 6.0, open src/chuck_win32.dsw, choosebuild -> set active config -> release, hit F7 to build.

    Otherwise:

    2.

    cK : [building ChucK] http://chuck.stanford.edu/doc/build/

    3 30-01-2016 12:43

  • 8/18/2019 ChucK _ [Building ChucK]

    2/3

    unzip/tar the source (replace chuck-x.x.x.x.tgz with the actual file name):

    %> t ar xvzf chuck- x. x. x. x. t gz

    3.

    Go to the src/ directory (replace chuck-x.x.x.x with the actual directory name):

    %> cd chuck- x. x. x. x/ sr c/

    4.

    If you type 'make' here, you should get the following message:

    %> make[ chuck bui l d] : pl ease use one of t he f ol l owi ng conf i gur at i ons:  make l i nux- al sa, make l i nux- j ack, make l i nux- oss,  make osx- ppc, make osx- i ntel , make wi n32

    Now, type the command corresponding to your platform...

    for example, for MacOS X (PowerPC):

    %> make osx- ppc

    If all goes well, you should end up with a 'chuck' file in the current directory.

    5.

    If you like to install chuck (cp into /usr/bin by default). if you don't like the destination,

    simply edit the makefile under 'install', or skip this step altogether. (we recommend

    putting it somewhere in your path, it makes on-the-fly programming easier)

    # ( opt i onal : edi t t he makef i l e f i r st )%> make i nst al l

    If you haven't gotten any egregous error messages up to this point, then you should be

    done!

    6.

    For a quick sanity check, execute the following (use './chuck' if chuck is not in your

    path), and see if you get the same output:

    %> chuck[ chuck] : no i nput f i l es . . .

    To test out the audio/vm, go to the examples/ directory and run (assuming 'chuck' is

    in your path). To stop, pressed c t r l - c :

    # ( r un ot f _05. ck - t he . ck i s opt i onal . . . )%> chuck ot f _05. ck

    # ( r un any number of f i l es i n par al l el . . . )%> chuck ot f _01 ot f _06

    # (or . . . )%> chuck ot f _01 ot f _02 ot f _05

    # ( or r un al l whose name st ar t s wi t h ' ot f ' . . . )%> chuck ot f *

    # ( and f i r e up t he mand- o- mat i c, i n st k/ di r ector y. . . )

    7.

    cK : [building ChucK] http://chuck.stanford.edu/doc/build/

    3 30-01-2016 12:43

  • 8/18/2019 ChucK _ [Building ChucK]

    3/3

    %> chuck st k/ mand- o- mat i c. ck

    (if you do get error messages during compilation, or you run into some other problem -

    please let us know and we will do our best to provide support)

    You are ready to ChucK. If this is your first time programming in ChucK, you may want

    to look at the documentation, or take the ChucK Tutorial. ThanK you very much. Go

    forth and ChucK - email us for support or to make a suggestion or to call us idiots.

    8.

    - Ge + Perry

    chuck | soundlab | cs | music | ccrma

    cK : [building ChucK] http://chuck.stanford.edu/doc/build/

    3 30-01-2016 12:43