Btw, I couldn't ever get CMAKE_SYSYEM_INCLUDE to work. The only fail
safe way I've managed to find of setting paths is by:
set(CMAKE_C_FLAGS "-I../path/to/include/")



On 29 October 2014 17:37, Steven Yi  wrote:
> Awesome! Glad that's sorted.
>
>
> On Wed Oct 29 2014 at 1:25:50 PM Rory Walsh  wrote:
>>
>> Ah, yes, I see. Argghh!! Looks like this was the problem all along. I
>> saw the include files in the FL folder and assumed that it was the
>> include directory. It's seen by cmake. I'll try building now.
>>
>> On 29 October 2014 17:15, Steven Yi  wrote:
>> > Aren't the headers for including FLTK done like #include  ? If
>> > so,
>> > then your include path is off:
>> >
>> >  list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>> >         "C:/Users/rory/Documents/sourcecode/fltk-1.3.2")
>> >
>> > Otherwise, if you built FLTK while in an msys shell, you could try just
>> > doing "make install" and seeing if CMake then finds it.  If it doesn't,
>> > you
>> > could check if C:/MinGW/msys/1.0/lib and C:/MinGW/msys/1.0/include are
>> > on
>> > your paths too.
>> >
>> > On Wed Oct 29 2014 at 12:53:33 PM Rory Walsh  wrote:
>> >>
>> >> I tried the following in Custom.cmake.ex without any success:
>> >>
>> >> if(WIN32)
>> >>     list(APPEND CMAKE_SYSTEM_LIBRARY_PATH
>> >>         "C:/Users/rory/Documents/sourcecode/fltk-1.3.2/lib")
>> >>     list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>> >>         "C:/Users/rory/Documents/sourcecode/fltk-1.3.2/FL")
>> >> endif()
>> >>
>> >> I still have no idea what the fltk-config script is?
>> >>
>> >> On 29 October 2014 16:13, Michael Gogins 
>> >> wrote:
>> >> > Thanks, the "list (...)" was the missing bit of information.
>> >> >
>> >> > Best,
>> >> > Mike
>> >> >
>> >> > On Oct 29, 2014 11:46 AM, "Steven Yi"  wrote:
>> >> >>
>> >> >> Well, what I pasted earlier shows how it works:
>> >> >>
>> >> >> if(WIN32)
>> >> >>
>> >> >>     list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>> >> >>
>> >> >>             "c:/work/libsndfile-1_0_17")
>> >> >>
>> >> >>     list(APPEND CMAKE_SYSTEM_LIBRARY_PATH
>> >> >>
>> >> >>             "c:/work/libsndfile-1_0_17")
>> >> >>
>> >> >>
>> >> >>     list(APPEND CMAKE_SYSTEM_LIBRARY_PATH
>> >> >>
>> >> >>         "c:/Python25/libs")
>> >> >>
>> >> >>     list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>> >> >>
>> >> >>         "c:/Python25/include")
>> >> >>
>> >> >>
>> >> >> endif()
>> >> >>
>> >> >>
>> >> >> That appends values to CMAKE_SYSTEM_INCLUDE_PATH and
>> >> >> CMAKE_SYSTEM_LIBRARY_PATH, using standard Cmake list command.  You
>> >> >> can
>> >> >> add
>> >> >> something like:
>> >> >>
>> >> >>
>> >> >>     list(APPEND CMAKE_SYSTEM_LIBRARY_PATH
>> >> >>
>> >> >>         "c:/some/fltk/directory/lib")
>> >> >>
>> >> >>     list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>> >> >>
>> >> >>         "c:/some/fltk/directory/include")
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Wed Oct 29 2014 at 11:32:16 AM Michael Gogins
>> >> >>  wrote:
>> >> >>>
>> >> >>> "any normal CMake command in there gets run". Can you give me an
>> >> >>> example?
>> >> >>> E.g. for configuring FLTK in a non-standard location? The example
>> >> >>> doesn't
>> >> >>> have to actually work, just indicate how to specify the commands.
>> >> >>>
>> >> >>> Best,
>> >> >>> Mike
>> >> >>>
>> >> >>>
>> >> >>> -----------------------------------------------------
>> >> >>> Michael Gogins
>> >> >>> Irreducible Productions
>> >> >>> http://michaelgogins.tumblr.com
>> >> >>> Michael dot Gogins at gmail dot com
>> >> >>>
>> >> >>> On Wed, Oct 29, 2014 at 11:18 AM, Steven Yi 
>> >> >>> wrote:
>> >> >>>>
>> >> >>>> Custom.cmake gets include()'d near the top of the main
>> >> >>>> CMakeLists.txt.
>> >> >>>> It functions like the old custom.py in the CS5 Scons build.  Since
>> >> >>>> it's just
>> >> >>>> an include, any normal CMake command in there gets run.  This
>> >> >>>> allows
>> >> >>>> flexibility to customize paths in a repeatable way.  (I sometimes
>> >> >>>> do
>> >> >>>> a
>> >> >>>> separate build in a separate folder with a different branch, so
>> >> >>>> I'll
>> >> >>>> copy
>> >> >>>> the Custom.cmake I use from one folder to another).
>> >> >>>>
>> >> >>>> On Wed Oct 29 2014 at 10:28:02 AM Michael Gogins
>> >> >>>>  wrote:
>> >> >>>>>
>> >> >>>>> The use of Custom.cmake is never explained, therefore I have not
>> >> >>>>> been
>> >> >>>>> able to use it.
>> >> >>>>>
>> >> >>>>> An example of Custom.cmake or explanation of how to use it would
>> >> >>>>> be
>> >> >>>>> much appreciated.
>> >> >>>>>
>> >> >>>>> As you suggest, I have increasingly relied on installing to
>> >> >>>>> /usr/local.
>> >> >>>>> But there is not always a working install target or script on
>> >> >>>>> Windows, so
>> >> >>>>> this is a bit flaky.
>> >> >>>>>
>> >> >>>>> Regards,
>> >> >>>>> Mike
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> -----------------------------------------------------
>> >> >>>>> Michael Gogins
>> >> >>>>> Irreducible Productions
>> >> >>>>> http://michaelgogins.tumblr.com
>> >> >>>>> Michael dot Gogins at gmail dot com
>> >> >>>>>
>> >> >>>>> On Wed, Oct 29, 2014 at 10:23 AM, Steven Yi 
>> >> >>>>> wrote:
>> >> >>>>>>
>> >> >>>>>> For libraries and headers, I think it's preferable to install
>> >> >>>>>> them
>> >> >>>>>> into a location that CMake will find it, rather than setting
>> >> >>>>>> them
>> >> >>>>>> yourself
>> >> >>>>>> in the cache. Normally that means installing the library after
>> >> >>>>>> building to
>> >> >>>>>> /usr/local. However, you can add additional paths for CMake to
>> >> >>>>>> search.  If
>> >> >>>>>> you look at the Cusom.cmake.ex file, you'll see things like:
>> >> >>>>>>
>> >> >>>>>> if(WIN32)
>> >> >>>>>>
>> >> >>>>>>     list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>> >> >>>>>>
>> >> >>>>>>             "c:/work/libsndfile-1_0_17")
>> >> >>>>>>
>> >> >>>>>>     list(APPEND CMAKE_SYSTEM_LIBRARY_PATH
>> >> >>>>>>
>> >> >>>>>>             "c:/work/libsndfile-1_0_17")
>> >> >>>>>>
>> >> >>>>>>
>> >> >>>>>>     list(APPEND CMAKE_SYSTEM_LIBRARY_PATH
>> >> >>>>>>
>> >> >>>>>>         "c:/Python25/libs")
>> >> >>>>>>
>> >> >>>>>>     list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>> >> >>>>>>
>> >> >>>>>>         "c:/Python25/include")
>> >> >>>>>>
>> >> >>>>>>
>> >> >>>>>> endif()
>> >> >>>>>>
>> >> >>>>>> If you copy that to Custom.cmake, then you can add your own
>> >> >>>>>> paths.
>> >> >>>>>> So
>> >> >>>>>> a couple of options here:
>> >> >>>>>>
>> >> >>>>>> 1. You can still try doing a "make install".  That probably only
>> >> >>>>>> works
>> >> >>>>>> if you're within an msys shell. (I'm not certain what the
>> >> >>>>>> convention is for
>> >> >>>>>> the standard cmd prompt if you use MinGW's make.)
>> >> >>>>>>
>> >> >>>>>> 2. You can create a folder where you'll manually add all of your
>> >> >>>>>> libs
>> >> >>>>>> and headers.  Then you can add that folder to your paths. This
>> >> >>>>>> is
>> >> >>>>>> handy if
>> >> >>>>>> you want to isolate the dependencies you build from the rest of
>> >> >>>>>> your system.
>> >> >>>>>> For the mingw cross-compile scripts for compiling the windows
>> >> >>>>>> binaries from
>> >> >>>>>> Linux, that was the approach I took with the dependency builder
>> >> >>>>>> scripts.
>> >> >>>>>>
>> >> >>>>>> 3. You can individually add each folder of each dependency you
>> >> >>>>>> build
>> >> >>>>>> to the CMake paths.
>> >> >>>>>>
>> >> >>>>>> Hope that helps!
>> >> >>>>>>
>> >> >>>>>> steven
>> >> >>>>>>
>> >> >>>>>>
>> >> >>>>>> On Wed Oct 29 2014 at 10:16:26 AM Rory Walsh 
>> >> >>>>>> wrote:
>> >> >>>>>>>
>> >> >>>>>>> Yes, my point is I have no idea what else I need to tell cmake
>> >> >>>>>>> so
>> >> >>>>>>> that
>> >> >>>>>>> it finds it. I've added valid paths to all the fltk stuff.
>> >> >>>>>>> Anyhow,
>> >> >>>>>>> your cmake cache should help sort it out.
>> >> >>>>>>>
>> >> >>>>>>> On 29 October 2014 14:10, Michael Gogins
>> >> >>>>>>> 
>> >> >>>>>>> wrote:
>> >> >>>>>>> > It returns false because FLTK is not found. We just tell
>> >> >>>>>>> > CMake
>> >> >>>>>>> > where it is.
>> >> >>>>>>> > Not the same thing.
>> >> >>>>>>> >
>> >> >>>>>>> > Regards,
>> >> >>>>>>> > Mike
>> >> >>>>>>> >
>> >> >>>>>>> >
>> >> >>>>>>> > -----------------------------------------------------
>> >> >>>>>>> > Michael Gogins
>> >> >>>>>>> > Irreducible Productions
>> >> >>>>>>> > http://michaelgogins.tumblr.com
>> >> >>>>>>> > Michael dot Gogins at gmail dot com
>> >> >>>>>>> >
>> >> >>>>>>> > On Wed, Oct 29, 2014 at 9:58 AM, Rory Walsh
>> >> >>>>>>> > 
>> >> >>>>>>> > wrote:
>> >> >>>>>>> >>
>> >> >>>>>>> >> Thanks Mike, that would help. I'm just curious as to why
>> >> >>>>>>> >> FLTK_FOUND
>> >> >>>>>>> >> keeps returning false.
>> >> >>>>>>> >>
>> >> >>>>>>> >> On 29 October 2014 13:54, Michael Gogins
>> >> >>>>>>> >>  wrote:
>> >> >>>>>>> >> > OK, sorry about that. I just kept looking at the CMake
>> >> >>>>>>> >> > error
>> >> >>>>>>> >> > messages
>> >> >>>>>>> >> > and
>> >> >>>>>>> >> > filling in missing variables. If you like, when I get home
>> >> >>>>>>> >> > this
>> >> >>>>>>> >> > evening
>> >> >>>>>>> >> > I
>> >> >>>>>>> >> > will send you my CMake cache.
>> >> >>>>>>> >> >
>> >> >>>>>>> >> > Regards,
>> >> >>>>>>> >> > Mike
>> >> >>>>>>> >> >
>> >> >>>>>>> >> >
>> >> >>>>>>> >> > -----------------------------------------------------
>> >> >>>>>>> >> > Michael Gogins
>> >> >>>>>>> >> > Irreducible Productions
>> >> >>>>>>> >> > http://michaelgogins.tumblr.com
>> >> >>>>>>> >> > Michael dot Gogins at gmail dot com
>> >> >>>>>>> >> >
>> >> >>>>>>> >> > On Wed, Oct 29, 2014 at 8:41 AM, Rory Walsh
>> >> >>>>>>> >> > 
>> >> >>>>>>> >> > wrote:
>> >> >>>>>>> >> >>
>> >> >>>>>>> >> >> Yup. I don't see anything in there relating to how to set
>> >> >>>>>>> >> >> up
>> >> >>>>>>> >> >> cmake so
>> >> >>>>>>> >> >> that it sees fltk?
>> >> >>>>>>> >> >>
>> >> >>>>>>> >> >> On 29 October 2014 12:34, Michael Gogins
>> >> >>>>>>> >> >> 
>> >> >>>>>>> >> >> wrote:
>> >> >>>>>>> >> >> > Did you read my "how to build on Windows" document?
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> > Regards,
>> >> >>>>>>> >> >> > Mike
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> > -----------------------------------------------------
>> >> >>>>>>> >> >> > Michael Gogins
>> >> >>>>>>> >> >> > Irreducible Productions
>> >> >>>>>>> >> >> > http://michaelgogins.tumblr.com
>> >> >>>>>>> >> >> > Michael dot Gogins at gmail dot com
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> > On Wed, Oct 29, 2014 at 8:18 AM, Rory Walsh
>> >> >>>>>>> >> >> >  wrote:
>> >> >>>>>>> >> >> >>
>> >> >>>>>>> >> >> >> I'm having a go at a full Windows build at the moment,
>> >> >>>>>>> >> >> >> but
>> >> >>>>>>> >> >> >> once
>> >> >>>>>>> >> >> >> again
>> >> >>>>>>> >> >> >> have come up a cropper with fltk. It builds fine for
>> >> >>>>>>> >> >> >> me,
>> >> >>>>>>> >> >> >> but
>> >> >>>>>>> >> >> >> I can't
>> >> >>>>>>> >> >> >> get cmake to see it. Can anyone confirm what values I
>> >> >>>>>>> >> >> >> should
>> >> >>>>>>> >> >> >> have
>> >> >>>>>>> >> >> >> for
>> >> >>>>>>> >> >> >> these entries to CMake:
>> >> >>>>>>> >> >> >>
>> >> >>>>>>> >> >> >> FLTK_INCLUDE_DIR= ..........this is the FL directory
>> >> >>>>>>> >> >> >> contained in
>> >> >>>>>>> >> >> >> the
>> >> >>>>>>> >> >> >> main fltk dir?
>> >> >>>>>>> >> >> >> FLTK_DIR=.........the main fltk directory?
>> >> >>>>>>> >> >> >> FLTK_BASE_LIBRARY=.......lib/libfltk.a?
>> >> >>>>>>> >> >> >> FLTK_CONFIG_SCRIPT= no idea what or where this is?
>> >> >>>>>>> >> >> >>
>> >> >>>>>>> >> >> >> I have the above set apart from the fltk_config_script
>> >> >>>>>>> >> >> >> but
>> >> >>>>>>> >> >> >> cmake
>> >> >>>>>>> >> >> >> still
>> >> >>>>>>> >> >> >> tells me that FLTK is disabled because
>> >> >>>>>>> >> >> >> FLTK_FOUND=false.
>> >> >>>>>>> >> >> >> Any
>> >> >>>>>>> >> >> >> ideas?
>> >> >>>>>>> >> >> >>
>> >> >>>>>>> >> >> >>
>> >> >>>>>>> >> >> >>
>> >> >>>>>>> >> >> >>
>> >> >>>>>>> >> >> >>
>> >> >>>>>>> >> >> >>
>> >> >>>>>>> >> >> >>
>> >> >>>>>>> >> >> >> ------------------------------------------------------------------------------
>> >> >>>>>>> >> >> >> _______________________________________________
>> >> >>>>>>> >> >> >> Csound-devel mailing list
>> >> >>>>>>> >> >> >> Csound-devel@lists.sourceforge.net
>> >> >>>>>>> >> >> >>
>> >> >>>>>>> >> >> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> > ------------------------------------------------------------------------------
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> > _______________________________________________
>> >> >>>>>>> >> >> > Csound-devel mailing list
>> >> >>>>>>> >> >> > Csound-devel@lists.sourceforge.net
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >>>>>>> >> >> >
>> >> >>>>>>> >> >>
>> >> >>>>>>> >> >>
>> >> >>>>>>> >> >>
>> >> >>>>>>> >> >>
>> >> >>>>>>> >> >>
>> >> >>>>>>> >> >>
>> >> >>>>>>> >> >> ------------------------------------------------------------------------------
>> >> >>>>>>> >> >> _______________________________________________
>> >> >>>>>>> >> >> Csound-devel mailing list
>> >> >>>>>>> >> >> Csound-devel@lists.sourceforge.net
>> >> >>>>>>> >> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >>>>>>> >> >
>> >> >>>>>>> >> >
>> >> >>>>>>> >> >
>> >> >>>>>>> >> >
>> >> >>>>>>> >> >
>> >> >>>>>>> >> >
>> >> >>>>>>> >> >
>> >> >>>>>>> >> > ------------------------------------------------------------------------------
>> >> >>>>>>> >> >
>> >> >>>>>>> >> > _______________________________________________
>> >> >>>>>>> >> > Csound-devel mailing list
>> >> >>>>>>> >> > Csound-devel@lists.sourceforge.net
>> >> >>>>>>> >> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >>>>>>> >> >
>> >> >>>>>>> >>
>> >> >>>>>>> >>
>> >> >>>>>>> >>
>> >> >>>>>>> >>
>> >> >>>>>>> >>
>> >> >>>>>>> >> ------------------------------------------------------------------------------
>> >> >>>>>>> >> _______________________________________________
>> >> >>>>>>> >> Csound-devel mailing list
>> >> >>>>>>> >> Csound-devel@lists.sourceforge.net
>> >> >>>>>>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >>>>>>> >
>> >> >>>>>>> >
>> >> >>>>>>> >
>> >> >>>>>>> >
>> >> >>>>>>> >
>> >> >>>>>>> >
>> >> >>>>>>> > ------------------------------------------------------------------------------
>> >> >>>>>>> >
>> >> >>>>>>> > _______________________________________________
>> >> >>>>>>> > Csound-devel mailing list
>> >> >>>>>>> > Csound-devel@lists.sourceforge.net
>> >> >>>>>>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >>>>>>> >
>> >> >>>>>>>
>> >> >>>>>>>
>> >> >>>>>>>
>> >> >>>>>>>
>> >> >>>>>>> ------------------------------------------------------------------------------
>> >> >>>>>>> _______________________________________________
>> >> >>>>>>> Csound-devel mailing list
>> >> >>>>>>> Csound-devel@lists.sourceforge.net
>> >> >>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >>>>>>
>> >> >>>>>>
>> >> >>>>>>
>> >> >>>>>>
>> >> >>>>>>
>> >> >>>>>> ------------------------------------------------------------------------------
>> >> >>>>>>
>> >> >>>>>> _______________________________________________
>> >> >>>>>> Csound-devel mailing list
>> >> >>>>>> Csound-devel@lists.sourceforge.net
>> >> >>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> ------------------------------------------------------------------------------
>> >> >>>>> _______________________________________________
>> >> >>>>> Csound-devel mailing list
>> >> >>>>> Csound-devel@lists.sourceforge.net
>> >> >>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>> ------------------------------------------------------------------------------
>> >> >>>>
>> >> >>>> _______________________________________________
>> >> >>>> Csound-devel mailing list
>> >> >>>> Csound-devel@lists.sourceforge.net
>> >> >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >>>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> ------------------------------------------------------------------------------
>> >> >>> _______________________________________________
>> >> >>> Csound-devel mailing list
>> >> >>> Csound-devel@lists.sourceforge.net
>> >> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> ------------------------------------------------------------------------------
>> >> >>
>> >> >> _______________________________________________
>> >> >> Csound-devel mailing list
>> >> >> Csound-devel@lists.sourceforge.net
>> >> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > ------------------------------------------------------------------------------
>> >> >
>> >> > _______________________________________________
>> >> > Csound-devel mailing list
>> >> > Csound-devel@lists.sourceforge.net
>> >> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >> >
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> _______________________________________________
>> >> Csound-devel mailing list
>> >> Csound-devel@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Correction. If I put that stuff directly into CMakeLists.txt then it
works fine. But placing it in the custom.ex file doesn't seem to have
any affect.

