http://permalink.gmane.org/gmane.comp.audio.csound.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.audio.csound.devel/22419 <pre>Hi all, Just FYI, I've just committed some CMake changes so that PUBLIC_HEADER is used when building OSX Framework. I had to move the inclusion of H/CMakeLists.txt higher up in the main Cmake file, so that I could grab the list of headers and add them to the src list as well as use as the PUBLIC_HEADER argument. (Note: It took a while to figure out, but the headers must be part of the src list for PUBLIC_HEADER to work). Now, I think there is a possible way to use just PUBLIC_HEADER and not use the install command for installing these headers. I think if you use PUBLIC_HEADER on non-OSX, those headers get installed into /usr/local/include/csound, but I have not tried it. It's a possible place to improve this, I think. Has anyone experience with this or thoughts on it? Thanks! steven ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT ma</pre> Steven Yi 2012-05-16T15:38:31 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22418 <pre>Ah, okay. I've made the change to Top/getstring.c and po/CMakeLists.txt and pushed it. Thanks! steven On Tue, May 15, 2012 at 3:57 PM, Felipe Sateler &lt;fsateler&lt; at &gt;gmail.com&gt; wrote: ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Csound-devel mailing list Csound-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel </pre> Steven Yi 2012-05-15T20:05:48 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22417 <pre>Okay. Compiler search path and &lt;csound.h&gt; sounds good too. On Tue, May 15, 2012 at 3:54 PM, Felipe Sateler &lt;fsateler&lt; at &gt;gmail.com&gt; wrote: ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Csound-devel mailing list Csound-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel </pre> Steven Yi 2012-05-15T20:01:53 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22416 <pre>I have seen the following pattern which seems to simplify things to me: In /usr/local/include there is a csound dir. In the csound dir there is a versioned csound dir. I.e. we have /usr/local/incude/csound/csound6 and /usr/local/include/csound/csound6 Then to include headers, we can have "#include &lt;csound/csound6/csound.h&gt;" and it just works off /usr/local/include, or we can have "#include &lt;csound.h&gt;" but the build has to be configured to look in /usr/local/csound/csound6. Regards, Mike On Tue, May 15, 2012 at 3:54 PM, Felipe Sateler &lt;fsateler&lt; at &gt;gmail.com&gt; wrote: </pre> Michael Gogins 2012-05-15T20:00:55 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22415 <pre>Line 76 uses dgettext("csound5", s). That csound5 should be changed to csound6 (and the cmakelists updated). I'm not on my own computer now, that's why I don't change it myself. On Tue, May 15, 2012 at 3:49 PM, Steven Yi &lt;stevenyi&lt; at &gt;gmail.com&gt; wrote: </pre> Felipe Sateler 2012-05-15T19:57:52 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22414 <pre>Yes, it makes sense to install by default to csound6 to avoid conflicts with csound5. But I think apps should still just #include &lt;csound.h&gt; and manipulate the compiler search path. On Tue, May 15, 2012 at 3:46 PM, Steven Yi &lt;stevenyi&lt; at &gt;gmail.com&gt; wrote: </pre> Felipe Sateler 2012-05-15T19:54:24 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22413 <pre>I'm not too familiar with all the gettext stuff in Csound. I did see this in Top/getstring.c: /* textdomain("csound5"); */ /* This is not needed when using dgettext */ So, maybe it's not an issue? On Tue, May 15, 2012 at 2:02 PM, Felipe Sateler &lt;fsateler&lt; at &gt;gmail.com&gt; wrote: ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Csound-devel mailing list Csound-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel </pre> Steven Yi 2012-05-15T19:49:34 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22412 <pre>Ah, I see now that you have already coded it to installed to "include/csound" in the H/CMakeLists.txt and main CMakeLists.txt. I'm working on the OSX Framework stuff now and am figuring out best way to handle the headers (on build or on install). Any thoughts on csound vs. csound6 (i.e. /usr/include/csound6)? I'm still thinking we're going to have a transition period where cs5 and cs6 apps are going to both need to be supported for building. Thanks! steven On Tue, May 15, 2012 at 2:07 PM, Felipe Sateler &lt;fsateler&lt; at &gt;gmail.com&gt; wrote: ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Csound-devel mailing list Csound-dev</pre> Steven Yi 2012-05-15T19:46:46 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22411 <pre>FWIW, in debian I install in /usr/include/csound. I believe it is the job of the build tools to find out where things are installed. Therefore, a frontend should add -I/usr/include/csound to the compiler. The install location could probably be retrieved from pkg-config, or manually by the user. Then just #include &lt;csound.h&gt;. By not making any promise about where stuff is installed, there can be any number of parallel installations. On Tue, May 15, 2012 at 1:49 PM, Steven Yi &lt;stevenyi&lt; at &gt;gmail.com&gt; wrote: </pre> Felipe Sateler 2012-05-15T18:07:53 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22410 <pre>But it looks like the textdomain needs to be changed from csound5 to csound6. On Tue, May 15, 2012 at 1:39 PM, Steven Yi &lt;stevenyi&lt; at &gt;gmail.com&gt; wrote: </pre> Felipe Sateler 2012-05-15T18:02:26 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22409 <pre>Hi All, I was thinking we should install headers into "csound" or "csound6" instead of the base install dir for includes. i.e. we'd have /usr/local/include/csound6 and code would have: #include &lt;csound6/csound.h&gt; Another issue though, with OSX frameworks, when you use "-framework CsoundLib64", you're supposed to use &lt;CsoundLib64/csound.h&gt; for the include. I think we usually get around it by including the CsoundLib64.framework/Headers directly onto the include path, which is fine as it gets around the framework design and is a bit more cross-platform. My thought here with adding a csound6/ prefix is that it is a bit tidier when we install as all the headers are grouped together. Also, developers can compile applications to work with both Csound5 and Csound6 installed on the same system if they are separated. (Cs5 could just remain where it currently is in the base include dir). Thoughts? steven ------------------------------------------------------------------------------ Live Security Virtual Confer</pre> Steven Yi 2012-05-15T17:49:45 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22408 <pre>AH, never mind. I realize now the work was already done in the po folder and all much better than what I committed. I'll revert the change I just did now. Thanks and sorry for the noise! steven On Tue, May 15, 2012 at 1:33 PM, Steven Yi &lt;stevenyi&lt; at &gt;gmail.com&gt; wrote: ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Csound-devel mailing list Csound-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel </pre> Steven Yi 2012-05-15T17:39:51 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22407 <pre>Hi All, I've added into the CMake build to run msgfmt with the PO files. I followed along with the Scons build. Currently, they are generating into ${BUILD_DIR}/po. Question: Where should the mo files be installed to? I'd like to make it install to the correct directory when you run "make install". Thanks! steven ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Csound-devel mailing list Csound-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel </pre> Steven Yi 2012-05-15T17:33:42 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22406 <pre>I used to maintain this document in LaTeX format (which is plain text that LaTeX makes into a PDF). I preferred this format because the PDF was more beautiful and easier to read than the present document. The LaTeX was what was checked into the repository, not the PDF, of course. Some people complained because the LaTeX was hard for them to read and they did not want to take the time to install LaTeX and build the PDF, so I converted the document to the what you see is what you get doc format we now have. That way the source is checked in yet anyone with Word, Open Office, Libre Office, or Google Chrome (which is just about everyone as far as I can tell) can read it or print it out. Regards, Mike On Sun, May 13, 2012 at 6:47 PM, Adam Puckett &lt;adotsdothmusic&lt; at &gt;gmail.com&gt; wrote: </pre> Michael Gogins 2012-05-13T23:30:36 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22405 <pre>+1 Why not use plain ASCII in the howto build file btw? On 5/13/12, john ffitch &lt;jpff&lt; at &gt;codemist.co.uk&gt; wrote: ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Csound-devel mailing list Csound-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel </pre> Adam Puckett 2012-05-13T22:47:42 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22404 <pre>Plain ASCII is such a useful and flexible format ==John ffitch ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Csound-devel mailing list Csound-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel </pre> john ffitch 2012-05-13T10:40:22 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22403 <pre>There aren't CR or LF in the file. Yes, I can see it with a browser, convert it with `lynx -dump' but it is difficult to read the source of the html file with emacs without a filter. It is like to write a C program in only one line. I can compile it and run the program but it is difficult to read the source. I read in your msg "Sent using Google Docs http://docs.google.com/" and the first thing that I do is to read the html code. One line html is a bad style. However, Leonardo Da Vinci wrote from right to left and from bottom to top, a kind of cryptography. tito ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Csou</pre> Tito Latini 2012-05-10T20:41:48 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22402 <pre>If you are able to view the HTML I would not consider it a bug. Are you having a problem reading the downloaded HTML in your browser? I found I could open and edit the downloaded HTML in WYSIWYG format in Word 2010 and I think Libre Office could also do it. If you would like another format for commenting or editing or something, let me know and I will send it (PDF, Open Document, etc.). Regards, Mike On Thu, May 10, 2012 at 3:16 PM, Tito Latini &lt;tito.01beta&lt; at &gt;gmail.com&gt; wrote: </pre> Michael Gogins 2012-05-10T19:42:23 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22401 <pre>Coding Standards for Csound.html: wc -l Coding\ Standards\ for\ Csound.html 0 Coding Standards for Csound.html Perhaps there is a bug in Google Docs, the exported html is written in only one line. If it is not a bug, it is securely bad style. Where is the original source code to fix it ? tito ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Csound-devel mailing list Csound-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel </pre> Tito Latini 2012-05-10T19:16:22 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22400 <pre>Attached: Coding Standards for Csound.html Sent using Google Docs http://docs.google.com/ I have updated this as follows: (1) Incorporated most suggestions from comments. (2) Added quite a bit to the Speed rules. More comments are invited. Regards, Mike ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ Csound-devel mailing list Csound-devel&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel </pre> Michael Gogins (Google Docs 2012-05-10T00:58:15 http://permalink.gmane.org/gmane.comp.audio.csound.devel/22399 <pre>The whole point of these coding standards is that a name such as OPARMS should never be used. The meanings of types should be obvious to the uninitiated. Something like "PerformanceParameters" should be enough. (What does "O" mean here, anyway?) If that isn't clear enough, please suggest something that is. The amount of typing involved should not be a factor, although names longer than 31 characters should not be used. One of the basic principles of coding to standards is to define things as little possible. If you don't need to define it, don't define it. If you do need to define it, define it in one and only one place. Therefore, if you can define it just by naming a type, do that. If you have to name a type and then comment it, that's two definitions for the same thing. Invariably, in my experience, and evidently in the experience of the critical systems programmers, some of these multiple definitions drift apart, and then it's just not clear what's really supposed to be happening. This is also the real</pre> Michael Gogins 2012-05-09T19:38:15 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.audio.csound.devel