Well, as long as there is a standard way to include files and developers are expected to do it one way and not another, and if they have cross-platform projects and the source can be made to expect to work on all platforms without tricky makefile hacking to detect the location of the csound.h file, then I think that would be fine. On the other hand, I think it does go against the convention of /usr/local/include being a standard place for includes that developers place their headers with the path being set correctly, and requiring an extra -I in the compilation flags. It just seems awkward to me, but I have no stake in this really as I'm not planning to do any C/C++ dev work anytime soon that uses the API, so would be fine myself if this is the way we're setting to do it. steven On 12/21/05, Istvan Varga wrote: > On Wednesday 21 December 2005 19:25, Steven Yi wrote: > > > BTW: I was thinking today that it's a bit strange that for frontends > > that are in CS5 CVS, because the H dir is included in the build > > properties, they reference directly the header and not , > > while end users who may build a program on top of CS5 will have to use > > . So the frontends examples don't quite reflect what an > > end user would experience, and the H dir is not set up in a way > > reflective of the installed directory structure. It's really a minor > > issue in the end, but curious nevertheless, and perhaps would require > > a note to developer users who will be using the C/C++ API. > > Including the headers directly like should work too > if the /usr/local/include/csound is added to the include path. > The reason why the headers are installed to a separate directory > is to avoid possible conflicts with other packages (some of the > files have simple names like version.h). > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net