Csound Csound-dev Csound-tekno Search About

Re: [Cs-dev] segfault

Date2014-11-04 14:44
FromSteven Yi
SubjectRe: [Cs-dev] segfault
AttachmentsNone  None  
Hi Jim,

I tend to keep a copy of Custom.cmake with paths added there. There's the Custom.cmake.ex that you can copy as Custom.cmake in the csound6 source root you can use as an example, as well as one in csound6/installer/macosx.  In general though, if I build libraries, I install them into /usr/local and as long as the libraries are there, they should get picked up if you have /usr/local/lib and /usr/local/include on your CMAKE_SYSTEM_LIBRARY_PATH and CMAKE_SYSTEM_INCLUDE_PATH.
On Wed Oct 29 2014 at 1:41:43 AM James Hearon <j_hearon@hotmail.com> wrote:
Hi,
re: 6.03.02 sefault
My gdb is not giving much info about this, but I think it may be due to building using a previous CMakeCache.txt file.  I noticed some small differences.

I was using that approach to help recall all my options and some rather convoluted paths to libs etc. too.  Seems recalling using a previous cache file and then tweaking for any new additions which show up may not be best practices.

So what is a good way to keep track of all the options and paths etc. from vers. to vers. for help with building, besides saving the cache file?

Regards,
Jim Hearon


------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel