Csound Csound-dev Csound-tekno Search About

Re: [Cs-dev] version 5.04 bugs/comments

Date2006-11-23 04:31
FromMichael Gogins
SubjectRe: [Cs-dev] version 5.04 bugs/comments
custom.py contains the variables to be edited as to include file paths, library paths, options for tools, etc.

Command line options to scons determine which targets shall be built.

Regards,
Mike

-----Original Message-----
>From: Mike Coleman 
>Sent: Nov 22, 2006 11:09 PM
>To: csound-devel@lists.sourceforge.net
>Subject: [Cs-dev] version 5.04 bugs/comments
>
>Here are some bugs and other issues I noticed while building version
>5.04 (under Ubuntu Linux):
>
>- In SConstruct, 'withMSVC' is missing parentheses in one place.
>
>- In CsoundVST.cpp, '==' is incorrectly used instead of '=' in two
>places (near csoundGetCurrentThreadId).
>
>- It's not really clear how to configure the scons config variables.
>I admit I haven't read the scons manual, but it'd be nice if this were
>a little more obvious.  I ended up simply editing the code in
>SConstruct, but this is surely the wrong way to do things.  What would
>be nice would be something like the way 'make' works: variables at the
>top of a file that can be edited, and easy override at the
>command-line.
>
>- Also in that file, multi-char constants (e.g., 'cVsT') are being
>used.  These aren't portable and draw a gcc warning.  It would be
>better, for example, to create the string and cast it to the
>appropriate type.
>
>- 'scons -n install' doesn't work.
>
>- It seems like the install target isn't installing _CsoundVST.so.
>Not sure exactly what's going on there.
>
>- Shared libraries should probably be the default under Linux (as
>opposed to static libs).
>
>- PYTHON_DIR is being forced to be a system directory.  It makes
>debugging a lot simpler if *everything* the install target installs
>can be redirected to a custom directory.
>
>- The current .deb file seems to be missing 'csound5gui'.
>
>- Sometimes when I try to exit CsoundVST it gives an error "Csound
>tidy up: Aborted" and doesn't exit (requiring that the program be
>manually killed).  I wonder if this couldn't be changed to go ahead
>and exit in this case.
>
>Keep up the good work!
>Mike
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel




-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net