On 30 October 2014 11:45, Rory Walsh  wrote:
> Btw, I couldn't ever get CMAKE_SYSYEM_INCLUDE to work. The only fail
> safe way I've managed to find of setting paths is by:
> set(CMAKE_C_FLAGS "-I../path/to/include/")
>
>
>
> On 29 October 2014 17:37, Steven Yi  wrote:
>> Awesome! Glad that's sorted.
>>
>>
>> On Wed Oct 29 2014 at 1:25:50 PM Rory Walsh  wrote:
>>>
>>> Ah, yes, I see. Argghh!! Looks like this was the problem all along. I
>>> saw the include files in the FL folder and assumed that it was the
>>> include directory. It's seen by cmake. I'll try building now.
>>>
>>> On 29 October 2014 17:15, Steven Yi  wrote:
>>> > Aren't the headers for including FLTK done like #include  ? If
>>> > so,
>>> > then your include path is off:
>>> >
>>> >  list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>>> >         "C:/Users/rory/Documents/sourcecode/fltk-1.3.2")
>>> >
>>> > Otherwise, if you built FLTK while in an msys shell, you could try just
>>> > doing "make install" and seeing if CMake then finds it.  If it doesn't,
>>> > you
>>> > could check if C:/MinGW/msys/1.0/lib and C:/MinGW/msys/1.0/include are
>>> > on
>>> > your paths too.
>>> >
>>> > On Wed Oct 29 2014 at 12:53:33 PM Rory Walsh  wrote:
>>> >>
>>> >> I tried the following in Custom.cmake.ex without any success:
>>> >>
>>> >> if(WIN32)
>>> >>     list(APPEND CMAKE_SYSTEM_LIBRARY_PATH
>>> >>         "C:/Users/rory/Documents/sourcecode/fltk-1.3.2/lib")
>>> >>     list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>>> >>         "C:/Users/rory/Documents/sourcecode/fltk-1.3.2/FL")
>>> >> endif()
>>> >>
>>> >> I still have no idea what the fltk-config script is?
>>> >>
>>> >> On 29 October 2014 16:13, Michael Gogins 
>>> >> wrote:
>>> >> > Thanks, the "list (...)" was the missing bit of information.
>>> >> >
>>> >> > Best,
>>> >> > Mike
>>> >> >
>>> >> > On Oct 29, 2014 11:46 AM, "Steven Yi"  wrote:
>>> >> >>
>>> >> >> Well, what I pasted earlier shows how it works:
>>> >> >>
>>> >> >> if(WIN32)
>>> >> >>
>>> >> >>     list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>>> >> >>
>>> >> >>             "c:/work/libsndfile-1_0_17")
>>> >> >>
>>> >> >>     list(APPEND CMAKE_SYSTEM_LIBRARY_PATH
>>> >> >>
>>> >> >>             "c:/work/libsndfile-1_0_17")
>>> >> >>
>>> >> >>
>>> >> >>     list(APPEND CMAKE_SYSTEM_LIBRARY_PATH
>>> >> >>
>>> >> >>         "c:/Python25/libs")
>>> >> >>
>>> >> >>     list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>>> >> >>
>>> >> >>         "c:/Python25/include")
>>> >> >>
>>> >> >>
>>> >> >> endif()
>>> >> >>
>>> >> >>
>>> >> >> That appends values to CMAKE_SYSTEM_INCLUDE_PATH and
>>> >> >> CMAKE_SYSTEM_LIBRARY_PATH, using standard Cmake list command.  You
>>> >> >> can
>>> >> >> add
>>> >> >> something like:
>>> >> >>
>>> >> >>
>>> >> >>     list(APPEND CMAKE_SYSTEM_LIBRARY_PATH
>>> >> >>
>>> >> >>         "c:/some/fltk/directory/lib")
>>> >> >>
>>> >> >>     list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>>> >> >>
>>> >> >>         "c:/some/fltk/directory/include")
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> On Wed Oct 29 2014 at 11:32:16 AM Michael Gogins
>>> >> >>  wrote:
>>> >> >>>
>>> >> >>> "any normal CMake command in there gets run". Can you give me an
>>> >> >>> example?
>>> >> >>> E.g. for configuring FLTK in a non-standard location? The example
>>> >> >>> doesn't
>>> >> >>> have to actually work, just indicate how to specify the commands.
>>> >> >>>
>>> >> >>> Best,
>>> >> >>> Mike
>>> >> >>>
>>> >> >>>
>>> >> >>> -----------------------------------------------------
>>> >> >>> Michael Gogins
>>> >> >>> Irreducible Productions
>>> >> >>> http://michaelgogins.tumblr.com
>>> >> >>> Michael dot Gogins at gmail dot com
>>> >> >>>
>>> >> >>> On Wed, Oct 29, 2014 at 11:18 AM, Steven Yi 
>>> >> >>> wrote:
>>> >> >>>>
>>> >> >>>> Custom.cmake gets include()'d near the top of the main
>>> >> >>>> CMakeLists.txt.
>>> >> >>>> It functions like the old custom.py in the CS5 Scons build.  Since
>>> >> >>>> it's just
>>> >> >>>> an include, any normal CMake command in there gets run.  This
>>> >> >>>> allows
>>> >> >>>> flexibility to customize paths in a repeatable way.  (I sometimes
>>> >> >>>> do
>>> >> >>>> a
>>> >> >>>> separate build in a separate folder with a different branch, so
>>> >> >>>> I'll
>>> >> >>>> copy
>>> >> >>>> the Custom.cmake I use from one folder to another).
>>> >> >>>>
>>> >> >>>> On Wed Oct 29 2014 at 10:28:02 AM Michael Gogins
>>> >> >>>>  wrote:
>>> >> >>>>>
>>> >> >>>>> The use of Custom.cmake is never explained, therefore I have not
>>> >> >>>>> been
>>> >> >>>>> able to use it.
>>> >> >>>>>
>>> >> >>>>> An example of Custom.cmake or explanation of how to use it would
>>> >> >>>>> be
>>> >> >>>>> much appreciated.
>>> >> >>>>>
>>> >> >>>>> As you suggest, I have increasingly relied on installing to
>>> >> >>>>> /usr/local.
>>> >> >>>>> But there is not always a working install target or script on
>>> >> >>>>> Windows, so
>>> >> >>>>> this is a bit flaky.
>>> >> >>>>>
>>> >> >>>>> Regards,
>>> >> >>>>> Mike
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> -----------------------------------------------------
>>> >> >>>>> Michael Gogins
>>> >> >>>>> Irreducible Productions
>>> >> >>>>> http://michaelgogins.tumblr.com
>>> >> >>>>> Michael dot Gogins at gmail dot com
>>> >> >>>>>
>>> >> >>>>> On Wed, Oct 29, 2014 at 10:23 AM, Steven Yi 
>>> >> >>>>> wrote:
>>> >> >>>>>>
>>> >> >>>>>> For libraries and headers, I think it's preferable to install
>>> >> >>>>>> them
>>> >> >>>>>> into a location that CMake will find it, rather than setting
>>> >> >>>>>> them
>>> >> >>>>>> yourself
>>> >> >>>>>> in the cache. Normally that means installing the library after
>>> >> >>>>>> building to
>>> >> >>>>>> /usr/local. However, you can add additional paths for CMake to
>>> >> >>>>>> search.  If
>>> >> >>>>>> you look at the Cusom.cmake.ex file, you'll see things like:
>>> >> >>>>>>
>>> >> >>>>>> if(WIN32)
>>> >> >>>>>>
>>> >> >>>>>>     list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>>> >> >>>>>>
>>> >> >>>>>>             "c:/work/libsndfile-1_0_17")
>>> >> >>>>>>
>>> >> >>>>>>     list(APPEND CMAKE_SYSTEM_LIBRARY_PATH
>>> >> >>>>>>
>>> >> >>>>>>             "c:/work/libsndfile-1_0_17")
>>> >> >>>>>>
>>> >> >>>>>>
>>> >> >>>>>>     list(APPEND CMAKE_SYSTEM_LIBRARY_PATH
>>> >> >>>>>>
>>> >> >>>>>>         "c:/Python25/libs")
>>> >> >>>>>>
>>> >> >>>>>>     list(APPEND CMAKE_SYSTEM_INCLUDE_PATH
>>> >> >>>>>>
>>> >> >>>>>>         "c:/Python25/include")
>>> >> >>>>>>
>>> >> >>>>>>
>>> >> >>>>>> endif()
>>> >> >>>>>>
>>> >> >>>>>> If you copy that to Custom.cmake, then you can add your own
>>> >> >>>>>> paths.
>>> >> >>>>>> So
>>> >> >>>>>> a couple of options here:
>>> >> >>>>>>
>>> >> >>>>>> 1. You can still try doing a "make install".  That probably only
>>> >> >>>>>> works
>>> >> >>>>>> if you're within an msys shell. (I'm not certain what the
>>> >> >>>>>> convention is for
>>> >> >>>>>> the standard cmd prompt if you use MinGW's make.)
>>> >> >>>>>>
>>> >> >>>>>> 2. You can create a folder where you'll manually add all of your
>>> >> >>>>>> libs
>>> >> >>>>>> and headers.  Then you can add that folder to your paths. This
>>> >> >>>>>> is
>>> >> >>>>>> handy if
>>> >> >>>>>> you want to isolate the dependencies you build from the rest of
>>> >> >>>>>> your system.
>>> >> >>>>>> For the mingw cross-compile scripts for compiling the windows
>>> >> >>>>>> binaries from
>>> >> >>>>>> Linux, that was the approach I took with the dependency builder
>>> >> >>>>>> scripts.
>>> >> >>>>>>
>>> >> >>>>>> 3. You can individually add each folder of each dependency you
>>> >> >>>>>> build
>>> >> >>>>>> to the CMake paths.
>>> >> >>>>>>
>>> >> >>>>>> Hope that helps!
>>> >> >>>>>>
>>> >> >>>>>> steven
>>> >> >>>>>>
>>> >> >>>>>>
>>> >> >>>>>> On Wed Oct 29 2014 at 10:16:26 AM Rory Walsh 
>>> >> >>>>>> wrote:
>>> >> >>>>>>>
>>> >> >>>>>>> Yes, my point is I have no idea what else I need to tell cmake
>>> >> >>>>>>> so
>>> >> >>>>>>> that
>>> >> >>>>>>> it finds it. I've added valid paths to all the fltk stuff.
>>> >> >>>>>>> Anyhow,
>>> >> >>>>>>> your cmake cache should help sort it out.
>>> >> >>>>>>>
>>> >> >>>>>>> On 29 October 2014 14:10, Michael Gogins
>>> >> >>>>>>> 
>>> >> >>>>>>> wrote:
>>> >> >>>>>>> > It returns false because FLTK is not found. We just tell
>>> >> >>>>>>> > CMake
>>> >> >>>>>>> > where it is.
>>> >> >>>>>>> > Not the same thing.
>>> >> >>>>>>> >
>>> >> >>>>>>> > Regards,
>>> >> >>>>>>> > Mike
>>> >> >>>>>>> >
>>> >> >>>>>>> >
>>> >> >>>>>>> > -----------------------------------------------------
>>> >> >>>>>>> > Michael Gogins
>>> >> >>>>>>> > Irreducible Productions
>>> >> >>>>>>> > http://michaelgogins.tumblr.com
>>> >> >>>>>>> > Michael dot Gogins at gmail dot com
>>> >> >>>>>>> >
>>> >> >>>>>>> > On Wed, Oct 29, 2014 at 9:58 AM, Rory Walsh
>>> >> >>>>>>> > 
>>> >> >>>>>>> > wrote:
>>> >> >>>>>>> >>
>>> >> >>>>>>> >> Thanks Mike, that would help. I'm just curious as to why
>>> >> >>>>>>> >> FLTK_FOUND
>>> >> >>>>>>> >> keeps returning false.
>>> >> >>>>>>> >>
>>> >> >>>>>>> >> On 29 October 2014 13:54, Michael Gogins
>>> >> >>>>>>> >>  wrote:
>>> >> >>>>>>> >> > OK, sorry about that. I just kept looking at the CMake
>>> >> >>>>>>> >> > error
>>> >> >>>>>>> >> > messages
>>> >> >>>>>>> >> > and
>>> >> >>>>>>> >> > filling in missing variables. If you like, when I get home
>>> >> >>>>>>> >> > this
>>> >> >>>>>>> >> > evening
>>> >> >>>>>>> >> > I
>>> >> >>>>>>> >> > will send you my CMake cache.
>>> >> >>>>>>> >> >
>>> >> >>>>>>> >> > Regards,
>>> >> >>>>>>> >> > Mike
>>> >> >>>>>>> >> >
>>> >> >>>>>>> >> >
>>> >> >>>>>>> >> > -----------------------------------------------------
>>> >> >>>>>>> >> > Michael Gogins
>>> >> >>>>>>> >> > Irreducible Productions
>>> >> >>>>>>> >> > http://michaelgogins.tumblr.com
>>> >> >>>>>>> >> > Michael dot Gogins at gmail dot com
>>> >> >>>>>>> >> >
>>> >> >>>>>>> >> > On Wed, Oct 29, 2014 at 8:41 AM, Rory Walsh
>>> >> >>>>>>> >> > 
>>> >> >>>>>>> >> > wrote:
>>> >> >>>>>>> >> >>
>>> >> >>>>>>> >> >> Yup. I don't see anything in there relating to how to set
>>> >> >>>>>>> >> >> up
>>> >> >>>>>>> >> >> cmake so
>>> >> >>>>>>> >> >> that it sees fltk?
>>> >> >>>>>>> >> >>
>>> >> >>>>>>> >> >> On 29 October 2014 12:34, Michael Gogins
>>> >> >>>>>>> >> >> 
>>> >> >>>>>>> >> >> wrote:
>>> >> >>>>>>> >> >> > Did you read my "how to build on Windows" document?
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> > Regards,
>>> >> >>>>>>> >> >> > Mike
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> > -----------------------------------------------------
>>> >> >>>>>>> >> >> > Michael Gogins
>>> >> >>>>>>> >> >> > Irreducible Productions
>>> >> >>>>>>> >> >> > http://michaelgogins.tumblr.com
>>> >> >>>>>>> >> >> > Michael dot Gogins at gmail dot com
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> > On Wed, Oct 29, 2014 at 8:18 AM, Rory Walsh
>>> >> >>>>>>> >> >> >  wrote:
>>> >> >>>>>>> >> >> >>
>>> >> >>>>>>> >> >> >> I'm having a go at a full Windows build at the moment,
>>> >> >>>>>>> >> >> >> but
>>> >> >>>>>>> >> >> >> once
>>> >> >>>>>>> >> >> >> again
>>> >> >>>>>>> >> >> >> have come up a cropper with fltk. It builds fine for
>>> >> >>>>>>> >> >> >> me,
>>> >> >>>>>>> >> >> >> but
>>> >> >>>>>>> >> >> >> I can't
>>> >> >>>>>>> >> >> >> get cmake to see it. Can anyone confirm what values I
>>> >> >>>>>>> >> >> >> should
>>> >> >>>>>>> >> >> >> have
>>> >> >>>>>>> >> >> >> for
>>> >> >>>>>>> >> >> >> these entries to CMake:
>>> >> >>>>>>> >> >> >>
>>> >> >>>>>>> >> >> >> FLTK_INCLUDE_DIR= ..........this is the FL directory
>>> >> >>>>>>> >> >> >> contained in
>>> >> >>>>>>> >> >> >> the
>>> >> >>>>>>> >> >> >> main fltk dir?
>>> >> >>>>>>> >> >> >> FLTK_DIR=.........the main fltk directory?
>>> >> >>>>>>> >> >> >> FLTK_BASE_LIBRARY=.......lib/libfltk.a?
>>> >> >>>>>>> >> >> >> FLTK_CONFIG_SCRIPT= no idea what or where this is?
>>> >> >>>>>>> >> >> >>
>>> >> >>>>>>> >> >> >> I have the above set apart from the fltk_config_script
>>> >> >>>>>>> >> >> >> but
>>> >> >>>>>>> >> >> >> cmake
>>> >> >>>>>>> >> >> >> still
>>> >> >>>>>>> >> >> >> tells me that FLTK is disabled because
>>> >> >>>>>>> >> >> >> FLTK_FOUND=false.
>>> >> >>>>>>> >> >> >> Any
>>> >> >>>>>>> >> >> >> ideas?
>>> >> >>>>>>> >> >> >>
>>> >> >>>>>>> >> >> >>
>>> >> >>>>>>> >> >> >>
>>> >> >>>>>>> >> >> >>
>>> >> >>>>>>> >> >> >>
>>> >> >>>>>>> >> >> >>
>>> >> >>>>>>> >> >> >>
>>> >> >>>>>>> >> >> >> ------------------------------------------------------------------------------
>>> >> >>>>>>> >> >> >> _______________________________________________
>>> >> >>>>>>> >> >> >> Csound-devel mailing list
>>> >> >>>>>>> >> >> >> Csound-devel@lists.sourceforge.net
>>> >> >>>>>>> >> >> >>
>>> >> >>>>>>> >> >> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> > ------------------------------------------------------------------------------
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> > _______________________________________________
>>> >> >>>>>>> >> >> > Csound-devel mailing list
>>> >> >>>>>>> >> >> > Csound-devel@lists.sourceforge.net
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >> >>>>>>> >> >> >
>>> >> >>>>>>> >> >>
>>> >> >>>>>>> >> >>
>>> >> >>>>>>> >> >>
>>> >> >>>>>>> >> >>
>>> >> >>>>>>> >> >>
>>> >> >>>>>>> >> >>
>>> >> >>>>>>> >> >> ------------------------------------------------------------------------------
>>> >> >>>>>>> >> >> _______________________________________________
>>> >> >>>>>>> >> >> Csound-devel mailing list
>>> >> >>>>>>> >> >> Csound-devel@lists.sourceforge.net
>>> >> >>>>>>> >> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >> >>>>>>> >> >
>>> >> >>>>>>> >> >
>>> >> >>>>>>> >> >
>>> >> >>>>>>> >> >
>>> >> >>>>>>> >> >
>>> >> >>>>>>> >> >
>>> >> >>>>>>> >> >
>>> >> >>>>>>> >> > ------------------------------------------------------------------------------
>>> >> >>>>>>> >> >
>>> >> >>>>>>> >> > _______________________________________________
>>> >> >>>>>>> >> > Csound-devel mailing list
>>> >> >>>>>>> >> > Csound-devel@lists.sourceforge.net
>>> >> >>>>>>> >> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >> >>>>>>> >> >
>>> >> >>>>>>> >>
>>> >> >>>>>>> >>
>>> >> >>>>>>> >>
>>> >> >>>>>>> >>
>>> >> >>>>>>> >>
>>> >> >>>>>>> >> ------------------------------------------------------------------------------
>>> >> >>>>>>> >> _______________________________________________
>>> >> >>>>>>> >> Csound-devel mailing list
>>> >> >>>>>>> >> Csound-devel@lists.sourceforge.net
>>> >> >>>>>>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >> >>>>>>> >
>>> >> >>>>>>> >
>>> >> >>>>>>> >
>>> >> >>>>>>> >
>>> >> >>>>>>> >
>>> >> >>>>>>> >
>>> >> >>>>>>> > ------------------------------------------------------------------------------
>>> >> >>>>>>> >
>>> >> >>>>>>> > _______________________________________________
>>> >> >>>>>>> > Csound-devel mailing list
>>> >> >>>>>>> > Csound-devel@lists.sourceforge.net
>>> >> >>>>>>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >> >>>>>>> >
>>> >> >>>>>>>
>>> >> >>>>>>>
>>> >> >>>>>>>
>>> >> >>>>>>>
>>> >> >>>>>>> ------------------------------------------------------------------------------
>>> >> >>>>>>> _______________________________________________
>>> >> >>>>>>> Csound-devel mailing list
>>> >> >>>>>>> Csound-devel@lists.sourceforge.net
>>> >> >>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >> >>>>>>
>>> >> >>>>>>
>>> >> >>>>>>
>>> >> >>>>>>
>>> >> >>>>>>
>>> >> >>>>>> ------------------------------------------------------------------------------
>>> >> >>>>>>
>>> >> >>>>>> _______________________________________________
>>> >> >>>>>> Csound-devel mailing list
>>> >> >>>>>> Csound-devel@lists.sourceforge.net
>>> >> >>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >> >>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> ------------------------------------------------------------------------------
>>> >> >>>>> _______________________________________________
>>> >> >>>>> Csound-devel mailing list
>>> >> >>>>> Csound-devel@lists.sourceforge.net
>>> >> >>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >> >>>>
>>> >> >>>>
>>> >> >>>>
>>> >> >>>>
>>> >> >>>>
>>> >> >>>> ------------------------------------------------------------------------------
>>> >> >>>>
>>> >> >>>> _______________________________________________
>>> >> >>>> Csound-devel mailing list
>>> >> >>>> Csound-devel@lists.sourceforge.net
>>> >> >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >> >>>>
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> >> >>> ------------------------------------------------------------------------------
>>> >> >>> _______________________________________________
>>> >> >>> Csound-devel mailing list
>>> >> >>> Csound-devel@lists.sourceforge.net
>>> >> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> ------------------------------------------------------------------------------
>>> >> >>
>>> >> >> _______________________________________________
>>> >> >> Csound-devel mailing list
>>> >> >> Csound-devel@lists.sourceforge.net
>>> >> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > ------------------------------------------------------------------------------
>>> >> >
>>> >> > _______________________________________________
>>> >> > Csound-devel mailing list
>>> >> > Csound-devel@lists.sourceforge.net
>>> >> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> ------------------------------------------------------------------------------
>>> >> _______________________________________________
>>> >> Csound-devel mailing list
>>> >> Csound-devel@lists.sourceforge.net
>>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >
>>> >
>>> >
>>> > ------------------------------------------------------------------------------
>>> >
>>> > _______________________________________________
>>> > Csound-devel mailing list
>>> > Csound-devel@lists.sourceforge.net
>>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>

------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net