Hi All,

I have setup a release branch for 6.07.0 on github.  The branch can be
pulled by using:

git pull
git checkout release/6.07.0

I think the version.h has already been set to 6.07.0. Installer
scripts may need to be updated to reflect the new version.

I believe we are using Github for the next release.  There's a bit of
a chicken and egg issue with setting up a release: on Github, releases
are associated with tags, but we should wait to tag the release as
part of "finishing" the release branch as part of git-flow.  I would
propose: let's build the releases from the release branch and signal
here when a release is ready.  Once we've all built, I can finish the
release branch which will tag the release and merge with master.  At
that point, we can create the file release on Github and upload builds
there.  Also to note, Github will auto-generated source releases (zip,
bz2 I think) for the release, so we will only have to work on compiled
releases.

One last thing: since our releases often package in the reference
manual, we should probably first tag and build the manual.  Who will
do this?

Thanks!

And apologies, it seems like a change to CMake  I made isn't working
on Travis/Linux.  I will revert in both the develop and release
branch.

On Sun, May 15, 2016 at 4:15 PM, Steven Yi  wrote:
> Hi All,
>
> I have setup a release branch for 6.07.0 on github.  The branch can be
> pulled by using:
>
> git pull
> git checkout release/6.07.0
>
> I think the version.h has already been set to 6.07.0. Installer
> scripts may need to be updated to reflect the new version.
>
> I believe we are using Github for the next release.  There's a bit of
> a chicken and egg issue with setting up a release: on Github, releases
> are associated with tags, but we should wait to tag the release as
> part of "finishing" the release branch as part of git-flow.  I would
> propose: let's build the releases from the release branch and signal
> here when a release is ready.  Once we've all built, I can finish the
> release branch which will tag the release and merge with master.  At
> that point, we can create the file release on Github and upload builds
> there.  Also to note, Github will auto-generated source releases (zip,
> bz2 I think) for the release, so we will only have to work on compiled
> releases.
>
> One last thing: since our releases often package in the reference
> manual, we should probably first tag and build the manual.  Who will
> do this?
>
> Thanks!

Hi Francois,

What do you think about doing a release for the manual on the
csound/manual github repo?

Thanks!
steven

On Sun, May 15, 2016 at 4:20 PM, Francois PINOT  wrote:
> I'll build the manual in the different formats (10 packages) and let you get
> it from my repo.
>
> Francois
>
> 2016-05-15 22:17 GMT+02:00 Steven Yi :
>>
>> And apologies, it seems like a change to CMake  I made isn't working
>> on Travis/Linux.  I will revert in both the develop and release
>> branch.
>>
>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi  wrote:
>> > Hi All,
>> >
>> > I have setup a release branch for 6.07.0 on github.  The branch can be
>> > pulled by using:
>> >
>> > git pull
>> > git checkout release/6.07.0
>> >
>> > I think the version.h has already been set to 6.07.0. Installer
>> > scripts may need to be updated to reflect the new version.
>> >
>> > I believe we are using Github for the next release.  There's a bit of
>> > a chicken and egg issue with setting up a release: on Github, releases
>> > are associated with tags, but we should wait to tag the release as
>> > part of "finishing" the release branch as part of git-flow.  I would
>> > propose: let's build the releases from the release branch and signal
>> > here when a release is ready.  Once we've all built, I can finish the
>> > release branch which will tag the release and merge with master.  At
>> > that point, we can create the file release on Github and upload builds
>> > there.  Also to note, Github will auto-generated source releases (zip,
>> > bz2 I think) for the release, so we will only have to work on compiled
>> > releases.
>> >
>> > One last thing: since our releases often package in the reference
>> > manual, we should probably first tag and build the manual.  Who will
>> > do this?
>> >
>> > Thanks!
>> > steven
>

Will do.

Best,
Mike

Hi Francois,

Thanks!  I think having the manual with the main Csound release is fine.

For myself, I have so far built the Emscripten release.  I will look
at Android and static-lib version of iOS next.

steven

On Sun, May 15, 2016 at 6:58 PM, Francois PINOT  wrote:
> manual and manual-fr are now tagged on github. You can get the built
> packages here:
>
> http://fggp.org/csound/manual-packages/
>
> Francois
>
> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
>>
>> Maybe the manual packages should be found in the same place (csound repo)
>> than the csound packages, as it was on SF?
>>
>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>>>
>>> Hi Francois,
>>>
>>> What do you think about doing a release for the manual on the
>>> csound/manual github repo?
>>>
>>> Thanks!
>>> steven
>>>
>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
>>> wrote:
>>> > I'll build the manual in the different formats (10 packages) and let
>>> > you get
>>> > it from my repo.
>>> >
>>> > Francois
>>> >
>>> > 2016-05-15 22:17 GMT+02:00 Steven Yi :
>>> >>
>>> >> And apologies, it seems like a change to CMake  I made isn't working
>>> >> on Travis/Linux.  I will revert in both the develop and release
>>> >> branch.
>>> >>
>>> >> On Sun, May 15, 2016 at 4:15 PM, Steven Yi  wrote:
>>> >> > Hi All,
>>> >> >
>>> >> > I have setup a release branch for 6.07.0 on github.  The branch can
>>> >> > be
>>> >> > pulled by using:
>>> >> >
>>> >> > git pull
>>> >> > git checkout release/6.07.0
>>> >> >
>>> >> > I think the version.h has already been set to 6.07.0. Installer
>>> >> > scripts may need to be updated to reflect the new version.
>>> >> >
>>> >> > I believe we are using Github for the next release.  There's a bit
>>> >> > of
>>> >> > a chicken and egg issue with setting up a release: on Github,
>>> >> > releases
>>> >> > are associated with tags, but we should wait to tag the release as
>>> >> > part of "finishing" the release branch as part of git-flow.  I would
>>> >> > propose: let's build the releases from the release branch and signal
>>> >> > here when a release is ready.  Once we've all built, I can finish
>>> >> > the
>>> >> > release branch which will tag the release and merge with master.  At
>>> >> > that point, we can create the file release on Github and upload
>>> >> > builds
>>> >> > there.  Also to note, Github will auto-generated source releases
>>> >> > (zip,
>>> >> > bz2 I think) for the release, so we will only have to work on
>>> >> > compiled
>>> >> > releases.
>>> >> >
>>> >> > One last thing: since our releases often package in the reference
>>> >> > manual, we should probably first tag and build the manual.  Who will
>>> >> > do this?
>>> >> >
>>> >> > Thanks!
>>> >> > steven
>>> >
>>> >
>>
>>

I have built Csound 6.07 for Windows x64 from the release branch, and
it installs and runs. I have one or two minor changes to files in the
release branch, but no source code changes. I am going to do a few
more tests tomorrow.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
> Hi Francois,
>
> Thanks!  I think having the manual with the main Csound release is fine.
>
> For myself, I have so far built the Emscripten release.  I will look
> at Android and static-lib version of iOS next.
>
> steven
>
> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT  wrote:
>> manual and manual-fr are now tagged on github. You can get the built
>> packages here:
>>
>> http://fggp.org/csound/manual-packages/
>>
>> Francois
>>
>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
>>>
>>> Maybe the manual packages should be found in the same place (csound repo)
>>> than the csound packages, as it was on SF?
>>>
>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>>>>
>>>> Hi Francois,
>>>>
>>>> What do you think about doing a release for the manual on the
>>>> csound/manual github repo?
>>>>
>>>> Thanks!
>>>> steven
>>>>
>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
>>>> wrote:
>>>> > I'll build the manual in the different formats (10 packages) and let
>>>> > you get
>>>> > it from my repo.
>>>> >
>>>> > Francois
>>>> >
>>>> > 2016-05-15 22:17 GMT+02:00 Steven Yi :
>>>> >>
>>>> >> And apologies, it seems like a change to CMake  I made isn't working
>>>> >> on Travis/Linux.  I will revert in both the develop and release
>>>> >> branch.
>>>> >>
>>>> >> On Sun, May 15, 2016 at 4:15 PM, Steven Yi  wrote:
>>>> >> > Hi All,
>>>> >> >
>>>> >> > I have setup a release branch for 6.07.0 on github.  The branch can
>>>> >> > be
>>>> >> > pulled by using:
>>>> >> >
>>>> >> > git pull
>>>> >> > git checkout release/6.07.0
>>>> >> >
>>>> >> > I think the version.h has already been set to 6.07.0. Installer
>>>> >> > scripts may need to be updated to reflect the new version.
>>>> >> >
>>>> >> > I believe we are using Github for the next release.  There's a bit
>>>> >> > of
>>>> >> > a chicken and egg issue with setting up a release: on Github,
>>>> >> > releases
>>>> >> > are associated with tags, but we should wait to tag the release as
>>>> >> > part of "finishing" the release branch as part of git-flow.  I would
>>>> >> > propose: let's build the releases from the release branch and signal
>>>> >> > here when a release is ready.  Once we've all built, I can finish
>>>> >> > the
>>>> >> > release branch which will tag the release and merge with master.  At
>>>> >> > that point, we can create the file release on Github and upload
>>>> >> > builds
>>>> >> > there.  Also to note, Github will auto-generated source releases
>>>> >> > (zip,
>>>> >> > bz2 I think) for the release, so we will only have to work on
>>>> >> > compiled
>>>> >> > releases.
>>>> >> >
>>>> >> > One last thing: since our releases often package in the reference
>>>> >> > manual, we should probably first tag and build the manual.  Who will
>>>> >> > do this?
>>>> >> >
>>>> >> > Thanks!
>>>> >> > steven
>>>> >
>>>> >
>>>
>>>

I ran into an issue with Android and minSdkVersions (should be an easy
fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs further
investigation).  Will look into this tomorrow.

On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
 wrote:
> I have built Csound 6.07 for Windows x64 from the release branch, and
> it installs and runs. I have one or two minor changes to files in the
> release branch, but no source code changes. I am going to do a few
> more tests tomorrow.
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
>> Hi Francois,
>>
>> Thanks!  I think having the manual with the main Csound release is fine.
>>
>> For myself, I have so far built the Emscripten release.  I will look
>> at Android and static-lib version of iOS next.
>>
>> steven
>>
>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT  wrote:
>>> manual and manual-fr are now tagged on github. You can get the built
>>> packages here:
>>>
>>> http://fggp.org/csound/manual-packages/
>>>
>>> Francois
>>>
>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
>>>>
>>>> Maybe the manual packages should be found in the same place (csound repo)
>>>> than the csound packages, as it was on SF?
>>>>
>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>>>>>
>>>>> Hi Francois,
>>>>>
>>>>> What do you think about doing a release for the manual on the
>>>>> csound/manual github repo?
>>>>>
>>>>> Thanks!
>>>>> steven
>>>>>
>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
>>>>> wrote:
>>>>> > I'll build the manual in the different formats (10 packages) and let
>>>>> > you get
>>>>> > it from my repo.
>>>>> >
>>>>> > Francois
>>>>> >
>>>>> > 2016-05-15 22:17 GMT+02:00 Steven Yi :
>>>>> >>
>>>>> >> And apologies, it seems like a change to CMake  I made isn't working
>>>>> >> on Travis/Linux.  I will revert in both the develop and release
>>>>> >> branch.
>>>>> >>
>>>>> >> On Sun, May 15, 2016 at 4:15 PM, Steven Yi  wrote:
>>>>> >> > Hi All,
>>>>> >> >
>>>>> >> > I have setup a release branch for 6.07.0 on github.  The branch can
>>>>> >> > be
>>>>> >> > pulled by using:
>>>>> >> >
>>>>> >> > git pull
>>>>> >> > git checkout release/6.07.0
>>>>> >> >
>>>>> >> > I think the version.h has already been set to 6.07.0. Installer
>>>>> >> > scripts may need to be updated to reflect the new version.
>>>>> >> >
>>>>> >> > I believe we are using Github for the next release.  There's a bit
>>>>> >> > of
>>>>> >> > a chicken and egg issue with setting up a release: on Github,
>>>>> >> > releases
>>>>> >> > are associated with tags, but we should wait to tag the release as
>>>>> >> > part of "finishing" the release branch as part of git-flow.  I would
>>>>> >> > propose: let's build the releases from the release branch and signal
>>>>> >> > here when a release is ready.  Once we've all built, I can finish
>>>>> >> > the
>>>>> >> > release branch which will tag the release and merge with master.  At
>>>>> >> > that point, we can create the file release on Github and upload
>>>>> >> > builds
>>>>> >> > there.  Also to note, Github will auto-generated source releases
>>>>> >> > (zip,
>>>>> >> > bz2 I think) for the release, so we will only have to work on
>>>>> >> > compiled
>>>>> >> > releases.
>>>>> >> >
>>>>> >> > One last thing: since our releases often package in the reference
>>>>> >> > manual, we should probably first tag and build the manual.  Who will
>>>>> >> > do this?
>>>>> >> >
>>>>> >> > Thanks!
>>>>> >> > steven
>>>>> >
>>>>> >
>>>>
>>>>

I will include the header. Go ahead and make a compact installer option that meets your needs and book it in or issue a pull request. I wasn't even aware that there is a compact install option.

Regards,
Mike

Hi All,

An update from my side, for Android, I realized my NDK version was
quite old and so I have updated that for this build.  However, while
libcsound builds fine, I am getting various problems with the plugin
libs that will take a bit of time to sort out (should hopefully be
done in the next few hours). I'll update once things are complete.

steven

On Sun, May 15, 2016 at 10:45 PM, Steven Yi  wrote:
> I ran into an issue with Android and minSdkVersions (should be an easy
> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs further
> investigation).  Will look into this tomorrow.
>
> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
>  wrote:
>> I have built Csound 6.07 for Windows x64 from the release branch, and
>> it installs and runs. I have one or two minor changes to files in the
>> release branch, but no source code changes. I am going to do a few
>> more tests tomorrow.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
>>> Hi Francois,
>>>
>>> Thanks!  I think having the manual with the main Csound release is fine.
>>>
>>> For myself, I have so far built the Emscripten release.  I will look
>>> at Android and static-lib version of iOS next.
>>>
>>> steven
>>>
>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT  wrote:
>>>> manual and manual-fr are now tagged on github. You can get the built
>>>> packages here:
>>>>
>>>> http://fggp.org/csound/manual-packages/
>>>>
>>>> Francois
>>>>
>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
>>>>>
>>>>> Maybe the manual packages should be found in the same place (csound repo)
>>>>> than the csound packages, as it was on SF?
>>>>>
>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>>>>>>
>>>>>> Hi Francois,
>>>>>>
>>>>>> What do you think about doing a release for the manual on the
>>>>>> csound/manual github repo?
>>>>>>
>>>>>> Thanks!
>>>>>> steven
>>>>>>
>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
>>>>>> wrote:
>>>>>> > I'll build the manual in the different formats (10 packages) and let
>>>>>> > you get
>>>>>> > it from my repo.
>>>>>> >
>>>>>> > Francois
>>>>>> >
>>>>>> > 2016-05-15 22:17 GMT+02:00 Steven Yi :
>>>>>> >>
>>>>>> >> And apologies, it seems like a change to CMake  I made isn't working
>>>>>> >> on Travis/Linux.  I will revert in both the develop and release
>>>>>> >> branch.
>>>>>> >>
>>>>>> >> On Sun, May 15, 2016 at 4:15 PM, Steven Yi  wrote:
>>>>>> >> > Hi All,
>>>>>> >> >
>>>>>> >> > I have setup a release branch for 6.07.0 on github.  The branch can
>>>>>> >> > be
>>>>>> >> > pulled by using:
>>>>>> >> >
>>>>>> >> > git pull
>>>>>> >> > git checkout release/6.07.0
>>>>>> >> >
>>>>>> >> > I think the version.h has already been set to 6.07.0. Installer
>>>>>> >> > scripts may need to be updated to reflect the new version.
>>>>>> >> >
>>>>>> >> > I believe we are using Github for the next release.  There's a bit
>>>>>> >> > of
>>>>>> >> > a chicken and egg issue with setting up a release: on Github,
>>>>>> >> > releases
>>>>>> >> > are associated with tags, but we should wait to tag the release as
>>>>>> >> > part of "finishing" the release branch as part of git-flow.  I would
>>>>>> >> > propose: let's build the releases from the release branch and signal
>>>>>> >> > here when a release is ready.  Once we've all built, I can finish
>>>>>> >> > the
>>>>>> >> > release branch which will tag the release and merge with master.  At
>>>>>> >> > that point, we can create the file release on Github and upload
>>>>>> >> > builds
>>>>>> >> > there.  Also to note, Github will auto-generated source releases
>>>>>> >> > (zip,
>>>>>> >> > bz2 I think) for the release, so we will only have to work on
>>>>>> >> > compiled
>>>>>> >> > releases.
>>>>>> >> >
>>>>>> >> > One last thing: since our releases often package in the reference
>>>>>> >> > manual, we should probably first tag and build the manual.  Who will
>>>>>> >> > do this?
>>>>>> >> >
>>>>>> >> > Thanks!
>>>>>> >> > steven
>>>>>> >
>>>>>> >
>>>>>
>>>>>

Make sure that the plugin mk files are set up
to use clang, which libcsound is now using.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 16 May 2016, at 15:08, Steven Yi  wrote:
> 
> Hi All,
> 
> An update from my side, for Android, I realized my NDK version was
> quite old and so I have updated that for this build.  However, while
> libcsound builds fine, I am getting various problems with the plugin
> libs that will take a bit of time to sort out (should hopefully be
> done in the next few hours). I'll update once things are complete.
> 
> steven
> 
>> On Sun, May 15, 2016 at 10:45 PM, Steven Yi  wrote:
>> I ran into an issue with Android and minSdkVersions (should be an easy
>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs further
>> investigation).  Will look into this tomorrow.
>> 
>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
>>  wrote:
>>> I have built Csound 6.07 for Windows x64 from the release branch, and
>>> it installs and runs. I have one or two minor changes to files in the
>>> release branch, but no source code changes. I am going to do a few
>>> more tests tomorrow.
>>> 
>>> Regards,
>>> Mike
>>> 
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>> 
>>> 
>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
>>>> Hi Francois,
>>>> 
>>>> Thanks!  I think having the manual with the main Csound release is fine.
>>>> 
>>>> For myself, I have so far built the Emscripten release.  I will look
>>>> at Android and static-lib version of iOS next.
>>>> 
>>>> steven
>>>> 
>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT  wrote:
>>>>> manual and manual-fr are now tagged on github. You can get the built
>>>>> packages here:
>>>>> 
>>>>> http://fggp.org/csound/manual-packages/
>>>>> 
>>>>> Francois
>>>>> 
>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
>>>>>> 
>>>>>> Maybe the manual packages should be found in the same place (csound repo)
>>>>>> than the csound packages, as it was on SF?
>>>>>> 
>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>>>>>>> 
>>>>>>> Hi Francois,
>>>>>>> 
>>>>>>> What do you think about doing a release for the manual on the
>>>>>>> csound/manual github repo?
>>>>>>> 
>>>>>>> Thanks!
>>>>>>> steven
>>>>>>> 
>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
>>>>>>> wrote:
>>>>>>>> I'll build the manual in the different formats (10 packages) and let
>>>>>>>> you get
>>>>>>>> it from my repo.
>>>>>>>> 
>>>>>>>> Francois
>>>>>>>> 
>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
>>>>>>>>> 
>>>>>>>>> And apologies, it seems like a change to CMake  I made isn't working
>>>>>>>>> on Travis/Linux.  I will revert in both the develop and release
>>>>>>>>> branch.
>>>>>>>>> 
>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi  wrote:
>>>>>>>>>> Hi All,
>>>>>>>>>> 
>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The branch can
>>>>>>>>>> be
>>>>>>>>>> pulled by using:
>>>>>>>>>> 
>>>>>>>>>> git pull
>>>>>>>>>> git checkout release/6.07.0
>>>>>>>>>> 
>>>>>>>>>> I think the version.h has already been set to 6.07.0. Installer
>>>>>>>>>> scripts may need to be updated to reflect the new version.
>>>>>>>>>> 
>>>>>>>>>> I believe we are using Github for the next release.  There's a bit
>>>>>>>>>> of
>>>>>>>>>> a chicken and egg issue with setting up a release: on Github,
>>>>>>>>>> releases
>>>>>>>>>> are associated with tags, but we should wait to tag the release as
>>>>>>>>>> part of "finishing" the release branch as part of git-flow.  I would
>>>>>>>>>> propose: let's build the releases from the release branch and signal
>>>>>>>>>> here when a release is ready.  Once we've all built, I can finish
>>>>>>>>>> the
>>>>>>>>>> release branch which will tag the release and merge with master.  At
>>>>>>>>>> that point, we can create the file release on Github and upload
>>>>>>>>>> builds
>>>>>>>>>> there.  Also to note, Github will auto-generated source releases
>>>>>>>>>> (zip,
>>>>>>>>>> bz2 I think) for the release, so we will only have to work on
>>>>>>>>>> compiled
>>>>>>>>>> releases.
>>>>>>>>>> 
>>>>>>>>>> One last thing: since our releases often package in the reference
>>>>>>>>>> manual, we should probably first tag and build the manual.  Who will
>>>>>>>>>> do this?
>>>>>>>>>> 
>>>>>>>>>> Thanks!
>>>>>>>>>> steven

I would prefer Minimal or Core and Complete.

Thanks,
Mike

How does one build Csound for Android now on Windows? Is Clang now included in the NDK?

Regards,
Mike

yes, it’s the recommendation from the Android NDK people,
see release notes for NDK11

http://developer.android.com/ndk/downloads/revision_history.html

they’re starting to drop gcc support.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 16 May 2016, at 16:13, Michael Gogins  wrote:
> 
> How does one build Csound for Android now on Windows? Is Clang now included in the NDK?
> 
> Regards, 
> Mike
> 
> On May 16, 2016 10:17 AM, "Victor Lazzarini"  wrote:
> Make sure that the plugin mk files are set up
> to use clang, which libcsound is now using.
> 
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
> 
> > On 16 May 2016, at 15:08, Steven Yi  wrote:
> >
> > Hi All,
> >
> > An update from my side, for Android, I realized my NDK version was
> > quite old and so I have updated that for this build.  However, while
> > libcsound builds fine, I am getting various problems with the plugin
> > libs that will take a bit of time to sort out (should hopefully be
> > done in the next few hours). I'll update once things are complete.
> >
> > steven
> >
> >> On Sun, May 15, 2016 at 10:45 PM, Steven Yi  wrote:
> >> I ran into an issue with Android and minSdkVersions (should be an easy
> >> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs further
> >> investigation).  Will look into this tomorrow.
> >>
> >> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
> >>  wrote:
> >>> I have built Csound 6.07 for Windows x64 from the release branch, and
> >>> it installs and runs. I have one or two minor changes to files in the
> >>> release branch, but no source code changes. I am going to do a few
> >>> more tests tomorrow.
> >>>
> >>> Regards,
> >>> Mike
> >>>
> >>> -----------------------------------------------------
> >>> Michael Gogins
> >>> Irreducible Productions
> >>> http://michaelgogins.tumblr.com
> >>> Michael dot Gogins at gmail dot com
> >>>
> >>>
> >>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
> >>>> Hi Francois,
> >>>>
> >>>> Thanks!  I think having the manual with the main Csound release is fine.
> >>>>
> >>>> For myself, I have so far built the Emscripten release.  I will look
> >>>> at Android and static-lib version of iOS next.
> >>>>
> >>>> steven
> >>>>
> >>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT  wrote:
> >>>>> manual and manual-fr are now tagged on github. You can get the built
> >>>>> packages here:
> >>>>>
> >>>>> http://fggp.org/csound/manual-packages/
> >>>>>
> >>>>> Francois
> >>>>>
> >>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
> >>>>>>
> >>>>>> Maybe the manual packages should be found in the same place (csound repo)
> >>>>>> than the csound packages, as it was on SF?
> >>>>>>
> >>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
> >>>>>>>
> >>>>>>> Hi Francois,
> >>>>>>>
> >>>>>>> What do you think about doing a release for the manual on the
> >>>>>>> csound/manual github repo?
> >>>>>>>
> >>>>>>> Thanks!
> >>>>>>> steven
> >>>>>>>
> >>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
> >>>>>>> wrote:
> >>>>>>>> I'll build the manual in the different formats (10 packages) and let
> >>>>>>>> you get
> >>>>>>>> it from my repo.
> >>>>>>>>
> >>>>>>>> Francois
> >>>>>>>>
> >>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
> >>>>>>>>>
> >>>>>>>>> And apologies, it seems like a change to CMake  I made isn't working
> >>>>>>>>> on Travis/Linux.  I will revert in both the develop and release
> >>>>>>>>> branch.
> >>>>>>>>>
> >>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi  wrote:
> >>>>>>>>>> Hi All,
> >>>>>>>>>>
> >>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The branch can
> >>>>>>>>>> be
> >>>>>>>>>> pulled by using:
> >>>>>>>>>>
> >>>>>>>>>> git pull
> >>>>>>>>>> git checkout release/6.07.0
> >>>>>>>>>>
> >>>>>>>>>> I think the version.h has already been set to 6.07.0. Installer
> >>>>>>>>>> scripts may need to be updated to reflect the new version.
> >>>>>>>>>>
> >>>>>>>>>> I believe we are using Github for the next release.  There's a bit
> >>>>>>>>>> of
> >>>>>>>>>> a chicken and egg issue with setting up a release: on Github,
> >>>>>>>>>> releases
> >>>>>>>>>> are associated with tags, but we should wait to tag the release as
> >>>>>>>>>> part of "finishing" the release branch as part of git-flow.  I would
> >>>>>>>>>> propose: let's build the releases from the release branch and signal
> >>>>>>>>>> here when a release is ready.  Once we've all built, I can finish
> >>>>>>>>>> the
> >>>>>>>>>> release branch which will tag the release and merge with master.  At
> >>>>>>>>>> that point, we can create the file release on Github and upload
> >>>>>>>>>> builds
> >>>>>>>>>> there.  Also to note, Github will auto-generated source releases
> >>>>>>>>>> (zip,
> >>>>>>>>>> bz2 I think) for the release, so we will only have to work on
> >>>>>>>>>> compiled
> >>>>>>>>>> releases.
> >>>>>>>>>>
> >>>>>>>>>> One last thing: since our releases often package in the reference
> >>>>>>>>>> manual, we should probably first tag and build the manual.  Who will
> >>>>>>>>>> do this?
> >>>>>>>>>>
> >>>>>>>>>> Thanks!
> >>>>>>>>>> steven

Note that it’s the cross compiler for android we’re talking about, not the OSX system compiler,
two different things. It comes in the NDK.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 16 May 2016, at 16:13, Michael Gogins  wrote:
> 
> How does one build Csound for Android now on Windows? Is Clang now included in the NDK?
> 
> Regards, 
> Mike
> 
> On May 16, 2016 10:17 AM, "Victor Lazzarini"  wrote:
> Make sure that the plugin mk files are set up
> to use clang, which libcsound is now using.
> 
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
> 
> > On 16 May 2016, at 15:08, Steven Yi  wrote:
> >
> > Hi All,
> >
> > An update from my side, for Android, I realized my NDK version was
> > quite old and so I have updated that for this build.  However, while
> > libcsound builds fine, I am getting various problems with the plugin
> > libs that will take a bit of time to sort out (should hopefully be
> > done in the next few hours). I'll update once things are complete.
> >
> > steven
> >
> >> On Sun, May 15, 2016 at 10:45 PM, Steven Yi  wrote:
> >> I ran into an issue with Android and minSdkVersions (should be an easy
> >> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs further
> >> investigation).  Will look into this tomorrow.
> >>
> >> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
> >>  wrote:
> >>> I have built Csound 6.07 for Windows x64 from the release branch, and
> >>> it installs and runs. I have one or two minor changes to files in the
> >>> release branch, but no source code changes. I am going to do a few
> >>> more tests tomorrow.
> >>>
> >>> Regards,
> >>> Mike
> >>>
> >>> -----------------------------------------------------
> >>> Michael Gogins
> >>> Irreducible Productions
> >>> http://michaelgogins.tumblr.com
> >>> Michael dot Gogins at gmail dot com
> >>>
> >>>
> >>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
> >>>> Hi Francois,
> >>>>
> >>>> Thanks!  I think having the manual with the main Csound release is fine.
> >>>>
> >>>> For myself, I have so far built the Emscripten release.  I will look
> >>>> at Android and static-lib version of iOS next.
> >>>>
> >>>> steven
> >>>>
> >>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT  wrote:
> >>>>> manual and manual-fr are now tagged on github. You can get the built
> >>>>> packages here:
> >>>>>
> >>>>> http://fggp.org/csound/manual-packages/
> >>>>>
> >>>>> Francois
> >>>>>
> >>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
> >>>>>>
> >>>>>> Maybe the manual packages should be found in the same place (csound repo)
> >>>>>> than the csound packages, as it was on SF?
> >>>>>>
> >>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
> >>>>>>>
> >>>>>>> Hi Francois,
> >>>>>>>
> >>>>>>> What do you think about doing a release for the manual on the
> >>>>>>> csound/manual github repo?
> >>>>>>>
> >>>>>>> Thanks!
> >>>>>>> steven
> >>>>>>>
> >>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
> >>>>>>> wrote:
> >>>>>>>> I'll build the manual in the different formats (10 packages) and let
> >>>>>>>> you get
> >>>>>>>> it from my repo.
> >>>>>>>>
> >>>>>>>> Francois
> >>>>>>>>
> >>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
> >>>>>>>>>
> >>>>>>>>> And apologies, it seems like a change to CMake  I made isn't working
> >>>>>>>>> on Travis/Linux.  I will revert in both the develop and release
> >>>>>>>>> branch.
> >>>>>>>>>
> >>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi  wrote:
> >>>>>>>>>> Hi All,
> >>>>>>>>>>
> >>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The branch can
> >>>>>>>>>> be
> >>>>>>>>>> pulled by using:
> >>>>>>>>>>
> >>>>>>>>>> git pull
> >>>>>>>>>> git checkout release/6.07.0
> >>>>>>>>>>
> >>>>>>>>>> I think the version.h has already been set to 6.07.0. Installer
> >>>>>>>>>> scripts may need to be updated to reflect the new version.
> >>>>>>>>>>
> >>>>>>>>>> I believe we are using Github for the next release.  There's a bit
> >>>>>>>>>> of
> >>>>>>>>>> a chicken and egg issue with setting up a release: on Github,
> >>>>>>>>>> releases
> >>>>>>>>>> are associated with tags, but we should wait to tag the release as
> >>>>>>>>>> part of "finishing" the release branch as part of git-flow.  I would
> >>>>>>>>>> propose: let's build the releases from the release branch and signal
> >>>>>>>>>> here when a release is ready.  Once we've all built, I can finish
> >>>>>>>>>> the
> >>>>>>>>>> release branch which will tag the release and merge with master.  At
> >>>>>>>>>> that point, we can create the file release on Github and upload
> >>>>>>>>>> builds
> >>>>>>>>>> there.  Also to note, Github will auto-generated source releases
> >>>>>>>>>> (zip,
> >>>>>>>>>> bz2 I think) for the release, so we will only have to work on
> >>>>>>>>>> compiled
> >>>>>>>>>> releases.
> >>>>>>>>>>
> >>>>>>>>>> One last thing: since our releases often package in the reference
> >>>>>>>>>> manual, we should probably first tag and build the manual.  Who will
> >>>>>>>>>> do this?
> >>>>>>>>>>
> >>>>>>>>>> Thanks!
> >>>>>>>>>> steven

On 15 May 2016 at 16:15, Steven Yi  wrote:
> Also to note, Github will auto-generated source releases (zip,
> bz2 I think) for the release, so we will only have to work on compiled
> releases.

Note to self and other packagers: this will be the source code as
present in git. I don't think this will cause problems (cmake does not
ship autogenerated stuff in the tarballs like the autotools), but
should keep in mind anyway. In particular, the git control files will
be present (.gitignore/.gitattributes).

-- 

Saludos,

Where do the release files go?  URL?

Also should we delete files fromSF?  Ihave copies if most of them and 
could sync te rest



On Mon, 16 May 2016, Felipe Sateler wrote:

> On 15 May 2016 at 16:15, Steven Yi  wrote:
>> Also to note, Github will auto-generated source releases (zip,
>> bz2 I think) for the release, so we will only have to work on compiled
>> releases.
>
> Note to self and other packagers: this will be the source code as
> present in git. I don't think this will cause problems (cmake does not
> ship autogenerated stuff in the tarballs like the autotools), but
> should keep in mind anyway. In particular, the git control files will
> be present (.gitignore/.gitattributes).
>
> -- 
>
> Saludos,
> Felipe Sateler

Re: Android, I know that libcsound is being built with it, I will
double check on the plugins.

For the releases, we need to wait until the release branch is
"finished", which will be after everyone reports that their builds are
done.  Once that is done, I'll finish the release branch and it will
commit a tag for the release.  From there, we can setup a file release
on Github associated with the tag. It sounds like everyone else is
complete except for me on Android and iOS.  Hopefully the remaining
issues will be quick.

On Mon, May 16, 2016 at 11:42 AM, jpff  wrote:
> Where do the release files go?  URL?
>
> Also should we delete files fromSF?  Ihave copies if most of them and could
> sync te rest
>
>
>
>
> On Mon, 16 May 2016, Felipe Sateler wrote:
>
>> On 15 May 2016 at 16:15, Steven Yi  wrote:
>>>
>>> Also to note, Github will auto-generated source releases (zip,
>>> bz2 I think) for the release, so we will only have to work on compiled
>>> releases.
>>
>>
>> Note to self and other packagers: this will be the source code as
>> present in git. I don't think this will cause problems (cmake does not
>> ship autogenerated stuff in the tarballs like the autotools), but
>> should keep in mind anyway. In particular, the git control files will
>> be present (.gitignore/.gitattributes).
>>
>> --
>>
>> Saludos,
>> Felipe Sateler
>>

I think I have most of the Csound plugins compiling. It looks like a
few warnings are popping up, but the one plugin that isn't compiling
is LuaOpcodes because I'm having a difficult time for luajit to
compile.  I'm going to stop and move on to iOS and come back to this.

On Mon, May 16, 2016 at 11:55 AM, Steven Yi  wrote:
> Re: Android, I know that libcsound is being built with it, I will
> double check on the plugins.
>
> For the releases, we need to wait until the release branch is
> "finished", which will be after everyone reports that their builds are
> done.  Once that is done, I'll finish the release branch and it will
> commit a tag for the release.  From there, we can setup a file release
> on Github associated with the tag. It sounds like everyone else is
> complete except for me on Android and iOS.  Hopefully the remaining
> issues will be quick.
>
> On Mon, May 16, 2016 at 11:42 AM, jpff  wrote:
>> Where do the release files go?  URL?
>>
>> Also should we delete files fromSF?  Ihave copies if most of them and could
>> sync te rest
>>
>>
>>
>>
>> On Mon, 16 May 2016, Felipe Sateler wrote:
>>
>>> On 15 May 2016 at 16:15, Steven Yi  wrote:
>>>>
>>>> Also to note, Github will auto-generated source releases (zip,
>>>> bz2 I think) for the release, so we will only have to work on compiled
>>>> releases.
>>>
>>>
>>> Note to self and other packagers: this will be the source code as
>>> present in git. I don't think this will cause problems (cmake does not
>>> ship autogenerated stuff in the tarballs like the autotools), but
>>> should keep in mind anyway. In particular, the git control files will
>>> be present (.gitignore/.gitattributes).
>>>
>>> --
>>>
>>> Saludos,
>>> Felipe Sateler
>>>

I did some research but did not find that anyone was building LuaJIT
using llvm or CLang. Therefore I conclude that LuaJIT itself must be
compiled using gcc. The LuaCsound opcodes are of course a plugin, so I
think that will work.

I also found that, because LuaJIT's code is challenging to understand,
other people have created similar projects, some based on llvm -- but
nothing other people have done is as small, or runs as fast, as
LuaJIT.

Best,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Mon, May 16, 2016 at 12:57 PM, Steven Yi  wrote:
> I think I have most of the Csound plugins compiling. It looks like a
> few warnings are popping up, but the one plugin that isn't compiling
> is LuaOpcodes because I'm having a difficult time for luajit to
> compile.  I'm going to stop and move on to iOS and come back to this.
>
> On Mon, May 16, 2016 at 11:55 AM, Steven Yi  wrote:
>> Re: Android, I know that libcsound is being built with it, I will
>> double check on the plugins.
>>
>> For the releases, we need to wait until the release branch is
>> "finished", which will be after everyone reports that their builds are
>> done.  Once that is done, I'll finish the release branch and it will
>> commit a tag for the release.  From there, we can setup a file release
>> on Github associated with the tag. It sounds like everyone else is
>> complete except for me on Android and iOS.  Hopefully the remaining
>> issues will be quick.
>>
>> On Mon, May 16, 2016 at 11:42 AM, jpff  wrote:
>>> Where do the release files go?  URL?
>>>
>>> Also should we delete files fromSF?  Ihave copies if most of them and could
>>> sync te rest
>>>
>>>
>>>
>>>
>>> On Mon, 16 May 2016, Felipe Sateler wrote:
>>>
>>>> On 15 May 2016 at 16:15, Steven Yi  wrote:
>>>>>
>>>>> Also to note, Github will auto-generated source releases (zip,
>>>>> bz2 I think) for the release, so we will only have to work on compiled
>>>>> releases.
>>>>
>>>>
>>>> Note to self and other packagers: this will be the source code as
>>>> present in git. I don't think this will cause problems (cmake does not
>>>> ship autogenerated stuff in the tarballs like the autotools), but
>>>> should keep in mind anyway. In particular, the git control files will
>>>> be present (.gitignore/.gitattributes).
>>>>
>>>> --
>>>>
>>>> Saludos,
>>>> Felipe Sateler
>>>>

Perhaps pffft.h should be moved from H to include.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wrote:
> Mike, can you include pfftt.h in the include folder with the latest
> installer? I tried your latest installer and noticed that choosing compact
> install will not actually install anything at all. I see from the iss file
> that no files are identified with the Compact installation. Would it be
> possible to use that option to install a very basic version of Csound, i.e.,
> everything needed to run the CLI, plugins and libs, and the Csound docs?
>
> On 16 May 2016 at 03:45, Steven Yi  wrote:
>>
>> I ran into an issue with Android and minSdkVersions (should be an easy
>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs further
>> investigation).  Will look into this tomorrow.
>>
>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
>>  wrote:
>> > I have built Csound 6.07 for Windows x64 from the release branch, and
>> > it installs and runs. I have one or two minor changes to files in the
>> > release branch, but no source code changes. I am going to do a few
>> > more tests tomorrow.
>> >
>> > Regards,
>> > Mike
>> >
>> > -----------------------------------------------------
>> > Michael Gogins
>> > Irreducible Productions
>> > http://michaelgogins.tumblr.com
>> > Michael dot Gogins at gmail dot com
>> >
>> >
>> > On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
>> >> Hi Francois,
>> >>
>> >> Thanks!  I think having the manual with the main Csound release is
>> >> fine.
>> >>
>> >> For myself, I have so far built the Emscripten release.  I will look
>> >> at Android and static-lib version of iOS next.
>> >>
>> >> steven
>> >>
>> >> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT 
>> >> wrote:
>> >>> manual and manual-fr are now tagged on github. You can get the built
>> >>> packages here:
>> >>>
>> >>> http://fggp.org/csound/manual-packages/
>> >>>
>> >>> Francois
>> >>>
>> >>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
>> >>>>
>> >>>> Maybe the manual packages should be found in the same place (csound
>> >>>> repo)
>> >>>> than the csound packages, as it was on SF?
>> >>>>
>> >>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>> >>>>>
>> >>>>> Hi Francois,
>> >>>>>
>> >>>>> What do you think about doing a release for the manual on the
>> >>>>> csound/manual github repo?
>> >>>>>
>> >>>>> Thanks!
>> >>>>> steven
>> >>>>>
>> >>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
>> >>>>> wrote:
>> >>>>> > I'll build the manual in the different formats (10 packages) and
>> >>>>> > let
>> >>>>> > you get
>> >>>>> > it from my repo.
>> >>>>> >
>> >>>>> > Francois
>> >>>>> >
>> >>>>> > 2016-05-15 22:17 GMT+02:00 Steven Yi :
>> >>>>> >>
>> >>>>> >> And apologies, it seems like a change to CMake  I made isn't
>> >>>>> >> working
>> >>>>> >> on Travis/Linux.  I will revert in both the develop and release
>> >>>>> >> branch.
>> >>>>> >>
>> >>>>> >> On Sun, May 15, 2016 at 4:15 PM, Steven Yi 
>> >>>>> >> wrote:
>> >>>>> >> > Hi All,
>> >>>>> >> >
>> >>>>> >> > I have setup a release branch for 6.07.0 on github.  The branch
>> >>>>> >> > can
>> >>>>> >> > be
>> >>>>> >> > pulled by using:
>> >>>>> >> >
>> >>>>> >> > git pull
>> >>>>> >> > git checkout release/6.07.0
>> >>>>> >> >
>> >>>>> >> > I think the version.h has already been set to 6.07.0. Installer
>> >>>>> >> > scripts may need to be updated to reflect the new version.
>> >>>>> >> >
>> >>>>> >> > I believe we are using Github for the next release.  There's a
>> >>>>> >> > bit
>> >>>>> >> > of
>> >>>>> >> > a chicken and egg issue with setting up a release: on Github,
>> >>>>> >> > releases
>> >>>>> >> > are associated with tags, but we should wait to tag the release
>> >>>>> >> > as
>> >>>>> >> > part of "finishing" the release branch as part of git-flow.  I
>> >>>>> >> > would
>> >>>>> >> > propose: let's build the releases from the release branch and
>> >>>>> >> > signal
>> >>>>> >> > here when a release is ready.  Once we've all built, I can
>> >>>>> >> > finish
>> >>>>> >> > the
>> >>>>> >> > release branch which will tag the release and merge with
>> >>>>> >> > master.  At
>> >>>>> >> > that point, we can create the file release on Github and upload
>> >>>>> >> > builds
>> >>>>> >> > there.  Also to note, Github will auto-generated source
>> >>>>> >> > releases
>> >>>>> >> > (zip,
>> >>>>> >> > bz2 I think) for the release, so we will only have to work on
>> >>>>> >> > compiled
>> >>>>> >> > releases.
>> >>>>> >> >
>> >>>>> >> > One last thing: since our releases often package in the
>> >>>>> >> > reference
>> >>>>> >> > manual, we should probably first tag and build the manual.  Who
>> >>>>> >> > will
>> >>>>> >> > do this?
>> >>>>> >> >
>> >>>>> >> > Thanks!
>> >>>>> >> > steven
>> >>>>> >
>> >>>>> >
>> >>>>
>> >>>>
>> >>>
>

No, the include should be removed from csoundCore.h and added to fftlib.c .

I thought I'd done that already, but obviously forgot about it.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 16 May 2016, at 18:13, Michael Gogins  wrote:
> 
> Perhaps pffft.h should be moved from H to include.
> 
> Regards,
> Mike
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> 
>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wrote:
>> Mike, can you include pfftt.h in the include folder with the latest
>> installer? I tried your latest installer and noticed that choosing compact
>> install will not actually install anything at all. I see from the iss file
>> that no files are identified with the Compact installation. Would it be
>> possible to use that option to install a very basic version of Csound, i.e.,
>> everything needed to run the CLI, plugins and libs, and the Csound docs?
>> 
>>> On 16 May 2016 at 03:45, Steven Yi  wrote:
>>> 
>>> I ran into an issue with Android and minSdkVersions (should be an easy
>>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs further
>>> investigation).  Will look into this tomorrow.
>>> 
>>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
>>>  wrote:
>>>> I have built Csound 6.07 for Windows x64 from the release branch, and
>>>> it installs and runs. I have one or two minor changes to files in the
>>>> release branch, but no source code changes. I am going to do a few
>>>> more tests tomorrow.
>>>> 
>>>> Regards,
>>>> Mike
>>>> 
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>> 
>>>> 
>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
>>>>> Hi Francois,
>>>>> 
>>>>> Thanks!  I think having the manual with the main Csound release is
>>>>> fine.
>>>>> 
>>>>> For myself, I have so far built the Emscripten release.  I will look
>>>>> at Android and static-lib version of iOS next.
>>>>> 
>>>>> steven
>>>>> 
>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT 
>>>>> wrote:
>>>>>> manual and manual-fr are now tagged on github. You can get the built
>>>>>> packages here:
>>>>>> 
>>>>>> http://fggp.org/csound/manual-packages/
>>>>>> 
>>>>>> Francois
>>>>>> 
>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
>>>>>>> 
>>>>>>> Maybe the manual packages should be found in the same place (csound
>>>>>>> repo)
>>>>>>> than the csound packages, as it was on SF?
>>>>>>> 
>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>>>>>>>> 
>>>>>>>> Hi Francois,
>>>>>>>> 
>>>>>>>> What do you think about doing a release for the manual on the
>>>>>>>> csound/manual github repo?
>>>>>>>> 
>>>>>>>> Thanks!
>>>>>>>> steven
>>>>>>>> 
>>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
>>>>>>>> wrote:
>>>>>>>>> I'll build the manual in the different formats (10 packages) and
>>>>>>>>> let
>>>>>>>>> you get
>>>>>>>>> it from my repo.
>>>>>>>>> 
>>>>>>>>> Francois
>>>>>>>>> 
>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
>>>>>>>>>> 
>>>>>>>>>> And apologies, it seems like a change to CMake  I made isn't
>>>>>>>>>> working
>>>>>>>>>> on Travis/Linux.  I will revert in both the develop and release
>>>>>>>>>> branch.
>>>>>>>>>> 
>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi 
>>>>>>>>>> wrote:
>>>>>>>>>>> Hi All,
>>>>>>>>>>> 
>>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The branch
>>>>>>>>>>> can
>>>>>>>>>>> be
>>>>>>>>>>> pulled by using:
>>>>>>>>>>> 
>>>>>>>>>>> git pull
>>>>>>>>>>> git checkout release/6.07.0
>>>>>>>>>>> 
>>>>>>>>>>> I think the version.h has already been set to 6.07.0. Installer
>>>>>>>>>>> scripts may need to be updated to reflect the new version.
>>>>>>>>>>> 
>>>>>>>>>>> I believe we are using Github for the next release.  There's a
>>>>>>>>>>> bit
>>>>>>>>>>> of
>>>>>>>>>>> a chicken and egg issue with setting up a release: on Github,
>>>>>>>>>>> releases
>>>>>>>>>>> are associated with tags, but we should wait to tag the release
>>>>>>>>>>> as
>>>>>>>>>>> part of "finishing" the release branch as part of git-flow.  I
>>>>>>>>>>> would
>>>>>>>>>>> propose: let's build the releases from the release branch and
>>>>>>>>>>> signal
>>>>>>>>>>> here when a release is ready.  Once we've all built, I can
>>>>>>>>>>> finish
>>>>>>>>>>> the
>>>>>>>>>>> release branch which will tag the release and merge with
>>>>>>>>>>> master.  At
>>>>>>>>>>> that point, we can create the file release on Github and upload
>>>>>>>>>>> builds
>>>>>>>>>>> there.  Also to note, Github will auto-generated source
>>>>>>>>>>> releases
>>>>>>>>>>> (zip,
>>>>>>>>>>> bz2 I think) for the release, so we will only have to work on
>>>>>>>>>>> compiled
>>>>>>>>>>> releases.
>>>>>>>>>>> 
>>>>>>>>>>> One last thing: since our releases often package in the
>>>>>>>>>>> reference
>>>>>>>>>>> manual, we should probably first tag and build the manual.  Who
>>>>>>>>>>> will
>>>>>>>>>>> do this?
>>>>>>>>>>> 
>>>>>>>>>>> Thanks!
>>>>>>>>>>> steven
>> 

I actually checked and I had moved the #include. So there is no need to add the
pffft.c to /include. It’s an internal header, only included in fftlib.c and pffft.c.

========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 16 May 2016, at 19:29, Victor Lazzarini  wrote:
> 
> No, the include should be removed from csoundCore.h and added to fftlib.c .
> 
> I thought I'd done that already, but obviously forgot about it.
> 
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
> 
>> On 16 May 2016, at 18:13, Michael Gogins  wrote:
>> 
>> Perhaps pffft.h should be moved from H to include.
>> 
>> Regards,
>> Mike
>> 
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>> 
>> 
>>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wrote:
>>> Mike, can you include pfftt.h in the include folder with the latest
>>> installer? I tried your latest installer and noticed that choosing compact
>>> install will not actually install anything at all. I see from the iss file
>>> that no files are identified with the Compact installation. Would it be
>>> possible to use that option to install a very basic version of Csound, i.e.,
>>> everything needed to run the CLI, plugins and libs, and the Csound docs?
>>> 
>>>> On 16 May 2016 at 03:45, Steven Yi  wrote:
>>>> 
>>>> I ran into an issue with Android and minSdkVersions (should be an easy
>>>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs further
>>>> investigation).  Will look into this tomorrow.
>>>> 
>>>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
>>>>  wrote:
>>>>> I have built Csound 6.07 for Windows x64 from the release branch, and
>>>>> it installs and runs. I have one or two minor changes to files in the
>>>>> release branch, but no source code changes. I am going to do a few
>>>>> more tests tomorrow.
>>>>> 
>>>>> Regards,
>>>>> Mike
>>>>> 
>>>>> -----------------------------------------------------
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://michaelgogins.tumblr.com
>>>>> Michael dot Gogins at gmail dot com
>>>>> 
>>>>> 
>>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
>>>>>> Hi Francois,
>>>>>> 
>>>>>> Thanks!  I think having the manual with the main Csound release is
>>>>>> fine.
>>>>>> 
>>>>>> For myself, I have so far built the Emscripten release.  I will look
>>>>>> at Android and static-lib version of iOS next.
>>>>>> 
>>>>>> steven
>>>>>> 
>>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT 
>>>>>> wrote:
>>>>>>> manual and manual-fr are now tagged on github. You can get the built
>>>>>>> packages here:
>>>>>>> 
>>>>>>> http://fggp.org/csound/manual-packages/
>>>>>>> 
>>>>>>> Francois
>>>>>>> 
>>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
>>>>>>>> 
>>>>>>>> Maybe the manual packages should be found in the same place (csound
>>>>>>>> repo)
>>>>>>>> than the csound packages, as it was on SF?
>>>>>>>> 
>>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>>>>>>>>> 
>>>>>>>>> Hi Francois,
>>>>>>>>> 
>>>>>>>>> What do you think about doing a release for the manual on the
>>>>>>>>> csound/manual github repo?
>>>>>>>>> 
>>>>>>>>> Thanks!
>>>>>>>>> steven
>>>>>>>>> 
>>>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
>>>>>>>>> wrote:
>>>>>>>>>> I'll build the manual in the different formats (10 packages) and
>>>>>>>>>> let
>>>>>>>>>> you get
>>>>>>>>>> it from my repo.
>>>>>>>>>> 
>>>>>>>>>> Francois
>>>>>>>>>> 
>>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
>>>>>>>>>>> 
>>>>>>>>>>> And apologies, it seems like a change to CMake  I made isn't
>>>>>>>>>>> working
>>>>>>>>>>> on Travis/Linux.  I will revert in both the develop and release
>>>>>>>>>>> branch.
>>>>>>>>>>> 
>>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi 
>>>>>>>>>>> wrote:
>>>>>>>>>>>> Hi All,
>>>>>>>>>>>> 
>>>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The branch
>>>>>>>>>>>> can
>>>>>>>>>>>> be
>>>>>>>>>>>> pulled by using:
>>>>>>>>>>>> 
>>>>>>>>>>>> git pull
>>>>>>>>>>>> git checkout release/6.07.0
>>>>>>>>>>>> 
>>>>>>>>>>>> I think the version.h has already been set to 6.07.0. Installer
>>>>>>>>>>>> scripts may need to be updated to reflect the new version.
>>>>>>>>>>>> 
>>>>>>>>>>>> I believe we are using Github for the next release.  There's a
>>>>>>>>>>>> bit
>>>>>>>>>>>> of
>>>>>>>>>>>> a chicken and egg issue with setting up a release: on Github,
>>>>>>>>>>>> releases
>>>>>>>>>>>> are associated with tags, but we should wait to tag the release
>>>>>>>>>>>> as
>>>>>>>>>>>> part of "finishing" the release branch as part of git-flow.  I
>>>>>>>>>>>> would
>>>>>>>>>>>> propose: let's build the releases from the release branch and
>>>>>>>>>>>> signal
>>>>>>>>>>>> here when a release is ready.  Once we've all built, I can
>>>>>>>>>>>> finish
>>>>>>>>>>>> the
>>>>>>>>>>>> release branch which will tag the release and merge with
>>>>>>>>>>>> master.  At
>>>>>>>>>>>> that point, we can create the file release on Github and upload
>>>>>>>>>>>> builds
>>>>>>>>>>>> there.  Also to note, Github will auto-generated source
>>>>>>>>>>>> releases
>>>>>>>>>>>> (zip,
>>>>>>>>>>>> bz2 I think) for the release, so we will only have to work on
>>>>>>>>>>>> compiled
>>>>>>>>>>>> releases.
>>>>>>>>>>>> 
>>>>>>>>>>>> One last thing: since our releases often package in the
>>>>>>>>>>>> reference
>>>>>>>>>>>> manual, we should probably first tag and build the manual.  Who
>>>>>>>>>>>> will
>>>>>>>>>>>> do this?
>>>>>>>>>>>> 
>>>>>>>>>>>> Thanks!
>>>>>>>>>>>> steven
>>> 

Built the installer here and tested, all seems OK. I need to add François new python interface to the installer, though.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 16 May 2016, at 19:34, Victor Lazzarini  wrote:
> 
> I actually checked and I had moved the #include. So there is no need to add the
> pffft.c to /include. It’s an internal header, only included in fftlib.c and pffft.c.
> 
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952 
> 
>> On 16 May 2016, at 19:29, Victor Lazzarini  wrote:
>> 
>> No, the include should be removed from csoundCore.h and added to fftlib.c .
>> 
>> I thought I'd done that already, but obviously forgot about it.
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>>> On 16 May 2016, at 18:13, Michael Gogins  wrote:
>>> 
>>> Perhaps pffft.h should be moved from H to include.
>>> 
>>> Regards,
>>> Mike
>>> 
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>> 
>>> 
>>>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wrote:
>>>> Mike, can you include pfftt.h in the include folder with the latest
>>>> installer? I tried your latest installer and noticed that choosing compact
>>>> install will not actually install anything at all. I see from the iss file
>>>> that no files are identified with the Compact installation. Would it be
>>>> possible to use that option to install a very basic version of Csound, i.e.,
>>>> everything needed to run the CLI, plugins and libs, and the Csound docs?
>>>> 
>>>>> On 16 May 2016 at 03:45, Steven Yi  wrote:
>>>>> 
>>>>> I ran into an issue with Android and minSdkVersions (should be an easy
>>>>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs further
>>>>> investigation).  Will look into this tomorrow.
>>>>> 
>>>>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
>>>>>  wrote:
>>>>>> I have built Csound 6.07 for Windows x64 from the release branch, and
>>>>>> it installs and runs. I have one or two minor changes to files in the
>>>>>> release branch, but no source code changes. I am going to do a few
>>>>>> more tests tomorrow.
>>>>>> 
>>>>>> Regards,
>>>>>> Mike
>>>>>> 
>>>>>> -----------------------------------------------------
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://michaelgogins.tumblr.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>> 
>>>>>> 
>>>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
>>>>>>> Hi Francois,
>>>>>>> 
>>>>>>> Thanks!  I think having the manual with the main Csound release is
>>>>>>> fine.
>>>>>>> 
>>>>>>> For myself, I have so far built the Emscripten release.  I will look
>>>>>>> at Android and static-lib version of iOS next.
>>>>>>> 
>>>>>>> steven
>>>>>>> 
>>>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT 
>>>>>>> wrote:
>>>>>>>> manual and manual-fr are now tagged on github. You can get the built
>>>>>>>> packages here:
>>>>>>>> 
>>>>>>>> http://fggp.org/csound/manual-packages/
>>>>>>>> 
>>>>>>>> Francois
>>>>>>>> 
>>>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
>>>>>>>>> 
>>>>>>>>> Maybe the manual packages should be found in the same place (csound
>>>>>>>>> repo)
>>>>>>>>> than the csound packages, as it was on SF?
>>>>>>>>> 
>>>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>>>>>>>>>> 
>>>>>>>>>> Hi Francois,
>>>>>>>>>> 
>>>>>>>>>> What do you think about doing a release for the manual on the
>>>>>>>>>> csound/manual github repo?
>>>>>>>>>> 
>>>>>>>>>> Thanks!
>>>>>>>>>> steven
>>>>>>>>>> 
>>>>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
>>>>>>>>>> wrote:
>>>>>>>>>>> I'll build the manual in the different formats (10 packages) and
>>>>>>>>>>> let
>>>>>>>>>>> you get
>>>>>>>>>>> it from my repo.
>>>>>>>>>>> 
>>>>>>>>>>> Francois
>>>>>>>>>>> 
>>>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
>>>>>>>>>>>> 
>>>>>>>>>>>> And apologies, it seems like a change to CMake  I made isn't
>>>>>>>>>>>> working
>>>>>>>>>>>> on Travis/Linux.  I will revert in both the develop and release
>>>>>>>>>>>> branch.
>>>>>>>>>>>> 
>>>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> Hi All,
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The branch
>>>>>>>>>>>>> can
>>>>>>>>>>>>> be
>>>>>>>>>>>>> pulled by using:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> git pull
>>>>>>>>>>>>> git checkout release/6.07.0
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I think the version.h has already been set to 6.07.0. Installer
>>>>>>>>>>>>> scripts may need to be updated to reflect the new version.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I believe we are using Github for the next release.  There's a
>>>>>>>>>>>>> bit
>>>>>>>>>>>>> of
>>>>>>>>>>>>> a chicken and egg issue with setting up a release: on Github,
>>>>>>>>>>>>> releases
>>>>>>>>>>>>> are associated with tags, but we should wait to tag the release
>>>>>>>>>>>>> as
>>>>>>>>>>>>> part of "finishing" the release branch as part of git-flow.  I
>>>>>>>>>>>>> would
>>>>>>>>>>>>> propose: let's build the releases from the release branch and
>>>>>>>>>>>>> signal
>>>>>>>>>>>>> here when a release is ready.  Once we've all built, I can
>>>>>>>>>>>>> finish
>>>>>>>>>>>>> the
>>>>>>>>>>>>> release branch which will tag the release and merge with
>>>>>>>>>>>>> master.  At
>>>>>>>>>>>>> that point, we can create the file release on Github and upload
>>>>>>>>>>>>> builds
>>>>>>>>>>>>> there.  Also to note, Github will auto-generated source
>>>>>>>>>>>>> releases
>>>>>>>>>>>>> (zip,
>>>>>>>>>>>>> bz2 I think) for the release, so we will only have to work on
>>>>>>>>>>>>> compiled
>>>>>>>>>>>>> releases.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> One last thing: since our releases often package in the
>>>>>>>>>>>>> reference
>>>>>>>>>>>>> manual, we should probably first tag and build the manual.  Who
>>>>>>>>>>>>> will
>>>>>>>>>>>>> do this?
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>> steven
>>>> 

That's not what Rory said.

I think he is saying this because he had a problem before I moved the header. 

ligeti:csound6 victor$ grep "pffft.h"  */*.h
ligeti:csound6 victor$ grep "pffft.h"  */*.c
OOps/fftlib.c:#include "pffft.h"
OOps/pffft.c:#include "pffft.h"
Opcodes/mp3in.c:#include 

See? It’s only included in three internal files. It’s nowhere in the public API. It should not be
in /include.

========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 16 May 2016, at 19:46, Michael Gogins  wrote:
> 
> That's not what Rory said.
> 
> On May 16, 2016 2:35 PM, "Victor Lazzarini"  wrote:
> I actually checked and I had moved the #include. So there is no need to add the
> pffft.c to /include. It’s an internal header, only included in fftlib.c and pffft.c.
> 
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
> 
> > On 16 May 2016, at 19:29, Victor Lazzarini  wrote:
> >
> > No, the include should be removed from csoundCore.h and added to fftlib.c .
> >
> > I thought I'd done that already, but obviously forgot about it.
> >
> > Victor Lazzarini
> > Dean of Arts, Celtic Studies, and Philosophy
> > Maynooth University
> > Ireland
> >
> >> On 16 May 2016, at 18:13, Michael Gogins  wrote:
> >>
> >> Perhaps pffft.h should be moved from H to include.
> >>
> >> Regards,
> >> Mike
> >>
> >> -----------------------------------------------------
> >> Michael Gogins
> >> Irreducible Productions
> >> http://michaelgogins.tumblr.com
> >> Michael dot Gogins at gmail dot com
> >>
> >>
> >>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wrote:
> >>> Mike, can you include pfftt.h in the include folder with the latest
> >>> installer? I tried your latest installer and noticed that choosing compact
> >>> install will not actually install anything at all. I see from the iss file
> >>> that no files are identified with the Compact installation. Would it be
> >>> possible to use that option to install a very basic version of Csound, i.e.,
> >>> everything needed to run the CLI, plugins and libs, and the Csound docs?
> >>>
> >>>> On 16 May 2016 at 03:45, Steven Yi  wrote:
> >>>>
> >>>> I ran into an issue with Android and minSdkVersions (should be an easy
> >>>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs further
> >>>> investigation).  Will look into this tomorrow.
> >>>>
> >>>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
> >>>>  wrote:
> >>>>> I have built Csound 6.07 for Windows x64 from the release branch, and
> >>>>> it installs and runs. I have one or two minor changes to files in the
> >>>>> release branch, but no source code changes. I am going to do a few
> >>>>> more tests tomorrow.
> >>>>>
> >>>>> Regards,
> >>>>> Mike
> >>>>>
> >>>>> -----------------------------------------------------
> >>>>> Michael Gogins
> >>>>> Irreducible Productions
> >>>>> http://michaelgogins.tumblr.com
> >>>>> Michael dot Gogins at gmail dot com
> >>>>>
> >>>>>
> >>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
> >>>>>> Hi Francois,
> >>>>>>
> >>>>>> Thanks!  I think having the manual with the main Csound release is
> >>>>>> fine.
> >>>>>>
> >>>>>> For myself, I have so far built the Emscripten release.  I will look
> >>>>>> at Android and static-lib version of iOS next.
> >>>>>>
> >>>>>> steven
> >>>>>>
> >>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT 
> >>>>>> wrote:
> >>>>>>> manual and manual-fr are now tagged on github. You can get the built
> >>>>>>> packages here:
> >>>>>>>
> >>>>>>> http://fggp.org/csound/manual-packages/
> >>>>>>>
> >>>>>>> Francois
> >>>>>>>
> >>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
> >>>>>>>>
> >>>>>>>> Maybe the manual packages should be found in the same place (csound
> >>>>>>>> repo)
> >>>>>>>> than the csound packages, as it was on SF?
> >>>>>>>>
> >>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
> >>>>>>>>>
> >>>>>>>>> Hi Francois,
> >>>>>>>>>
> >>>>>>>>> What do you think about doing a release for the manual on the
> >>>>>>>>> csound/manual github repo?
> >>>>>>>>>
> >>>>>>>>> Thanks!
> >>>>>>>>> steven
> >>>>>>>>>
> >>>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
> >>>>>>>>> wrote:
> >>>>>>>>>> I'll build the manual in the different formats (10 packages) and
> >>>>>>>>>> let
> >>>>>>>>>> you get
> >>>>>>>>>> it from my repo.
> >>>>>>>>>>
> >>>>>>>>>> Francois
> >>>>>>>>>>
> >>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
> >>>>>>>>>>>
> >>>>>>>>>>> And apologies, it seems like a change to CMake  I made isn't
> >>>>>>>>>>> working
> >>>>>>>>>>> on Travis/Linux.  I will revert in both the develop and release
> >>>>>>>>>>> branch.
> >>>>>>>>>>>
> >>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi 
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>> Hi All,
> >>>>>>>>>>>>
> >>>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The branch
> >>>>>>>>>>>> can
> >>>>>>>>>>>> be
> >>>>>>>>>>>> pulled by using:
> >>>>>>>>>>>>
> >>>>>>>>>>>> git pull
> >>>>>>>>>>>> git checkout release/6.07.0
> >>>>>>>>>>>>
> >>>>>>>>>>>> I think the version.h has already been set to 6.07.0. Installer
> >>>>>>>>>>>> scripts may need to be updated to reflect the new version.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I believe we are using Github for the next release.  There's a
> >>>>>>>>>>>> bit
> >>>>>>>>>>>> of
> >>>>>>>>>>>> a chicken and egg issue with setting up a release: on Github,
> >>>>>>>>>>>> releases
> >>>>>>>>>>>> are associated with tags, but we should wait to tag the release
> >>>>>>>>>>>> as
> >>>>>>>>>>>> part of "finishing" the release branch as part of git-flow.  I
> >>>>>>>>>>>> would
> >>>>>>>>>>>> propose: let's build the releases from the release branch and
> >>>>>>>>>>>> signal
> >>>>>>>>>>>> here when a release is ready.  Once we've all built, I can
> >>>>>>>>>>>> finish
> >>>>>>>>>>>> the
> >>>>>>>>>>>> release branch which will tag the release and merge with
> >>>>>>>>>>>> master.  At
> >>>>>>>>>>>> that point, we can create the file release on Github and upload
> >>>>>>>>>>>> builds
> >>>>>>>>>>>> there.  Also to note, Github will auto-generated source
> >>>>>>>>>>>> releases
> >>>>>>>>>>>> (zip,
> >>>>>>>>>>>> bz2 I think) for the release, so we will only have to work on
> >>>>>>>>>>>> compiled
> >>>>>>>>>>>> releases.
> >>>>>>>>>>>>
> >>>>>>>>>>>> One last thing: since our releases often package in the
> >>>>>>>>>>>> reference
> >>>>>>>>>>>> manual, we should probably first tag and build the manual.  Who
> >>>>>>>>>>>> will
> >>>>>>>>>>>> do this?
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks!
> >>>>>>>>>>>> steven
> >>>

OK, I will remove it from the installer then.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Mon, May 16, 2016 at 3:04 PM, Victor Lazzarini
 wrote:
> I think he is saying this because he had a problem before I moved the header.
>
> ligeti:csound6 victor$ grep "pffft.h"  */*.h
> ligeti:csound6 victor$ grep "pffft.h"  */*.c
> OOps/fftlib.c:#include "pffft.h"
> OOps/pffft.c:#include "pffft.h"
> Opcodes/mp3in.c:#include 
>
> See? It’s only included in three internal files. It’s nowhere in the public API. It should not be
> in /include.
>
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 16 May 2016, at 19:46, Michael Gogins  wrote:
>>
>> That's not what Rory said.
>>
>> On May 16, 2016 2:35 PM, "Victor Lazzarini"  wrote:
>> I actually checked and I had moved the #include. So there is no need to add the
>> pffft.c to /include. It’s an internal header, only included in fftlib.c and pffft.c.
>>
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>> > On 16 May 2016, at 19:29, Victor Lazzarini  wrote:
>> >
>> > No, the include should be removed from csoundCore.h and added to fftlib.c .
>> >
>> > I thought I'd done that already, but obviously forgot about it.
>> >
>> > Victor Lazzarini
>> > Dean of Arts, Celtic Studies, and Philosophy
>> > Maynooth University
>> > Ireland
>> >
>> >> On 16 May 2016, at 18:13, Michael Gogins  wrote:
>> >>
>> >> Perhaps pffft.h should be moved from H to include.
>> >>
>> >> Regards,
>> >> Mike
>> >>
>> >> -----------------------------------------------------
>> >> Michael Gogins
>> >> Irreducible Productions
>> >> http://michaelgogins.tumblr.com
>> >> Michael dot Gogins at gmail dot com
>> >>
>> >>
>> >>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wrote:
>> >>> Mike, can you include pfftt.h in the include folder with the latest
>> >>> installer? I tried your latest installer and noticed that choosing compact
>> >>> install will not actually install anything at all. I see from the iss file
>> >>> that no files are identified with the Compact installation. Would it be
>> >>> possible to use that option to install a very basic version of Csound, i.e.,
>> >>> everything needed to run the CLI, plugins and libs, and the Csound docs?
>> >>>
>> >>>> On 16 May 2016 at 03:45, Steven Yi  wrote:
>> >>>>
>> >>>> I ran into an issue with Android and minSdkVersions (should be an easy
>> >>>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs further
>> >>>> investigation).  Will look into this tomorrow.
>> >>>>
>> >>>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
>> >>>>  wrote:
>> >>>>> I have built Csound 6.07 for Windows x64 from the release branch, and
>> >>>>> it installs and runs. I have one or two minor changes to files in the
>> >>>>> release branch, but no source code changes. I am going to do a few
>> >>>>> more tests tomorrow.
>> >>>>>
>> >>>>> Regards,
>> >>>>> Mike
>> >>>>>
>> >>>>> -----------------------------------------------------
>> >>>>> Michael Gogins
>> >>>>> Irreducible Productions
>> >>>>> http://michaelgogins.tumblr.com
>> >>>>> Michael dot Gogins at gmail dot com
>> >>>>>
>> >>>>>
>> >>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
>> >>>>>> Hi Francois,
>> >>>>>>
>> >>>>>> Thanks!  I think having the manual with the main Csound release is
>> >>>>>> fine.
>> >>>>>>
>> >>>>>> For myself, I have so far built the Emscripten release.  I will look
>> >>>>>> at Android and static-lib version of iOS next.
>> >>>>>>
>> >>>>>> steven
>> >>>>>>
>> >>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT 
>> >>>>>> wrote:
>> >>>>>>> manual and manual-fr are now tagged on github. You can get the built
>> >>>>>>> packages here:
>> >>>>>>>
>> >>>>>>> http://fggp.org/csound/manual-packages/
>> >>>>>>>
>> >>>>>>> Francois
>> >>>>>>>
>> >>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
>> >>>>>>>>
>> >>>>>>>> Maybe the manual packages should be found in the same place (csound
>> >>>>>>>> repo)
>> >>>>>>>> than the csound packages, as it was on SF?
>> >>>>>>>>
>> >>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>> >>>>>>>>>
>> >>>>>>>>> Hi Francois,
>> >>>>>>>>>
>> >>>>>>>>> What do you think about doing a release for the manual on the
>> >>>>>>>>> csound/manual github repo?
>> >>>>>>>>>
>> >>>>>>>>> Thanks!
>> >>>>>>>>> steven
>> >>>>>>>>>
>> >>>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
>> >>>>>>>>> wrote:
>> >>>>>>>>>> I'll build the manual in the different formats (10 packages) and
>> >>>>>>>>>> let
>> >>>>>>>>>> you get
>> >>>>>>>>>> it from my repo.
>> >>>>>>>>>>
>> >>>>>>>>>> Francois
>> >>>>>>>>>>
>> >>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
>> >>>>>>>>>>>
>> >>>>>>>>>>> And apologies, it seems like a change to CMake  I made isn't
>> >>>>>>>>>>> working
>> >>>>>>>>>>> on Travis/Linux.  I will revert in both the develop and release
>> >>>>>>>>>>> branch.
>> >>>>>>>>>>>
>> >>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi 
>> >>>>>>>>>>> wrote:
>> >>>>>>>>>>>> Hi All,
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The branch
>> >>>>>>>>>>>> can
>> >>>>>>>>>>>> be
>> >>>>>>>>>>>> pulled by using:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> git pull
>> >>>>>>>>>>>> git checkout release/6.07.0
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> I think the version.h has already been set to 6.07.0. Installer
>> >>>>>>>>>>>> scripts may need to be updated to reflect the new version.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> I believe we are using Github for the next release.  There's a
>> >>>>>>>>>>>> bit
>> >>>>>>>>>>>> of
>> >>>>>>>>>>>> a chicken and egg issue with setting up a release: on Github,
>> >>>>>>>>>>>> releases
>> >>>>>>>>>>>> are associated with tags, but we should wait to tag the release
>> >>>>>>>>>>>> as
>> >>>>>>>>>>>> part of "finishing" the release branch as part of git-flow.  I
>> >>>>>>>>>>>> would
>> >>>>>>>>>>>> propose: let's build the releases from the release branch and
>> >>>>>>>>>>>> signal
>> >>>>>>>>>>>> here when a release is ready.  Once we've all built, I can
>> >>>>>>>>>>>> finish
>> >>>>>>>>>>>> the
>> >>>>>>>>>>>> release branch which will tag the release and merge with
>> >>>>>>>>>>>> master.  At
>> >>>>>>>>>>>> that point, we can create the file release on Github and upload
>> >>>>>>>>>>>> builds
>> >>>>>>>>>>>> there.  Also to note, Github will auto-generated source
>> >>>>>>>>>>>> releases
>> >>>>>>>>>>>> (zip,
>> >>>>>>>>>>>> bz2 I think) for the release, so we will only have to work on
>> >>>>>>>>>>>> compiled
>> >>>>>>>>>>>> releases.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> One last thing: since our releases often package in the
>> >>>>>>>>>>>> reference
>> >>>>>>>>>>>> manual, we should probably first tag and build the manual.  Who
>> >>>>>>>>>>>> will
>> >>>>>>>>>>>> do this?
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Thanks!
>> >>>>>>>>>>>> steven
>> >>>

yes, it was while I was adding the new fft routines, I forgot to tidy it up, but when you 
spotted it, it was fixed.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 16 May 2016, at 20:13, Rory Walsh  wrote:
> 
> Thanks guys. It was most likely before Victor tidied it up. 
> 
> 
> On 16 May 2016 at 20:12, Michael Gogins  wrote:
> OK, I will remove it from the installer then.
> 
> Regards,
> Mike
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> 
> On Mon, May 16, 2016 at 3:04 PM, Victor Lazzarini
>  wrote:
> > I think he is saying this because he had a problem before I moved the header.
> >
> > ligeti:csound6 victor$ grep "pffft.h"  */*.h
> > ligeti:csound6 victor$ grep "pffft.h"  */*.c
> > OOps/fftlib.c:#include "pffft.h"
> > OOps/pffft.c:#include "pffft.h"
> > Opcodes/mp3in.c:#include 
> >
> > See? It’s only included in three internal files. It’s nowhere in the public API. It should not be
> > in /include.
> >
> > ========================
> > Dr Victor Lazzarini
> > Dean of Arts, Celtic Studies and Philosophy,
> > Maynooth University,
> > Maynooth, Co Kildare, Ireland
> > Tel: 00 353 7086936
> > Fax: 00 353 1 7086952
> >
> >> On 16 May 2016, at 19:46, Michael Gogins  wrote:
> >>
> >> That's not what Rory said.
> >>
> >> On May 16, 2016 2:35 PM, "Victor Lazzarini"  wrote:
> >> I actually checked and I had moved the #include. So there is no need to add the
> >> pffft.c to /include. It’s an internal header, only included in fftlib.c and pffft.c.
> >>
> >> ========================
> >> Dr Victor Lazzarini
> >> Dean of Arts, Celtic Studies and Philosophy,
> >> Maynooth University,
> >> Maynooth, Co Kildare, Ireland
> >> Tel: 00 353 7086936
> >> Fax: 00 353 1 7086952
> >>
> >> > On 16 May 2016, at 19:29, Victor Lazzarini  wrote:
> >> >
> >> > No, the include should be removed from csoundCore.h and added to fftlib.c .
> >> >
> >> > I thought I'd done that already, but obviously forgot about it.
> >> >
> >> > Victor Lazzarini
> >> > Dean of Arts, Celtic Studies, and Philosophy
> >> > Maynooth University
> >> > Ireland
> >> >
> >> >> On 16 May 2016, at 18:13, Michael Gogins  wrote:
> >> >>
> >> >> Perhaps pffft.h should be moved from H to include.
> >> >>
> >> >> Regards,
> >> >> Mike
> >> >>
> >> >> -----------------------------------------------------
> >> >> Michael Gogins
> >> >> Irreducible Productions
> >> >> http://michaelgogins.tumblr.com
> >> >> Michael dot Gogins at gmail dot com
> >> >>
> >> >>
> >> >>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wrote:
> >> >>> Mike, can you include pfftt.h in the include folder with the latest
> >> >>> installer? I tried your latest installer and noticed that choosing compact
> >> >>> install will not actually install anything at all. I see from the iss file
> >> >>> that no files are identified with the Compact installation. Would it be
> >> >>> possible to use that option to install a very basic version of Csound, i.e.,
> >> >>> everything needed to run the CLI, plugins and libs, and the Csound docs?
> >> >>>
> >> >>>> On 16 May 2016 at 03:45, Steven Yi  wrote:
> >> >>>>
> >> >>>> I ran into an issue with Android and minSdkVersions (should be an easy
> >> >>>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs further
> >> >>>> investigation).  Will look into this tomorrow.
> >> >>>>
> >> >>>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
> >> >>>>  wrote:
> >> >>>>> I have built Csound 6.07 for Windows x64 from the release branch, and
> >> >>>>> it installs and runs. I have one or two minor changes to files in the
> >> >>>>> release branch, but no source code changes. I am going to do a few
> >> >>>>> more tests tomorrow.
> >> >>>>>
> >> >>>>> Regards,
> >> >>>>> Mike
> >> >>>>>
> >> >>>>> -----------------------------------------------------
> >> >>>>> Michael Gogins
> >> >>>>> Irreducible Productions
> >> >>>>> http://michaelgogins.tumblr.com
> >> >>>>> Michael dot Gogins at gmail dot com
> >> >>>>>
> >> >>>>>
> >> >>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
> >> >>>>>> Hi Francois,
> >> >>>>>>
> >> >>>>>> Thanks!  I think having the manual with the main Csound release is
> >> >>>>>> fine.
> >> >>>>>>
> >> >>>>>> For myself, I have so far built the Emscripten release.  I will look
> >> >>>>>> at Android and static-lib version of iOS next.
> >> >>>>>>
> >> >>>>>> steven
> >> >>>>>>
> >> >>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT 
> >> >>>>>> wrote:
> >> >>>>>>> manual and manual-fr are now tagged on github. You can get the built
> >> >>>>>>> packages here:
> >> >>>>>>>
> >> >>>>>>> http://fggp.org/csound/manual-packages/
> >> >>>>>>>
> >> >>>>>>> Francois
> >> >>>>>>>
> >> >>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
> >> >>>>>>>>
> >> >>>>>>>> Maybe the manual packages should be found in the same place (csound
> >> >>>>>>>> repo)
> >> >>>>>>>> than the csound packages, as it was on SF?
> >> >>>>>>>>
> >> >>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
> >> >>>>>>>>>
> >> >>>>>>>>> Hi Francois,
> >> >>>>>>>>>
> >> >>>>>>>>> What do you think about doing a release for the manual on the
> >> >>>>>>>>> csound/manual github repo?
> >> >>>>>>>>>
> >> >>>>>>>>> Thanks!
> >> >>>>>>>>> steven
> >> >>>>>>>>>
> >> >>>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
> >> >>>>>>>>> wrote:
> >> >>>>>>>>>> I'll build the manual in the different formats (10 packages) and
> >> >>>>>>>>>> let
> >> >>>>>>>>>> you get
> >> >>>>>>>>>> it from my repo.
> >> >>>>>>>>>>
> >> >>>>>>>>>> Francois
> >> >>>>>>>>>>
> >> >>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> And apologies, it seems like a change to CMake  I made isn't
> >> >>>>>>>>>>> working
> >> >>>>>>>>>>> on Travis/Linux.  I will revert in both the develop and release
> >> >>>>>>>>>>> branch.
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi 
> >> >>>>>>>>>>> wrote:
> >> >>>>>>>>>>>> Hi All,
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The branch
> >> >>>>>>>>>>>> can
> >> >>>>>>>>>>>> be
> >> >>>>>>>>>>>> pulled by using:
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> git pull
> >> >>>>>>>>>>>> git checkout release/6.07.0
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> I think the version.h has already been set to 6.07.0. Installer
> >> >>>>>>>>>>>> scripts may need to be updated to reflect the new version.
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> I believe we are using Github for the next release.  There's a
> >> >>>>>>>>>>>> bit
> >> >>>>>>>>>>>> of
> >> >>>>>>>>>>>> a chicken and egg issue with setting up a release: on Github,
> >> >>>>>>>>>>>> releases
> >> >>>>>>>>>>>> are associated with tags, but we should wait to tag the release
> >> >>>>>>>>>>>> as
> >> >>>>>>>>>>>> part of "finishing" the release branch as part of git-flow.  I
> >> >>>>>>>>>>>> would
> >> >>>>>>>>>>>> propose: let's build the releases from the release branch and
> >> >>>>>>>>>>>> signal
> >> >>>>>>>>>>>> here when a release is ready.  Once we've all built, I can
> >> >>>>>>>>>>>> finish
> >> >>>>>>>>>>>> the
> >> >>>>>>>>>>>> release branch which will tag the release and merge with
> >> >>>>>>>>>>>> master.  At
> >> >>>>>>>>>>>> that point, we can create the file release on Github and upload
> >> >>>>>>>>>>>> builds
> >> >>>>>>>>>>>> there.  Also to note, Github will auto-generated source
> >> >>>>>>>>>>>> releases
> >> >>>>>>>>>>>> (zip,
> >> >>>>>>>>>>>> bz2 I think) for the release, so we will only have to work on
> >> >>>>>>>>>>>> compiled
> >> >>>>>>>>>>>> releases.
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> One last thing: since our releases often package in the
> >> >>>>>>>>>>>> reference
> >> >>>>>>>>>>>> manual, we should probably first tag and build the manual.  Who
> >> >>>>>>>>>>>> will
> >> >>>>>>>>>>>> do this?
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> Thanks!
> >> >>>>>>>>>>>> steven
> >> >>>
> >> >>>

I managed to get luajit compiled with GCC.  I think everything is good
now except that my OSX system seems to have lost it's install of
Texlive when it updated to El Capitan.  It's downloading now (2.5 gb!)
and should be done in 15-20 minutes.  After that, I'll check that the
iOS and Android manuals are compiling for the release and, if so, will
finish off the release and notify here for uploading.

On Mon, May 16, 2016 at 3:20 PM, Victor Lazzarini
 wrote:
> yes, it was while I was adding the new fft routines, I forgot to tidy it up, but when you
> spotted it, it was fixed.
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 16 May 2016, at 20:13, Rory Walsh  wrote:
>>
>> Thanks guys. It was most likely before Victor tidied it up.
>>
>>
>> On 16 May 2016 at 20:12, Michael Gogins  wrote:
>> OK, I will remove it from the installer then.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Mon, May 16, 2016 at 3:04 PM, Victor Lazzarini
>>  wrote:
>> > I think he is saying this because he had a problem before I moved the header.
>> >
>> > ligeti:csound6 victor$ grep "pffft.h"  */*.h
>> > ligeti:csound6 victor$ grep "pffft.h"  */*.c
>> > OOps/fftlib.c:#include "pffft.h"
>> > OOps/pffft.c:#include "pffft.h"
>> > Opcodes/mp3in.c:#include 
>> >
>> > See? It’s only included in three internal files. It’s nowhere in the public API. It should not be
>> > in /include.
>> >
>> > ========================
>> > Dr Victor Lazzarini
>> > Dean of Arts, Celtic Studies and Philosophy,
>> > Maynooth University,
>> > Maynooth, Co Kildare, Ireland
>> > Tel: 00 353 7086936
>> > Fax: 00 353 1 7086952
>> >
>> >> On 16 May 2016, at 19:46, Michael Gogins  wrote:
>> >>
>> >> That's not what Rory said.
>> >>
>> >> On May 16, 2016 2:35 PM, "Victor Lazzarini"  wrote:
>> >> I actually checked and I had moved the #include. So there is no need to add the
>> >> pffft.c to /include. It’s an internal header, only included in fftlib.c and pffft.c.
>> >>
>> >> ========================
>> >> Dr Victor Lazzarini
>> >> Dean of Arts, Celtic Studies and Philosophy,
>> >> Maynooth University,
>> >> Maynooth, Co Kildare, Ireland
>> >> Tel: 00 353 7086936
>> >> Fax: 00 353 1 7086952
>> >>
>> >> > On 16 May 2016, at 19:29, Victor Lazzarini  wrote:
>> >> >
>> >> > No, the include should be removed from csoundCore.h and added to fftlib.c .
>> >> >
>> >> > I thought I'd done that already, but obviously forgot about it.
>> >> >
>> >> > Victor Lazzarini
>> >> > Dean of Arts, Celtic Studies, and Philosophy
>> >> > Maynooth University
>> >> > Ireland
>> >> >
>> >> >> On 16 May 2016, at 18:13, Michael Gogins  wrote:
>> >> >>
>> >> >> Perhaps pffft.h should be moved from H to include.
>> >> >>
>> >> >> Regards,
>> >> >> Mike
>> >> >>
>> >> >> -----------------------------------------------------
>> >> >> Michael Gogins
>> >> >> Irreducible Productions
>> >> >> http://michaelgogins.tumblr.com
>> >> >> Michael dot Gogins at gmail dot com
>> >> >>
>> >> >>
>> >> >>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wrote:
>> >> >>> Mike, can you include pfftt.h in the include folder with the latest
>> >> >>> installer? I tried your latest installer and noticed that choosing compact
>> >> >>> install will not actually install anything at all. I see from the iss file
>> >> >>> that no files are identified with the Compact installation. Would it be
>> >> >>> possible to use that option to install a very basic version of Csound, i.e.,
>> >> >>> everything needed to run the CLI, plugins and libs, and the Csound docs?
>> >> >>>
>> >> >>>> On 16 May 2016 at 03:45, Steven Yi  wrote:
>> >> >>>>
>> >> >>>> I ran into an issue with Android and minSdkVersions (should be an easy
>> >> >>>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs further
>> >> >>>> investigation).  Will look into this tomorrow.
>> >> >>>>
>> >> >>>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
>> >> >>>>  wrote:
>> >> >>>>> I have built Csound 6.07 for Windows x64 from the release branch, and
>> >> >>>>> it installs and runs. I have one or two minor changes to files in the
>> >> >>>>> release branch, but no source code changes. I am going to do a few
>> >> >>>>> more tests tomorrow.
>> >> >>>>>
>> >> >>>>> Regards,
>> >> >>>>> Mike
>> >> >>>>>
>> >> >>>>> -----------------------------------------------------
>> >> >>>>> Michael Gogins
>> >> >>>>> Irreducible Productions
>> >> >>>>> http://michaelgogins.tumblr.com
>> >> >>>>> Michael dot Gogins at gmail dot com
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi  wrote:
>> >> >>>>>> Hi Francois,
>> >> >>>>>>
>> >> >>>>>> Thanks!  I think having the manual with the main Csound release is
>> >> >>>>>> fine.
>> >> >>>>>>
>> >> >>>>>> For myself, I have so far built the Emscripten release.  I will look
>> >> >>>>>> at Android and static-lib version of iOS next.
>> >> >>>>>>
>> >> >>>>>> steven
>> >> >>>>>>
>> >> >>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT 
>> >> >>>>>> wrote:
>> >> >>>>>>> manual and manual-fr are now tagged on github. You can get the built
>> >> >>>>>>> packages here:
>> >> >>>>>>>
>> >> >>>>>>> http://fggp.org/csound/manual-packages/
>> >> >>>>>>>
>> >> >>>>>>> Francois
>> >> >>>>>>>
>> >> >>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT :
>> >> >>>>>>>>
>> >> >>>>>>>> Maybe the manual packages should be found in the same place (csound
>> >> >>>>>>>> repo)
>> >> >>>>>>>> than the csound packages, as it was on SF?
>> >> >>>>>>>>
>> >> >>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>> >> >>>>>>>>>
>> >> >>>>>>>>> Hi Francois,
>> >> >>>>>>>>>
>> >> >>>>>>>>> What do you think about doing a release for the manual on the
>> >> >>>>>>>>> csound/manual github repo?
>> >> >>>>>>>>>
>> >> >>>>>>>>> Thanks!
>> >> >>>>>>>>> steven
>> >> >>>>>>>>>
>> >> >>>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT 
>> >> >>>>>>>>> wrote:
>> >> >>>>>>>>>> I'll build the manual in the different formats (10 packages) and
>> >> >>>>>>>>>> let
>> >> >>>>>>>>>> you get
>> >> >>>>>>>>>> it from my repo.
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> Francois
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> And apologies, it seems like a change to CMake  I made isn't
>> >> >>>>>>>>>>> working
>> >> >>>>>>>>>>> on Travis/Linux.  I will revert in both the develop and release
>> >> >>>>>>>>>>> branch.
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi 
>> >> >>>>>>>>>>> wrote:
>> >> >>>>>>>>>>>> Hi All,
>> >> >>>>>>>>>>>>
>> >> >>>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The branch
>> >> >>>>>>>>>>>> can
>> >> >>>>>>>>>>>> be
>> >> >>>>>>>>>>>> pulled by using:
>> >> >>>>>>>>>>>>
>> >> >>>>>>>>>>>> git pull
>> >> >>>>>>>>>>>> git checkout release/6.07.0
>> >> >>>>>>>>>>>>
>> >> >>>>>>>>>>>> I think the version.h has already been set to 6.07.0. Installer
>> >> >>>>>>>>>>>> scripts may need to be updated to reflect the new version.
>> >> >>>>>>>>>>>>
>> >> >>>>>>>>>>>> I believe we are using Github for the next release.  There's a
>> >> >>>>>>>>>>>> bit
>> >> >>>>>>>>>>>> of
>> >> >>>>>>>>>>>> a chicken and egg issue with setting up a release: on Github,
>> >> >>>>>>>>>>>> releases
>> >> >>>>>>>>>>>> are associated with tags, but we should wait to tag the release
>> >> >>>>>>>>>>>> as
>> >> >>>>>>>>>>>> part of "finishing" the release branch as part of git-flow.  I
>> >> >>>>>>>>>>>> would
>> >> >>>>>>>>>>>> propose: let's build the releases from the release branch and
>> >> >>>>>>>>>>>> signal
>> >> >>>>>>>>>>>> here when a release is ready.  Once we've all built, I can
>> >> >>>>>>>>>>>> finish
>> >> >>>>>>>>>>>> the
>> >> >>>>>>>>>>>> release branch which will tag the release and merge with
>> >> >>>>>>>>>>>> master.  At
>> >> >>>>>>>>>>>> that point, we can create the file release on Github and upload
>> >> >>>>>>>>>>>> builds
>> >> >>>>>>>>>>>> there.  Also to note, Github will auto-generated source
>> >> >>>>>>>>>>>> releases
>> >> >>>>>>>>>>>> (zip,
>> >> >>>>>>>>>>>> bz2 I think) for the release, so we will only have to work on
>> >> >>>>>>>>>>>> compiled
>> >> >>>>>>>>>>>> releases.
>> >> >>>>>>>>>>>>
>> >> >>>>>>>>>>>> One last thing: since our releases often package in the
>> >> >>>>>>>>>>>> reference
>> >> >>>>>>>>>>>> manual, we should probably first tag and build the manual.  Who
>> >> >>>>>>>>>>>> will
>> >> >>>>>>>>>>>> do this?
>> >> >>>>>>>>>>>>
>> >> >>>>>>>>>>>> Thanks!
>> >> >>>>>>>>>>>> steven
>> >> >>>
>> >> >>>

With gcc? Will it link to clang-based Csound?

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 16 May 2016, at 22:00, Steven Yi  wrote:
> 
> X-Microsoft-Antispam:
>    UriScan:;BCL:0;PCL:0;RULEID:(421252002)(3010002)(71701004)(71702002);SRVR:VI1PR0201MB1885;
> X-Microsoft-Exchange-Diagnostics:
>    1;VI1PR0201MB1885;20:r3WYCIIW7i762/kJvtlKgxSBDxSvb5njRHAfldQIIu+i6+CLbyB+k2+pfKGasV15smXCKG7kFTe6Bcn32hoFvESJDnyScsRm0ZJvZ6AufKJVFRflKJwQsU79BtV3cJ1CPuqDOOQvf3Tbbcci9zhLnKWCyFXOBl3l+bxJNbwy50Ym/sJy9zK6FsxZvbjOBISHdMUc7gX5jbJuLRrJYv2rDbgrNYaGPl5Uk+aEpZU0KRAJm5HVMsGZw9KbeTWsXh5u;4:d2tzayJzv11I2lWiSoUm4EFQ4T4yyj4OgGH950BzrjzFVjkbGrP2yahXYNGjSpWx9vbou0fqCdce+WASbcxUPmnrlzNg3Hk34grRRveS5QR6jwTG27or7gj3fCTNh/H9Z5MNS9mb37fb6xUCHPsxvS2LwhaWpomWV8sjg95UHc7PUVKRNWVfQPX1DyrDHt5BcDYGNBzDxpBGJ4E2AHk6k7+wmuMoYRMMvPvDAIq0yG3oXKXkEo8BXLxWV7HF8oRlJv/bihNtfKzyAbRLPB57+HGZEcyThLio33AedYeSUArjdSfyUlLKLaHAVAb3DrqMYZqX06lbCpDBQ7zJIZUlDe6xRp+XrIifcl6+bFgH+r9Qzztag3P1lV89MlUrYaAG66KhGXh9j77ApS1Bnx4KtV5zRaPrdHuvTP8b3VLqHIYX-Exchange-Antispam-Report-Test: UriScan:;
> X-Exchange-Antispam-Report-CFA-Test:
>    BCL:0;PCL:0;RULEID:(9101531078)(601004)(2401047)(13018025)(13016025)(8121501046)(10201501046)(3002001);SRVR:VI1PR0201MB1885;BCL:0;PCL:0;RULEID:;SRVR:VI1PR0201MB1885;
> X-Microsoft-Exchange-Diagnostics:
>    =?utf-8?B?MTtWSTFQUjAyMDFNQjE4ODU7MjM6S0ZqeXZVaGNjQ0paSWo3bEZxYS9JbVVi?=
> =?utf-8?B?Ty9mbHZzQml2dnZ0aHRBbVBhV3FwTXVzYVJFRDFCWFNVVTkxdDByWHJEMTVi?=
> =?utf-8?B?c3VxWUZNQlArRXRZZW96aTFlY0E4aTIxdm9wR2FIckhlcGNCTjdGMUtEbWVL?=
> =?utf-8?B?amtvbzZUWVd1V3oxZFhuOWRiRFJXL1AyTVJPRFhVTzl3aW1YQysrWkdrdjlM?=
> =?utf-8?B?OFpCRWlkN2FrT1VLUmpyMFhLWktjSE1UczdrTk96dlZxeDc4WmwwZ29PRTVZ?=
> =?utf-8?B?d2FsUWxhYnZXc2ZWcW1mM1NKZDVHeG1wNVZqZzF4VDNacDlJemVaOVBQdTJN?=
> =?utf-8?B?Q3FsTHpQb2s0QlZnRVpBbUZYNkdqVTQwNE93Y2xIUGNHTE04ZTdiei9PR3gr?=
> =?utf-8?B?R2lPRExxalYrYzd1ZjZBd0RreGFZSUhtcktrNHpHRVBZbmMyVmpXcDJvRFlz?=
> =?utf-8?B?SHozcWs2MDRjdmhTMDZxM0kvZkIzbjByYVJ6WEhVbEJFR3QvNlJ4dVdFQm1r?=
> =?utf-8?B?TFRIaHNrbDdXd1phUUw4Y0tVZTdqZ0J3eWpwRmZCWE5Fa2psVWRpMGprQk1s?=
> =?utf-8?B?ZXB1MjNkeitUV0hwTGhrZ0FjMjE4NnFwaVRORXU3RENOZ2lsd2pLSGdGalhX?=
> =?utf-8?B?elE5cXFRVzV1REt2U3JxOFk1WXJGUVB2cDAzcC9aZGVLM2dyVDVXanVDL0RM?=
> =?utf-8?B?U01KTDFtelRUdHRaRER0MFU3Z0FGdEJYU0h0UkpjUkcxS0FnUEZCV2Q5MzU1?=
> =?utf-8?B?eXZoaHZLTnpobmRNZE4rZ2lNbnJrYXZOYUFjMy9yNlU1cStkK1JVczRzdk5u?=
> =?utf-8?B?UVFQYkF6RmZCc3ptOWcyMlljZFc3Z3ZFcGR2MWN5ZndtTWtsak9nRFp1NzVz?=
> =?utf-8?B?a3FWc2UzMldHMVNUV0R4VFI2czdqTXp4Y1RnQ1NHWExseG9nd05wRSt3aUF3?=
> =?utf-8?B?MThzTDg3dXBSaE9zZCtrWlEzbkxTRkh5NG9maUxINzcydUdES0xpbTlUUVU1?=
> =?utf-8?B?cGs3blB1Nm5RRUI0MS9sdDJSbzBWWGlCN1VRWlZhd1RHazVsZ1FHUHRHWnEv?=
> =?utf-8?B?bGJPUnppSlVzTWp6c1ZqN3BBTlJXQnB2dis1VUpKN1RVeHhPMEtzNnhtN0Y2?=
> =?utf-8?B?aGRNeVBrSVI4bmVmL0dFQm50VTNzc0NLKzlDOENwOUlZQWY1Nytod0FaVjBC?=
> =?utf-8?B?cXFnaDVQWGxxSGFxZkZyS1ZhVkloM0twdWI3UU5jQnVtaWNJaHV1UGpKZklw?=
> =?utf-8?B?MlF4dlZQODBHcTB1UmZmQjZFZ2tRdXR5a3Z5VEVxS3FucGd5WS9GNVZNcGI0?=
> =?utf-8?B?SEVZaFlxQUU5RnRQYlVaMlpRcXQzUEpKVG5NYWcwZFMzanlBVERrdXlBckda?=
> =?utf-8?B?cFQ4SGsxcGF3MGdOajNuL2NYVWhwOUx1MWtnUVo2MHhjNEcxM2JtaytYd1RQ?=
> =?utf-8?B?VHlRRFY4ZFE0NnNuWEpyRURLVm9QeDFsdnNVdGt4V1dvMk1acXBUcE4zUm9T?=
> =?utf-8?B?cVh0NWZtdjVjTHJIcHlvR2hYL3JxWXJqdkp6Y3gzUFVvUkZlVXlUVFVoeThN?=
> =?utf-8?B?T2VJdElMMHl3TVdURGZOSkJJY2FDMVFvVVlOSFJGT0VPQzRrVi9GTVVESkMv?=
> =?utf-8?B?MXVYMHRNUlpneHNvTUdjNGU5VVREby9MR0pnRkUvUjQ3UmJJUFVRd21CTW5w?=
> =?utf-8?B?OFFWZzd3dFNWRXVoVWVHUlNGWUJVaGR6OXh5QTRxeTdHZnJqa2NCSE51eXdJ?=
> =?utf-8?B?ckxTQXgrRDRCaFJMWk5kTGlHTGVPbnpMM2kyRm55anhIWGZiQWNocjRRRDJV?=
> =?utf-8?B?UkpqdkVFUnZ3WnJBd09kWEN6dkRBbmNDbnJkUUNwSng3R010WWptM1RqZmtO?=
> =?utf-8?B?dWZxOHkyQUtrT1lkYWJBVS9SRmNpSzh2b3ZJN0F0aStKTUxlSkM4d3N2dndr?=
> =?utf-8?B?Rk80cFJzaG8yZW9pQWNXOENFRVJhMVJYNG5ldnpWQ2M3bE96QzlRMjQxNWl4?=
> =?utf-8?B?MDJlUmpCeGQ1ODJ3SFkvSDFueFJVOUxEVGgvKzdRUzhEdXVUZThSNmJXdkxu?=
> =?utf-8?B?WXZYU1NnQUJmNkJsVVg0S1RjM1l0Sk5mQzM3NHFlcnkwQXhEWlRvNTFZbC9N?=
> =?utf-8?B?RVEzMm5pbUdtK25vbFl0L0diQXlhNktjRzZ3OVpnRTlLZURnSmlBUjd6dnRw?=
> =?utf-8?B?SUN1OXlENnNPTEkxd0htV3RsdGNxbXc9PQ==?=
> X-Microsoft-Exchange-Diagnostics:
>    1;VI1PR0201MB1885;5:EY/Cj4S8FZb0OwNEWsqAFBW5UHN3TFN+IlQjPUF1F6xYd5sR8XPFSHSiHBvxPYoEH8cHhtDaZKpiqoEXIwPetdVtttcH84LtHEPp/i/lvtAbBULY+7p7r2HnTECdOJbIS4eYfa7SlZ9RqPUo+1gNDg==;24:mNdvUPEfGSyYrOPtJbStEjqthITeTYG8r3wwzbIC6NqyUYBR5gyy2wY0poWrCxl+Bw37xQ9cMSZYvHJ8SNBK3OSjEcwaA1NZNyWMuuj/CX0=;7:liJQNWtffHFiSZ2fb/HdIQCsMLIRKl8MGv5/yPrL/hrFSr+t9PpQPCFFzVNIsiczVrH4gOFryJZCZZkSp0qVWmk3yKmkKRenVgtPoK5fp0tITgvAPq2QysPppqFKAm6iAqwIz1mfb5A3XqzrZIJtzYr8sIjB4dLMMGxaUo13ZPBSRrm+cLdhk3uEztTTSci1
> SpamDiagnosticOutput: 1:23
> SpamDiagnosticMetadata: NSPM
> X-OriginatorOrg: maynoothuniversity.onmicrosoft.com
> X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 May 2016 21:00:37.1219 (UTC)
> X-MS-Exchange-CrossTenant-Id: 1454f5cc-bb35-4685-bbd9-8621fd8055c9
> X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
> X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0201MB1885
> X-MS-Exchange-CrossPremises-OriginalClientIPAddress: 193.1.219.120
> X-MS-Exchange-CrossPremises-AuthSource: DB3FFO11FD009.protection.gbl
> X-MS-Exchange-CrossPremises-AuthAs: Anonymous
> X-MS-Exchange-CrossPremises-AVStamp-Service: 1.0
> X-MS-Exchange-CrossPremises-SCL: 1
> X-MS-Exchange-CrossPremises-Antispam-ScanContext:    DIR:Incoming;SFV:NSPM;SKIP:0;
> X-MS-Exchange-CrossPremises-Processed-By-Journaling: Journal Agent
> X-OrganizationHeadersPreserved: VI1PR0201MB1885.eurprd02.prod.outlook.com
> 
> I managed to get luajit compiled with GCC.  I think everything is good
> now except that my OSX system seems to have lost it's install of
> Texlive when it updated to El Capitan.  It's downloading now (2.5 gb!)
> and should be done in 15-20 minutes.  After that, I'll check that the
> iOS and Android manuals are compiling for the release and, if so, will
> finish off the release and notify here for uploading.
> 
> On Mon, May 16, 2016 at 3:20 PM, Victor Lazzarini
>  wrote:
>> yes, it was while I was adding the new fft routines, I forgot to tidy it =
> up, but when you
>> spotted it, it was fixed.
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>> 
>>> On 16 May 2016, at 20:13, Rory Walsh  wrote:
>>> 
>>> Thanks guys. It was most likely before Victor tidied it up.
>>> 
>>> 
>>> On 16 May 2016 at 20:12, Michael Gogins  wrote=
> :
>>> OK, I will remove it from the installer then.
>>> 
>>> Regards,
>>> Mike
>>> 
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>> 
>>> 
>>> On Mon, May 16, 2016 at 3:04 PM, Victor Lazzarini
>>>  wrote:
>>>> I think he is saying this because he had a problem before I moved the =
> header.
>>>> 
>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.h
>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.c
>>>> OOps/fftlib.c:#include "pffft.h"
>>>> OOps/pffft.c:#include "pffft.h"
>>>> Opcodes/mp3in.c:#include 
>>>> 
>>>> See? It=E2=80=99s only included in three internal files. It=E2=80=99s =
> nowhere in the public API. It should not be
>>>> in /include.
>>>> 
>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> =3D
>>>> Dr Victor Lazzarini
>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>> 
>>>>> On 16 May 2016, at 19:46, Michael Gogins  w=
> rote:
>>>>> 
>>>>> That's not what Rory said.
>>>>> 
>>>>> On May 16, 2016 2:35 PM, "Victor Lazzarini" > wrote:
>>>>> I actually checked and I had moved the #include. So there is no need =
> to add the
>>>>> pffft.c to /include. It=E2=80=99s an internal header, only included i=
> n fftlib.c and pffft.c.
>>>>> 
>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> =3D
>>>>> Dr Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>> Maynooth University,
>>>>> Maynooth, Co Kildare, Ireland
>>>>> Tel: 00 353 7086936
>>>>> Fax: 00 353 1 7086952
>>>>> 
>>>>>> On 16 May 2016, at 19:29, Victor Lazzarini  e> wrote:
>>>>>> 
>>>>>> No, the include should be removed from csoundCore.h and added to ff=
> tlib.c .
>>>>>> 
>>>>>> I thought I'd done that already, but obviously forgot about it.
>>>>>> 
>>>>>> Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>>> Maynooth University
>>>>>> Ireland
>>>>>> 
>>>>>>> On 16 May 2016, at 18:13, Michael Gogins > wrote:
>>>>>>> 
>>>>>>> Perhaps pffft.h should be moved from H to include.
>>>>>>> 
>>>>>>> Regards,
>>>>>>> Mike
>>>>>>> 
>>>>>>> -----------------------------------------------------
>>>>>>> Michael Gogins
>>>>>>> Irreducible Productions
>>>>>>> http://michaelgogins.tumblr.com
>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>> 
>>>>>>> 
>>>>>>>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wr=
> ote:
>>>>>>>> Mike, can you include pfftt.h in the include folder with the late=
> st
>>>>>>>> installer? I tried your latest installer and noticed that choosin=
> g compact
>>>>>>>> install will not actually install anything at all. I see from the=
> iss file
>>>>>>>> that no files are identified with the Compact installation. Would=
> it be
>>>>>>>> possible to use that option to install a very basic version of Cs=
> ound, i.e.,
>>>>>>>> everything needed to run the CLI, plugins and libs, and the Csoun=
> d docs?
>>>>>>>> 
>>>>>>>>> On 16 May 2016 at 03:45, Steven Yi  wrote:
>>>>>>>>> 
>>>>>>>>> I ran into an issue with Android and minSdkVersions (should be a=
> n easy
>>>>>>>>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs fur=
> ther
>>>>>>>>> investigation).  Will look into this tomorrow.
>>>>>>>>> 
>>>>>>>>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
>>>>>>>>>  wrote:
>>>>>>>>>> I have built Csound 6.07 for Windows x64 from the release branc=
> h, and
>>>>>>>>>> it installs and runs. I have one or two minor changes to files =
> in the
>>>>>>>>>> release branch, but no source code changes. I am going to do a =
> few
>>>>>>>>>> more tests tomorrow.
>>>>>>>>>> 
>>>>>>>>>> Regards,
>>>>>>>>>> Mike
>>>>>>>>>> 
>>>>>>>>>> -----------------------------------------------------
>>>>>>>>>> Michael Gogins
>>>>>>>>>> Irreducible Productions
>>>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi > wrote:
>>>>>>>>>>> Hi Francois,
>>>>>>>>>>> 
>>>>>>>>>>> Thanks!  I think having the manual with the main Csound releas=
> e is
>>>>>>>>>>> fine.
>>>>>>>>>>> 
>>>>>>>>>>> For myself, I have so far built the Emscripten release.  I wil=
> l look
>>>>>>>>>>> at Android and static-lib version of iOS next.
>>>>>>>>>>> 
>>>>>>>>>>> steven
>>>>>>>>>>> 
>>>>>>>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT  l.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>> manual and manual-fr are now tagged on github. You can get th=
> e built
>>>>>>>>>>>> packages here:
>>>>>>>>>>>> 
>>>>>>>>>>>> http://fggp.org/csound/manual-packages/
>>>>>>>>>>>> 
>>>>>>>>>>>> Francois
>>>>>>>>>>>> 
>>>>>>>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT > :
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Maybe the manual packages should be found in the same place =
> (csound
>>>>>>>>>>>>> repo)
>>>>>>>>>>>>> than the csound packages, as it was on SF?
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Hi Francois,
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> What do you think about doing a release for the manual on t=
> he
>>>>>>>>>>>>>> csound/manual github repo?
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>> steven
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT  mail.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> I'll build the manual in the different formats (10 package=
> s) and
>>>>>>>>>>>>>>> let
>>>>>>>>>>>>>>> you get
>>>>>>>>>>>>>>> it from my repo.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Francois
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> And apologies, it seems like a change to CMake  I made is=
> n't
>>>>>>>>>>>>>>>> working
>>>>>>>>>>>>>>>> on Travis/Linux.  I will revert in both the develop and r=
> elease
>>>>>>>>>>>>>>>> branch.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi  l.com>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> Hi All,
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The=
> branch
>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>> be
>>>>>>>>>>>>>>>>> pulled by using:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> git pull
>>>>>>>>>>>>>>>>> git checkout release/6.07.0
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> I think the version.h has already been set to 6.07.0. In=
> staller
>>>>>>>>>>>>>>>>> scripts may need to be updated to reflect the new versio=
> n.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> I believe we are using Github for the next release.  The=
> re's a
>>>>>>>>>>>>>>>>> bit
>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>> a chicken and egg issue with setting up a release: on Gi=
> thub,
>>>>>>>>>>>>>>>>> releases
>>>>>>>>>>>>>>>>> are associated with tags, but we should wait to tag the =
> release
>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>> part of "finishing" the release branch as part of git-fl=
> ow.  I
>>>>>>>>>>>>>>>>> would
>>>>>>>>>>>>>>>>> propose: let's build the releases from the release branc=
> h and
>>>>>>>>>>>>>>>>> signal
>>>>>>>>>>>>>>>>> here when a release is ready.  Once we've all built, I c=
> an
>>>>>>>>>>>>>>>>> finish
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> release branch which will tag the release and merge with
>>>>>>>>>>>>>>>>> master.  At
>>>>>>>>>>>>>>>>> that point, we can create the file release on Github and=
> upload
>>>>>>>>>>>>>>>>> builds
>>>>>>>>>>>>>>>>> there.  Also to note, Github will auto-generated source
>>>>>>>>>>>>>>>>> releases
>>>>>>>>>>>>>>>>> (zip,
>>>>>>>>>>>>>>>>> bz2 I think) for the release, so we will only have to wo=
> rk on
>>>>>>>>>>>>>>>>> compiled
>>>>>>>>>>>>>>>>> releases.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> One last thing: since our releases often package in the
>>>>>>>>>>>>>>>>> reference
>>>>>>>>>>>>>>>>> manual, we should probably first tag and build the manua=
> l.  Who
>>>>>>>>>>>>>>>>> will
>>>>>>>>>>>>>>>>> do this?
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>>> steven

Seems to have linked alright.

I've gone ahead and finished the release.  The summary of actions from
git-flow are:

Summary of actions:
- Release branch 'release/6.07.0' has been merged into 'master'
- The release was tagged '6.07.0'
- Release tag '6.07.0' has been back-merged into 'develop'
- Release branch 'release/6.07.0' has been locally deleted; it has
been remotely deleted from 'origin'
- You are now on branch 'develop'

On github, I have setup a draft under file releases for 6.07.0.  I
will iOS, Android, and Emscripten builds now.  Everyone here dealing
with releases should have edit access to the release and in there you
can upload by dragging and dropping the artifact in the browser.

On Mon, May 16, 2016 at 5:37 PM, Victor Lazzarini
 wrote:
> With gcc? Will it link to clang-based Csound?
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
>> On 16 May 2016, at 22:00, Steven Yi  wrote:
>>
>> X-Microsoft-Antispam:
>>    UriScan:;BCL:0;PCL:0;RULEID:(421252002)(3010002)(71701004)(71702002);SRVR:VI1PR0201MB1885;
>> X-Microsoft-Exchange-Diagnostics:
>>    1;VI1PR0201MB1885;20:r3WYCIIW7i762/kJvtlKgxSBDxSvb5njRHAfldQIIu+i6+CLbyB+k2+pfKGasV15smXCKG7kFTe6Bcn32hoFvESJDnyScsRm0ZJvZ6AufKJVFRflKJwQsU79BtV3cJ1CPuqDOOQvf3Tbbcci9zhLnKWCyFXOBl3l+bxJNbwy50Ym/sJy9zK6FsxZvbjOBISHdMUc7gX5jbJuLRrJYv2rDbgrNYaGPl5Uk+aEpZU0KRAJm5HVMsGZw9KbeTWsXh5u;4:d2tzayJzv11I2lWiSoUm4EFQ4T4yyj4OgGH950BzrjzFVjkbGrP2yahXYNGjSpWx9vbou0fqCdce+WASbcxUPmnrlzNg3Hk34grRRveS5QR6jwTG27or7gj3fCTNh/H9Z5MNS9mb37fb6xUCHPsxvS2LwhaWpomWV8sjg95UHc7PUVKRNWVfQPX1DyrDHt5BcDYGNBzDxpBGJ4E2AHk6k7+wmuMoYRMMvPvDAIq0yG3oXKXkEo8BXLxWV7HF8oRlJv/bihNtfKzyAbRLPB57+HGZEcyThLio33AedYeSUArjdSfyUlLKLaHAVAb3DrqMYZqX06lbCpDBQ7zJIZUlDe6xRp+XrIifcl6+bFgH+r9Qzztag3P1lV89MlUrYaAG66KhGXh9j77ApS1Bnx4KtV5zRaPrdHuvTP8b3VLqHIYX-Exchange-Antispam-Report-Test: UriScan:;
>> X-Exchange-Antispam-Report-CFA-Test:
>>    BCL:0;PCL:0;RULEID:(9101531078)(601004)(2401047)(13018025)(13016025)(8121501046)(10201501046)(3002001);SRVR:VI1PR0201MB1885;BCL:0;PCL:0;RULEID:;SRVR:VI1PR0201MB1885;
>> X-Microsoft-Exchange-Diagnostics:
>>    =?utf-8?B?MTtWSTFQUjAyMDFNQjE4ODU7MjM6S0ZqeXZVaGNjQ0paSWo3bEZxYS9JbVVi?=
>> =?utf-8?B?Ty9mbHZzQml2dnZ0aHRBbVBhV3FwTXVzYVJFRDFCWFNVVTkxdDByWHJEMTVi?=
>> =?utf-8?B?c3VxWUZNQlArRXRZZW96aTFlY0E4aTIxdm9wR2FIckhlcGNCTjdGMUtEbWVL?=
>> =?utf-8?B?amtvbzZUWVd1V3oxZFhuOWRiRFJXL1AyTVJPRFhVTzl3aW1YQysrWkdrdjlM?=
>> =?utf-8?B?OFpCRWlkN2FrT1VLUmpyMFhLWktjSE1UczdrTk96dlZxeDc4WmwwZ29PRTVZ?=
>> =?utf-8?B?d2FsUWxhYnZXc2ZWcW1mM1NKZDVHeG1wNVZqZzF4VDNacDlJemVaOVBQdTJN?=
>> =?utf-8?B?Q3FsTHpQb2s0QlZnRVpBbUZYNkdqVTQwNE93Y2xIUGNHTE04ZTdiei9PR3gr?=
>> =?utf-8?B?R2lPRExxalYrYzd1ZjZBd0RreGFZSUhtcktrNHpHRVBZbmMyVmpXcDJvRFlz?=
>> =?utf-8?B?SHozcWs2MDRjdmhTMDZxM0kvZkIzbjByYVJ6WEhVbEJFR3QvNlJ4dVdFQm1r?=
>> =?utf-8?B?TFRIaHNrbDdXd1phUUw4Y0tVZTdqZ0J3eWpwRmZCWE5Fa2psVWRpMGprQk1s?=
>> =?utf-8?B?ZXB1MjNkeitUV0hwTGhrZ0FjMjE4NnFwaVRORXU3RENOZ2lsd2pLSGdGalhX?=
>> =?utf-8?B?elE5cXFRVzV1REt2U3JxOFk1WXJGUVB2cDAzcC9aZGVLM2dyVDVXanVDL0RM?=
>> =?utf-8?B?U01KTDFtelRUdHRaRER0MFU3Z0FGdEJYU0h0UkpjUkcxS0FnUEZCV2Q5MzU1?=
>> =?utf-8?B?eXZoaHZLTnpobmRNZE4rZ2lNbnJrYXZOYUFjMy9yNlU1cStkK1JVczRzdk5u?=
>> =?utf-8?B?UVFQYkF6RmZCc3ptOWcyMlljZFc3Z3ZFcGR2MWN5ZndtTWtsak9nRFp1NzVz?=
>> =?utf-8?B?a3FWc2UzMldHMVNUV0R4VFI2czdqTXp4Y1RnQ1NHWExseG9nd05wRSt3aUF3?=
>> =?utf-8?B?MThzTDg3dXBSaE9zZCtrWlEzbkxTRkh5NG9maUxINzcydUdES0xpbTlUUVU1?=
>> =?utf-8?B?cGs3blB1Nm5RRUI0MS9sdDJSbzBWWGlCN1VRWlZhd1RHazVsZ1FHUHRHWnEv?=
>> =?utf-8?B?bGJPUnppSlVzTWp6c1ZqN3BBTlJXQnB2dis1VUpKN1RVeHhPMEtzNnhtN0Y2?=
>> =?utf-8?B?aGRNeVBrSVI4bmVmL0dFQm50VTNzc0NLKzlDOENwOUlZQWY1Nytod0FaVjBC?=
>> =?utf-8?B?cXFnaDVQWGxxSGFxZkZyS1ZhVkloM0twdWI3UU5jQnVtaWNJaHV1UGpKZklw?=
>> =?utf-8?B?MlF4dlZQODBHcTB1UmZmQjZFZ2tRdXR5a3Z5VEVxS3FucGd5WS9GNVZNcGI0?=
>> =?utf-8?B?SEVZaFlxQUU5RnRQYlVaMlpRcXQzUEpKVG5NYWcwZFMzanlBVERrdXlBckda?=
>> =?utf-8?B?cFQ4SGsxcGF3MGdOajNuL2NYVWhwOUx1MWtnUVo2MHhjNEcxM2JtaytYd1RQ?=
>> =?utf-8?B?VHlRRFY4ZFE0NnNuWEpyRURLVm9QeDFsdnNVdGt4V1dvMk1acXBUcE4zUm9T?=
>> =?utf-8?B?cVh0NWZtdjVjTHJIcHlvR2hYL3JxWXJqdkp6Y3gzUFVvUkZlVXlUVFVoeThN?=
>> =?utf-8?B?T2VJdElMMHl3TVdURGZOSkJJY2FDMVFvVVlOSFJGT0VPQzRrVi9GTVVESkMv?=
>> =?utf-8?B?MXVYMHRNUlpneHNvTUdjNGU5VVREby9MR0pnRkUvUjQ3UmJJUFVRd21CTW5w?=
>> =?utf-8?B?OFFWZzd3dFNWRXVoVWVHUlNGWUJVaGR6OXh5QTRxeTdHZnJqa2NCSE51eXdJ?=
>> =?utf-8?B?ckxTQXgrRDRCaFJMWk5kTGlHTGVPbnpMM2kyRm55anhIWGZiQWNocjRRRDJV?=
>> =?utf-8?B?UkpqdkVFUnZ3WnJBd09kWEN6dkRBbmNDbnJkUUNwSng3R010WWptM1RqZmtO?=
>> =?utf-8?B?dWZxOHkyQUtrT1lkYWJBVS9SRmNpSzh2b3ZJN0F0aStKTUxlSkM4d3N2dndr?=
>> =?utf-8?B?Rk80cFJzaG8yZW9pQWNXOENFRVJhMVJYNG5ldnpWQ2M3bE96QzlRMjQxNWl4?=
>> =?utf-8?B?MDJlUmpCeGQ1ODJ3SFkvSDFueFJVOUxEVGgvKzdRUzhEdXVUZThSNmJXdkxu?=
>> =?utf-8?B?WXZYU1NnQUJmNkJsVVg0S1RjM1l0Sk5mQzM3NHFlcnkwQXhEWlRvNTFZbC9N?=
>> =?utf-8?B?RVEzMm5pbUdtK25vbFl0L0diQXlhNktjRzZ3OVpnRTlLZURnSmlBUjd6dnRw?=
>> =?utf-8?B?SUN1OXlENnNPTEkxd0htV3RsdGNxbXc9PQ==?=
>> X-Microsoft-Exchange-Diagnostics:
>>    1;VI1PR0201MB1885;5:EY/Cj4S8FZb0OwNEWsqAFBW5UHN3TFN+IlQjPUF1F6xYd5sR8XPFSHSiHBvxPYoEH8cHhtDaZKpiqoEXIwPetdVtttcH84LtHEPp/i/lvtAbBULY+7p7r2HnTECdOJbIS4eYfa7SlZ9RqPUo+1gNDg==;24:mNdvUPEfGSyYrOPtJbStEjqthITeTYG8r3wwzbIC6NqyUYBR5gyy2wY0poWrCxl+Bw37xQ9cMSZYvHJ8SNBK3OSjEcwaA1NZNyWMuuj/CX0=;7:liJQNWtffHFiSZ2fb/HdIQCsMLIRKl8MGv5/yPrL/hrFSr+t9PpQPCFFzVNIsiczVrH4gOFryJZCZZkSp0qVWmk3yKmkKRenVgtPoK5fp0tITgvAPq2QysPppqFKAm6iAqwIz1mfb5A3XqzrZIJtzYr8sIjB4dLMMGxaUo13ZPBSRrm+cLdhk3uEztTTSci1
>> SpamDiagnosticOutput: 1:23
>> SpamDiagnosticMetadata: NSPM
>> X-OriginatorOrg: maynoothuniversity.onmicrosoft.com
>> X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 May 2016 21:00:37.1219 (UTC)
>> X-MS-Exchange-CrossTenant-Id: 1454f5cc-bb35-4685-bbd9-8621fd8055c9
>> X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
>> X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0201MB1885
>> X-MS-Exchange-CrossPremises-OriginalClientIPAddress: 193.1.219.120
>> X-MS-Exchange-CrossPremises-AuthSource: DB3FFO11FD009.protection.gbl
>> X-MS-Exchange-CrossPremises-AuthAs: Anonymous
>> X-MS-Exchange-CrossPremises-AVStamp-Service: 1.0
>> X-MS-Exchange-CrossPremises-SCL: 1
>> X-MS-Exchange-CrossPremises-Antispam-ScanContext:    DIR:Incoming;SFV:NSPM;SKIP:0;
>> X-MS-Exchange-CrossPremises-Processed-By-Journaling: Journal Agent
>> X-OrganizationHeadersPreserved: VI1PR0201MB1885.eurprd02.prod.outlook.com
>>
>> I managed to get luajit compiled with GCC.  I think everything is good
>> now except that my OSX system seems to have lost it's install of
>> Texlive when it updated to El Capitan.  It's downloading now (2.5 gb!)
>> and should be done in 15-20 minutes.  After that, I'll check that the
>> iOS and Android manuals are compiling for the release and, if so, will
>> finish off the release and notify here for uploading.
>>
>> On Mon, May 16, 2016 at 3:20 PM, Victor Lazzarini
>>  wrote:
>>> yes, it was while I was adding the new fft routines, I forgot to tidy it =
>> up, but when you
>>> spotted it, it was fixed.
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>>> On 16 May 2016, at 20:13, Rory Walsh  wrote:
>>>>
>>>> Thanks guys. It was most likely before Victor tidied it up.
>>>>
>>>>
>>>> On 16 May 2016 at 20:12, Michael Gogins  wrote=
>> :
>>>> OK, I will remove it from the installer then.
>>>>
>>>> Regards,
>>>> Mike
>>>>
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>> On Mon, May 16, 2016 at 3:04 PM, Victor Lazzarini
>>>>  wrote:
>>>>> I think he is saying this because he had a problem before I moved the =
>> header.
>>>>>
>>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.h
>>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.c
>>>>> OOps/fftlib.c:#include "pffft.h"
>>>>> OOps/pffft.c:#include "pffft.h"
>>>>> Opcodes/mp3in.c:#include 
>>>>>
>>>>> See? It=E2=80=99s only included in three internal files. It=E2=80=99s =
>> nowhere in the public API. It should not be
>>>>> in /include.
>>>>>
>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>> =3D
>>>>> Dr Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>> Maynooth University,
>>>>> Maynooth, Co Kildare, Ireland
>>>>> Tel: 00 353 7086936
>>>>> Fax: 00 353 1 7086952
>>>>>
>>>>>> On 16 May 2016, at 19:46, Michael Gogins  w=
>> rote:
>>>>>>
>>>>>> That's not what Rory said.
>>>>>>
>>>>>> On May 16, 2016 2:35 PM, "Victor Lazzarini" >> wrote:
>>>>>> I actually checked and I had moved the #include. So there is no need =
>> to add the
>>>>>> pffft.c to /include. It=E2=80=99s an internal header, only included i=
>> n fftlib.c and pffft.c.
>>>>>>
>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>> =3D
>>>>>> Dr Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>> Maynooth University,
>>>>>> Maynooth, Co Kildare, Ireland
>>>>>> Tel: 00 353 7086936
>>>>>> Fax: 00 353 1 7086952
>>>>>>
>>>>>>> On 16 May 2016, at 19:29, Victor Lazzarini > e> wrote:
>>>>>>>
>>>>>>> No, the include should be removed from csoundCore.h and added to ff=
>> tlib.c .
>>>>>>>
>>>>>>> I thought I'd done that already, but obviously forgot about it.
>>>>>>>
>>>>>>> Victor Lazzarini
>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>>>> Maynooth University
>>>>>>> Ireland
>>>>>>>
>>>>>>>> On 16 May 2016, at 18:13, Michael Gogins >> wrote:
>>>>>>>>
>>>>>>>> Perhaps pffft.h should be moved from H to include.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Mike
>>>>>>>>
>>>>>>>> -----------------------------------------------------
>>>>>>>> Michael Gogins
>>>>>>>> Irreducible Productions
>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wr=
>> ote:
>>>>>>>>> Mike, can you include pfftt.h in the include folder with the late=
>> st
>>>>>>>>> installer? I tried your latest installer and noticed that choosin=
>> g compact
>>>>>>>>> install will not actually install anything at all. I see from the=
>> iss file
>>>>>>>>> that no files are identified with the Compact installation. Would=
>> it be
>>>>>>>>> possible to use that option to install a very basic version of Cs=
>> ound, i.e.,
>>>>>>>>> everything needed to run the CLI, plugins and libs, and the Csoun=
>> d docs?
>>>>>>>>>
>>>>>>>>>> On 16 May 2016 at 03:45, Steven Yi  wrote:
>>>>>>>>>>
>>>>>>>>>> I ran into an issue with Android and minSdkVersions (should be a=
>> n easy
>>>>>>>>>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs fur=
>> ther
>>>>>>>>>> investigation).  Will look into this tomorrow.
>>>>>>>>>>
>>>>>>>>>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
>>>>>>>>>>  wrote:
>>>>>>>>>>> I have built Csound 6.07 for Windows x64 from the release branc=
>> h, and
>>>>>>>>>>> it installs and runs. I have one or two minor changes to files =
>> in the
>>>>>>>>>>> release branch, but no source code changes. I am going to do a =
>> few
>>>>>>>>>>> more tests tomorrow.
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Mike
>>>>>>>>>>>
>>>>>>>>>>> -----------------------------------------------------
>>>>>>>>>>> Michael Gogins
>>>>>>>>>>> Irreducible Productions
>>>>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi >> wrote:
>>>>>>>>>>>> Hi Francois,
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks!  I think having the manual with the main Csound releas=
>> e is
>>>>>>>>>>>> fine.
>>>>>>>>>>>>
>>>>>>>>>>>> For myself, I have so far built the Emscripten release.  I wil=
>> l look
>>>>>>>>>>>> at Android and static-lib version of iOS next.
>>>>>>>>>>>>
>>>>>>>>>>>> steven
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT > l.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> manual and manual-fr are now tagged on github. You can get th=
>> e built
>>>>>>>>>>>>> packages here:
>>>>>>>>>>>>>
>>>>>>>>>>>>> http://fggp.org/csound/manual-packages/
>>>>>>>>>>>>>
>>>>>>>>>>>>> Francois
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT >> :
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Maybe the manual packages should be found in the same place =
>> (csound
>>>>>>>>>>>>>> repo)
>>>>>>>>>>>>>> than the csound packages, as it was on SF?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Francois,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> What do you think about doing a release for the manual on t=
>> he
>>>>>>>>>>>>>>> csound/manual github repo?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>> steven
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT > mail.com>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> I'll build the manual in the different formats (10 package=
>> s) and
>>>>>>>>>>>>>>>> let
>>>>>>>>>>>>>>>> you get
>>>>>>>>>>>>>>>> it from my repo.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Francois
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> And apologies, it seems like a change to CMake  I made is=
>> n't
>>>>>>>>>>>>>>>>> working
>>>>>>>>>>>>>>>>> on Travis/Linux.  I will revert in both the develop and r=
>> elease
>>>>>>>>>>>>>>>>> branch.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi > l.com>
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> Hi All,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The=
>> branch
>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>> be
>>>>>>>>>>>>>>>>>> pulled by using:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> git pull
>>>>>>>>>>>>>>>>>> git checkout release/6.07.0
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I think the version.h has already been set to 6.07.0. In=
>> staller
>>>>>>>>>>>>>>>>>> scripts may need to be updated to reflect the new versio=
>> n.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I believe we are using Github for the next release.  The=
>> re's a
>>>>>>>>>>>>>>>>>> bit
>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>> a chicken and egg issue with setting up a release: on Gi=
>> thub,
>>>>>>>>>>>>>>>>>> releases
>>>>>>>>>>>>>>>>>> are associated with tags, but we should wait to tag the =
>> release
>>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>>> part of "finishing" the release branch as part of git-fl=
>> ow.  I
>>>>>>>>>>>>>>>>>> would
>>>>>>>>>>>>>>>>>> propose: let's build the releases from the release branc=
>> h and
>>>>>>>>>>>>>>>>>> signal
>>>>>>>>>>>>>>>>>> here when a release is ready.  Once we've all built, I c=
>> an
>>>>>>>>>>>>>>>>>> finish
>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>> release branch which will tag the release and merge with
>>>>>>>>>>>>>>>>>> master.  At
>>>>>>>>>>>>>>>>>> that point, we can create the file release on Github and=
>> upload
>>>>>>>>>>>>>>>>>> builds
>>>>>>>>>>>>>>>>>> there.  Also to note, Github will auto-generated source
>>>>>>>>>>>>>>>>>> releases
>>>>>>>>>>>>>>>>>> (zip,
>>>>>>>>>>>>>>>>>> bz2 I think) for the release, so we will only have to wo=
>> rk on
>>>>>>>>>>>>>>>>>> compiled
>>>>>>>>>>>>>>>>>> releases.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> One last thing: since our releases often package in the
>>>>>>>>>>>>>>>>>> reference
>>>>>>>>>>>>>>>>>> manual, we should probably first tag and build the manua=
>> l.  Who
>>>>>>>>>>>>>>>>>> will
>>>>>>>>>>>>>>>>>> do this?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>>>> steven

Ok, uploaded my packages and added release notes.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 16 May 2016, at 22:40, Steven Yi  wrote:
> 
> Seems to have linked alright.
> 
> I've gone ahead and finished the release.  The summary of actions from
> git-flow are:
> 
> Summary of actions:
> - Release branch 'release/6.07.0' has been merged into 'master'
> - The release was tagged '6.07.0'
> - Release tag '6.07.0' has been back-merged into 'develop'
> - Release branch 'release/6.07.0' has been locally deleted; it has
> been remotely deleted from 'origin'
> - You are now on branch 'develop'
> 
> On github, I have setup a draft under file releases for 6.07.0.  I
> will iOS, Android, and Emscripten builds now.  Everyone here dealing
> with releases should have edit access to the release and in there you
> can upload by dragging and dropping the artifact in the browser.
> 
> On Mon, May 16, 2016 at 5:37 PM, Victor Lazzarini
>  wrote:
>> With gcc? Will it link to clang-based Csound?
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>>> On 16 May 2016, at 22:00, Steven Yi  wrote:
>>> 
>>> X-Microsoft-Antispam:
>>>   UriScan:;BCL:0;PCL:0;RULEID:(421252002)(3010002)(71701004)(71702002);SRVR:VI1PR0201MB1885;
>>> X-Microsoft-Exchange-Diagnostics:
>>>   1;VI1PR0201MB1885;20:r3WYCIIW7i762/kJvtlKgxSBDxSvb5njRHAfldQIIu+i6+CLbyB+k2+pfKGasV15smXCKG7kFTe6Bcn32hoFvESJDnyScsRm0ZJvZ6AufKJVFRflKJwQsU79BtV3cJ1CPuqDOOQvf3Tbbcci9zhLnKWCyFXOBl3l+bxJNbwy50Ym/sJy9zK6FsxZvbjOBISHdMUc7gX5jbJuLRrJYv2rDbgrNYaGPl5Uk+aEpZU0KRAJm5HVMsGZw9KbeTWsXh5u;4:d2tzayJzv11I2lWiSoUm4EFQ4T4yyj4OgGH950BzrjzFVjkbGrP2yahXYNGjSpWx9vbou0fqCdce+WASbcxUPmnrlzNg3Hk34grRRveS5QR6jwTG27or7gj3fCTNh/H9Z5MNS9mb37fb6xUCHPsxvS2LwhaWpomWV8sjg95UHc7PUVKRNWVfQPX1DyrDHt5BcDYGNBzDxpBGJ4E2AHk6k7+wmuMoYRMMvPvDAIq0yG3oXKXkEo8BXLxWV7HF8oRlJv/bihNtfKzyAbRLPB57+HGZEcyThLio33AedYeSUArjdSfyUlLKLaHAVAb3DrqMYZqX06lbCpDBQ7zJIZUlDe6xRp+XrIifcl6+bFgH+r9Qzztag3P1lV89MlUrYaAG66KhGXh9j77ApS1Bnx4KtV5zRaPrdHuvTP8b3VLqHIYX-Exchange-Antispam-Report-Test: UriScan:;
>>> X-Exchange-Antispam-Report-CFA-Test:
>>>   BCL:0;PCL:0;RULEID:(9101531078)(601004)(2401047)(13018025)(13016025)(8121501046)(10201501046)(3002001);SRVR:VI1PR0201MB1885;BCL:0;PCL:0;RULEID:;SRVR:VI1PR0201MB1885;
>>> X-Microsoft-Exchange-Diagnostics:
>>>   =?utf-8?B?MTtWSTFQUjAyMDFNQjE4ODU7MjM6S0ZqeXZVaGNjQ0paSWo3bEZxYS9JbVVi?=
>>> =?utf-8?B?Ty9mbHZzQml2dnZ0aHRBbVBhV3FwTXVzYVJFRDFCWFNVVTkxdDByWHJEMTVi?=
>>> =?utf-8?B?c3VxWUZNQlArRXRZZW96aTFlY0E4aTIxdm9wR2FIckhlcGNCTjdGMUtEbWVL?=
>>> =?utf-8?B?amtvbzZUWVd1V3oxZFhuOWRiRFJXL1AyTVJPRFhVTzl3aW1YQysrWkdrdjlM?=
>>> =?utf-8?B?OFpCRWlkN2FrT1VLUmpyMFhLWktjSE1UczdrTk96dlZxeDc4WmwwZ29PRTVZ?=
>>> =?utf-8?B?d2FsUWxhYnZXc2ZWcW1mM1NKZDVHeG1wNVZqZzF4VDNacDlJemVaOVBQdTJN?=
>>> =?utf-8?B?Q3FsTHpQb2s0QlZnRVpBbUZYNkdqVTQwNE93Y2xIUGNHTE04ZTdiei9PR3gr?=
>>> =?utf-8?B?R2lPRExxalYrYzd1ZjZBd0RreGFZSUhtcktrNHpHRVBZbmMyVmpXcDJvRFlz?=
>>> =?utf-8?B?SHozcWs2MDRjdmhTMDZxM0kvZkIzbjByYVJ6WEhVbEJFR3QvNlJ4dVdFQm1r?=
>>> =?utf-8?B?TFRIaHNrbDdXd1phUUw4Y0tVZTdqZ0J3eWpwRmZCWE5Fa2psVWRpMGprQk1s?=
>>> =?utf-8?B?ZXB1MjNkeitUV0hwTGhrZ0FjMjE4NnFwaVRORXU3RENOZ2lsd2pLSGdGalhX?=
>>> =?utf-8?B?elE5cXFRVzV1REt2U3JxOFk1WXJGUVB2cDAzcC9aZGVLM2dyVDVXanVDL0RM?=
>>> =?utf-8?B?U01KTDFtelRUdHRaRER0MFU3Z0FGdEJYU0h0UkpjUkcxS0FnUEZCV2Q5MzU1?=
>>> =?utf-8?B?eXZoaHZLTnpobmRNZE4rZ2lNbnJrYXZOYUFjMy9yNlU1cStkK1JVczRzdk5u?=
>>> =?utf-8?B?UVFQYkF6RmZCc3ptOWcyMlljZFc3Z3ZFcGR2MWN5ZndtTWtsak9nRFp1NzVz?=
>>> =?utf-8?B?a3FWc2UzMldHMVNUV0R4VFI2czdqTXp4Y1RnQ1NHWExseG9nd05wRSt3aUF3?=
>>> =?utf-8?B?MThzTDg3dXBSaE9zZCtrWlEzbkxTRkh5NG9maUxINzcydUdES0xpbTlUUVU1?=
>>> =?utf-8?B?cGs3blB1Nm5RRUI0MS9sdDJSbzBWWGlCN1VRWlZhd1RHazVsZ1FHUHRHWnEv?=
>>> =?utf-8?B?bGJPUnppSlVzTWp6c1ZqN3BBTlJXQnB2dis1VUpKN1RVeHhPMEtzNnhtN0Y2?=
>>> =?utf-8?B?aGRNeVBrSVI4bmVmL0dFQm50VTNzc0NLKzlDOENwOUlZQWY1Nytod0FaVjBC?=
>>> =?utf-8?B?cXFnaDVQWGxxSGFxZkZyS1ZhVkloM0twdWI3UU5jQnVtaWNJaHV1UGpKZklw?=
>>> =?utf-8?B?MlF4dlZQODBHcTB1UmZmQjZFZ2tRdXR5a3Z5VEVxS3FucGd5WS9GNVZNcGI0?=
>>> =?utf-8?B?SEVZaFlxQUU5RnRQYlVaMlpRcXQzUEpKVG5NYWcwZFMzanlBVERrdXlBckda?=
>>> =?utf-8?B?cFQ4SGsxcGF3MGdOajNuL2NYVWhwOUx1MWtnUVo2MHhjNEcxM2JtaytYd1RQ?=
>>> =?utf-8?B?VHlRRFY4ZFE0NnNuWEpyRURLVm9QeDFsdnNVdGt4V1dvMk1acXBUcE4zUm9T?=
>>> =?utf-8?B?cVh0NWZtdjVjTHJIcHlvR2hYL3JxWXJqdkp6Y3gzUFVvUkZlVXlUVFVoeThN?=
>>> =?utf-8?B?T2VJdElMMHl3TVdURGZOSkJJY2FDMVFvVVlOSFJGT0VPQzRrVi9GTVVESkMv?=
>>> =?utf-8?B?MXVYMHRNUlpneHNvTUdjNGU5VVREby9MR0pnRkUvUjQ3UmJJUFVRd21CTW5w?=
>>> =?utf-8?B?OFFWZzd3dFNWRXVoVWVHUlNGWUJVaGR6OXh5QTRxeTdHZnJqa2NCSE51eXdJ?=
>>> =?utf-8?B?ckxTQXgrRDRCaFJMWk5kTGlHTGVPbnpMM2kyRm55anhIWGZiQWNocjRRRDJV?=
>>> =?utf-8?B?UkpqdkVFUnZ3WnJBd09kWEN6dkRBbmNDbnJkUUNwSng3R010WWptM1RqZmtO?=
>>> =?utf-8?B?dWZxOHkyQUtrT1lkYWJBVS9SRmNpSzh2b3ZJN0F0aStKTUxlSkM4d3N2dndr?=
>>> =?utf-8?B?Rk80cFJzaG8yZW9pQWNXOENFRVJhMVJYNG5ldnpWQ2M3bE96QzlRMjQxNWl4?=
>>> =?utf-8?B?MDJlUmpCeGQ1ODJ3SFkvSDFueFJVOUxEVGgvKzdRUzhEdXVUZThSNmJXdkxu?=
>>> =?utf-8?B?WXZYU1NnQUJmNkJsVVg0S1RjM1l0Sk5mQzM3NHFlcnkwQXhEWlRvNTFZbC9N?=
>>> =?utf-8?B?RVEzMm5pbUdtK25vbFl0L0diQXlhNktjRzZ3OVpnRTlLZURnSmlBUjd6dnRw?=
>>> =?utf-8?B?SUN1OXlENnNPTEkxd0htV3RsdGNxbXc9PQ==?=
>>> X-Microsoft-Exchange-Diagnostics:
>>>   1;VI1PR0201MB1885;5:EY/Cj4S8FZb0OwNEWsqAFBW5UHN3TFN+IlQjPUF1F6xYd5sR8XPFSHSiHBvxPYoEH8cHhtDaZKpiqoEXIwPetdVtttcH84LtHEPp/i/lvtAbBULY+7p7r2HnTECdOJbIS4eYfa7SlZ9RqPUo+1gNDg==;24:mNdvUPEfGSyYrOPtJbStEjqthITeTYG8r3wwzbIC6NqyUYBR5gyy2wY0poWrCxl+Bw37xQ9cMSZYvHJ8SNBK3OSjEcwaA1NZNyWMuuj/CX0=;7:liJQNWtffHFiSZ2fb/HdIQCsMLIRKl8MGv5/yPrL/hrFSr+t9PpQPCFFzVNIsiczVrH4gOFryJZCZZkSp0qVWmk3yKmkKRenVgtPoK5fp0tITgvAPq2QysPppqFKAm6iAqwIz1mfb5A3XqzrZIJtzYr8sIjB4dLMMGxaUo13ZPBSRrm+cLdhk3uEztTTSci1
>>> SpamDiagnosticOutput: 1:23
>>> SpamDiagnosticMetadata: NSPM
>>> X-OriginatorOrg: maynoothuniversity.onmicrosoft.com
>>> X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 May 2016 21:00:37.1219 (UTC)
>>> X-MS-Exchange-CrossTenant-Id: 1454f5cc-bb35-4685-bbd9-8621fd8055c9
>>> X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
>>> X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0201MB1885
>>> X-MS-Exchange-CrossPremises-OriginalClientIPAddress: 193.1.219.120
>>> X-MS-Exchange-CrossPremises-AuthSource: DB3FFO11FD009.protection.gbl
>>> X-MS-Exchange-CrossPremises-AuthAs: Anonymous
>>> X-MS-Exchange-CrossPremises-AVStamp-Service: 1.0
>>> X-MS-Exchange-CrossPremises-SCL: 1
>>> X-MS-Exchange-CrossPremises-Antispam-ScanContext:    DIR:Incoming;SFV:NSPM;SKIP:0;
>>> X-MS-Exchange-CrossPremises-Processed-By-Journaling: Journal Agent
>>> X-OrganizationHeadersPreserved: VI1PR0201MB1885.eurprd02.prod.outlook.com
>>> 
>>> I managed to get luajit compiled with GCC.  I think everything is good
>>> now except that my OSX system seems to have lost it's install of
>>> Texlive when it updated to El Capitan.  It's downloading now (2.5 gb!)
>>> and should be done in 15-20 minutes.  After that, I'll check that the
>>> iOS and Android manuals are compiling for the release and, if so, will
>>> finish off the release and notify here for uploading.
>>> 
>>> On Mon, May 16, 2016 at 3:20 PM, Victor Lazzarini
>>>  wrote:
>>>> yes, it was while I was adding the new fft routines, I forgot to tidy it =
>>> up, but when you
>>>> spotted it, it was fixed.
>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>> Dr Victor Lazzarini
>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>> 
>>>>> On 16 May 2016, at 20:13, Rory Walsh  wrote:
>>>>> 
>>>>> Thanks guys. It was most likely before Victor tidied it up.
>>>>> 
>>>>> 
>>>>> On 16 May 2016 at 20:12, Michael Gogins  wrote=
>>> :
>>>>> OK, I will remove it from the installer then.
>>>>> 
>>>>> Regards,
>>>>> Mike
>>>>> 
>>>>> -----------------------------------------------------
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://michaelgogins.tumblr.com
>>>>> Michael dot Gogins at gmail dot com
>>>>> 
>>>>> 
>>>>> On Mon, May 16, 2016 at 3:04 PM, Victor Lazzarini
>>>>>  wrote:
>>>>>> I think he is saying this because he had a problem before I moved the =
>>> header.
>>>>>> 
>>>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.h
>>>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.c
>>>>>> OOps/fftlib.c:#include "pffft.h"
>>>>>> OOps/pffft.c:#include "pffft.h"
>>>>>> Opcodes/mp3in.c:#include 
>>>>>> 
>>>>>> See? It=E2=80=99s only included in three internal files. It=E2=80=99s =
>>> nowhere in the public API. It should not be
>>>>>> in /include.
>>>>>> 
>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>>> =3D
>>>>>> Dr Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>> Maynooth University,
>>>>>> Maynooth, Co Kildare, Ireland
>>>>>> Tel: 00 353 7086936
>>>>>> Fax: 00 353 1 7086952
>>>>>> 
>>>>>>> On 16 May 2016, at 19:46, Michael Gogins  w=
>>> rote:
>>>>>>> 
>>>>>>> That's not what Rory said.
>>>>>>> 
>>>>>>> On May 16, 2016 2:35 PM, "Victor Lazzarini" >>> wrote:
>>>>>>> I actually checked and I had moved the #include. So there is no need =
>>> to add the
>>>>>>> pffft.c to /include. It=E2=80=99s an internal header, only included i=
>>> n fftlib.c and pffft.c.
>>>>>>> 
>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>>> =3D
>>>>>>> Dr Victor Lazzarini
>>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>>> Maynooth University,
>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>> Tel: 00 353 7086936
>>>>>>> Fax: 00 353 1 7086952
>>>>>>> 
>>>>>>>> On 16 May 2016, at 19:29, Victor Lazzarini >> e> wrote:
>>>>>>>> 
>>>>>>>> No, the include should be removed from csoundCore.h and added to ff=
>>> tlib.c .
>>>>>>>> 
>>>>>>>> I thought I'd done that already, but obviously forgot about it.
>>>>>>>> 
>>>>>>>> Victor Lazzarini
>>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>>>>> Maynooth University
>>>>>>>> Ireland
>>>>>>>> 
>>>>>>>>> On 16 May 2016, at 18:13, Michael Gogins >>> wrote:
>>>>>>>>> 
>>>>>>>>> Perhaps pffft.h should be moved from H to include.
>>>>>>>>> 
>>>>>>>>> Regards,
>>>>>>>>> Mike
>>>>>>>>> 
>>>>>>>>> -----------------------------------------------------
>>>>>>>>> Michael Gogins
>>>>>>>>> Irreducible Productions
>>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wr=
>>> ote:
>>>>>>>>>> Mike, can you include pfftt.h in the include folder with the late=
>>> st
>>>>>>>>>> installer? I tried your latest installer and noticed that choosin=
>>> g compact
>>>>>>>>>> install will not actually install anything at all. I see from the=
>>> iss file
>>>>>>>>>> that no files are identified with the Compact installation. Would=
>>> it be
>>>>>>>>>> possible to use that option to install a very basic version of Cs=
>>> ound, i.e.,
>>>>>>>>>> everything needed to run the CLI, plugins and libs, and the Csoun=
>>> d docs?
>>>>>>>>>> 
>>>>>>>>>>> On 16 May 2016 at 03:45, Steven Yi  wrote:
>>>>>>>>>>> 
>>>>>>>>>>> I ran into an issue with Android and minSdkVersions (should be a=
>>> n easy
>>>>>>>>>>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs fur=
>>> ther
>>>>>>>>>>> investigation).  Will look into this tomorrow.
>>>>>>>>>>> 
>>>>>>>>>>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
>>>>>>>>>>>  wrote:
>>>>>>>>>>>> I have built Csound 6.07 for Windows x64 from the release branc=
>>> h, and
>>>>>>>>>>>> it installs and runs. I have one or two minor changes to files =
>>> in the
>>>>>>>>>>>> release branch, but no source code changes. I am going to do a =
>>> few
>>>>>>>>>>>> more tests tomorrow.
>>>>>>>>>>>> 
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Mike
>>>>>>>>>>>> 
>>>>>>>>>>>> -----------------------------------------------------
>>>>>>>>>>>> Michael Gogins
>>>>>>>>>>>> Irreducible Productions
>>>>>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi >>> wrote:
>>>>>>>>>>>>> Hi Francois,
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Thanks!  I think having the manual with the main Csound releas=
>>> e is
>>>>>>>>>>>>> fine.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> For myself, I have so far built the Emscripten release.  I wil=
>>> l look
>>>>>>>>>>>>> at Android and static-lib version of iOS next.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> steven
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT >> l.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> manual and manual-fr are now tagged on github. You can get th=
>>> e built
>>>>>>>>>>>>>> packages here:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> http://fggp.org/csound/manual-packages/
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Francois
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT >>> :
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Maybe the manual packages should be found in the same place =
>>> (csound
>>>>>>>>>>>>>>> repo)
>>>>>>>>>>>>>>> than the csound packages, as it was on SF?
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Hi Francois,
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> What do you think about doing a release for the manual on t=
>>> he
>>>>>>>>>>>>>>>> csound/manual github repo?
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>> steven
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT >> mail.com>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> I'll build the manual in the different formats (10 package=
>>> s) and
>>>>>>>>>>>>>>>>> let
>>>>>>>>>>>>>>>>> you get
>>>>>>>>>>>>>>>>> it from my repo.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Francois
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> And apologies, it seems like a change to CMake  I made is=
>>> n't
>>>>>>>>>>>>>>>>>> working
>>>>>>>>>>>>>>>>>> on Travis/Linux.  I will revert in both the develop and r=
>>> elease
>>>>>>>>>>>>>>>>>> branch.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi >> l.com>
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> Hi All,
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The=
>>> branch
>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>> be
>>>>>>>>>>>>>>>>>>> pulled by using:
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> git pull
>>>>>>>>>>>>>>>>>>> git checkout release/6.07.0
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> I think the version.h has already been set to 6.07.0. In=
>>> staller
>>>>>>>>>>>>>>>>>>> scripts may need to be updated to reflect the new versio=
>>> n.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> I believe we are using Github for the next release.  The=
>>> re's a
>>>>>>>>>>>>>>>>>>> bit
>>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>>> a chicken and egg issue with setting up a release: on Gi=
>>> thub,
>>>>>>>>>>>>>>>>>>> releases
>>>>>>>>>>>>>>>>>>> are associated with tags, but we should wait to tag the =
>>> release
>>>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>>>> part of "finishing" the release branch as part of git-fl=
>>> ow.  I
>>>>>>>>>>>>>>>>>>> would
>>>>>>>>>>>>>>>>>>> propose: let's build the releases from the release branc=
>>> h and
>>>>>>>>>>>>>>>>>>> signal
>>>>>>>>>>>>>>>>>>> here when a release is ready.  Once we've all built, I c=
>>> an
>>>>>>>>>>>>>>>>>>> finish
>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> release branch which will tag the release and merge with
>>>>>>>>>>>>>>>>>>> master.  At
>>>>>>>>>>>>>>>>>>> that point, we can create the file release on Github and=
>>> upload
>>>>>>>>>>>>>>>>>>> builds
>>>>>>>>>>>>>>>>>>> there.  Also to note, Github will auto-generated source
>>>>>>>>>>>>>>>>>>> releases
>>>>>>>>>>>>>>>>>>> (zip,
>>>>>>>>>>>>>>>>>>> bz2 I think) for the release, so we will only have to wo=
>>> rk on
>>>>>>>>>>>>>>>>>>> compiled
>>>>>>>>>>>>>>>>>>> releases.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> One last thing: since our releases often package in the
>>>>>>>>>>>>>>>>>>> reference
>>>>>>>>>>>>>>>>>>> manual, we should probably first tag and build the manua=
>>> l.  Who
>>>>>>>>>>>>>>>>>>> will
>>>>>>>>>>>>>>>>>>> do this?
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>>>>> steven

How and where to upload?

On the github project repo is a link for releases. Click there, then find the release for 6.07.0, which should be a draft release, then select edit. At the bottom should be an area for uploading files.

(About to take a flight and will be offline for the next four hours)

Thanks, will do.

https://github.com/csound/csound/releases/tag/untagged-c5e62a0d037116d0c450

and then click on edit draft

========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 17 May 2016, at 13:58, Michael Gogins  wrote:
> 
> Thanks, will do.
> 
> On May 17, 2016 8:57 AM, "Steven Yi"  wrote:
> On the github project repo is a link for releases. Click there, then find the release for 6.07.0, which should be a draft release, then select edit. At the bottom should be an area for uploading files.
> 
> (About to take a flight and will be offline for the next four hours)
> 
> 
> On Tue, May 17, 2016, 8:52 AM Michael Gogins  wrote:
> How and where to upload?
> 
> On May 17, 2016 3:57 AM, "Victor Lazzarini"  wrote:
> Ok, uploaded my packages and added release notes.
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
> 
> > On 16 May 2016, at 22:40, Steven Yi  wrote:
> >
> > Seems to have linked alright.
> >
> > I've gone ahead and finished the release.  The summary of actions from
> > git-flow are:
> >
> > Summary of actions:
> > - Release branch 'release/6.07.0' has been merged into 'master'
> > - The release was tagged '6.07.0'
> > - Release tag '6.07.0' has been back-merged into 'develop'
> > - Release branch 'release/6.07.0' has been locally deleted; it has
> > been remotely deleted from 'origin'
> > - You are now on branch 'develop'
> >
> > On github, I have setup a draft under file releases for 6.07.0.  I
> > will iOS, Android, and Emscripten builds now.  Everyone here dealing
> > with releases should have edit access to the release and in there you
> > can upload by dragging and dropping the artifact in the browser.
> >
> > On Mon, May 16, 2016 at 5:37 PM, Victor Lazzarini
> >  wrote:
> >> With gcc? Will it link to clang-based Csound?
> >>
> >> Victor Lazzarini
> >> Dean of Arts, Celtic Studies, and Philosophy
> >> Maynooth University
> >> Ireland
> >>
> >>> On 16 May 2016, at 22:00, Steven Yi  wrote:
> >>>
> >>> X-Microsoft-Antispam:
> >>>   UriScan:;BCL:0;PCL:0;RULEID:(421252002)(3010002)(71701004)(71702002);SRVR:VI1PR0201MB1885;
> >>> X-Microsoft-Exchange-Diagnostics:
> >>>   1;VI1PR0201MB1885;20:r3WYCIIW7i762/kJvtlKgxSBDxSvb5njRHAfldQIIu+i6+CLbyB+k2+pfKGasV15smXCKG7kFTe6Bcn32hoFvESJDnyScsRm0ZJvZ6AufKJVFRflKJwQsU79BtV3cJ1CPuqDOOQvf3Tbbcci9zhLnKWCyFXOBl3l+bxJNbwy50Ym/sJy9zK6FsxZvbjOBISHdMUc7gX5jbJuLRrJYv2rDbgrNYaGPl5Uk+aEpZU0KRAJm5HVMsGZw9KbeTWsXh5u;4:d2tzayJzv11I2lWiSoUm4EFQ4T4yyj4OgGH950BzrjzFVjkbGrP2yahXYNGjSpWx9vbou0fqCdce+WASbcxUPmnrlzNg3Hk34grRRveS5QR6jwTG27or7gj3fCTNh/H9Z5MNS9mb37fb6xUCHPsxvS2LwhaWpomWV8sjg95UHc7PUVKRNWVfQPX1DyrDHt5BcDYGNBzDxpBGJ4E2AHk6k7+wmuMoYRMMvPvDAIq0yG3oXKXkEo8BXLxWV7HF8oRlJv/bihNtfKzyAbRLPB57+HGZEcyThLio33AedYeSUArjdSfyUlLKLaHAVAb3DrqMYZqX06lbCpDBQ7zJIZUlDe6xRp+XrIifcl6+bFgH+r9Qzztag3P1lV89MlUrYaAG66KhGXh9j77ApS1Bnx4KtV5zRaPrdHuvTP8b3VLqHIYX-Exchange-Antispam-Report-Test: UriScan:;
> >>> X-Exchange-Antispam-Report-CFA-Test:
> >>>   BCL:0;PCL:0;RULEID:(9101531078)(601004)(2401047)(13018025)(13016025)(8121501046)(10201501046)(3002001);SRVR:VI1PR0201MB1885;BCL:0;PCL:0;RULEID:;SRVR:VI1PR0201MB1885;
> >>> X-Microsoft-Exchange-Diagnostics:
> >>>   =?utf-8?B?MTtWSTFQUjAyMDFNQjE4ODU7MjM6S0ZqeXZVaGNjQ0paSWo3bEZxYS9JbVVi?=
> >>> =?utf-8?B?Ty9mbHZzQml2dnZ0aHRBbVBhV3FwTXVzYVJFRDFCWFNVVTkxdDByWHJEMTVi?=
> >>> =?utf-8?B?c3VxWUZNQlArRXRZZW96aTFlY0E4aTIxdm9wR2FIckhlcGNCTjdGMUtEbWVL?=
> >>> =?utf-8?B?amtvbzZUWVd1V3oxZFhuOWRiRFJXL1AyTVJPRFhVTzl3aW1YQysrWkdrdjlM?=
> >>> =?utf-8?B?OFpCRWlkN2FrT1VLUmpyMFhLWktjSE1UczdrTk96dlZxeDc4WmwwZ29PRTVZ?=
> >>> =?utf-8?B?d2FsUWxhYnZXc2ZWcW1mM1NKZDVHeG1wNVZqZzF4VDNacDlJemVaOVBQdTJN?=
> >>> =?utf-8?B?Q3FsTHpQb2s0QlZnRVpBbUZYNkdqVTQwNE93Y2xIUGNHTE04ZTdiei9PR3gr?=
> >>> =?utf-8?B?R2lPRExxalYrYzd1ZjZBd0RreGFZSUhtcktrNHpHRVBZbmMyVmpXcDJvRFlz?=
> >>> =?utf-8?B?SHozcWs2MDRjdmhTMDZxM0kvZkIzbjByYVJ6WEhVbEJFR3QvNlJ4dVdFQm1r?=
> >>> =?utf-8?B?TFRIaHNrbDdXd1phUUw4Y0tVZTdqZ0J3eWpwRmZCWE5Fa2psVWRpMGprQk1s?=
> >>> =?utf-8?B?ZXB1MjNkeitUV0hwTGhrZ0FjMjE4NnFwaVRORXU3RENOZ2lsd2pLSGdGalhX?=
> >>> =?utf-8?B?elE5cXFRVzV1REt2U3JxOFk1WXJGUVB2cDAzcC9aZGVLM2dyVDVXanVDL0RM?=
> >>> =?utf-8?B?U01KTDFtelRUdHRaRER0MFU3Z0FGdEJYU0h0UkpjUkcxS0FnUEZCV2Q5MzU1?=
> >>> =?utf-8?B?eXZoaHZLTnpobmRNZE4rZ2lNbnJrYXZOYUFjMy9yNlU1cStkK1JVczRzdk5u?=
> >>> =?utf-8?B?UVFQYkF6RmZCc3ptOWcyMlljZFc3Z3ZFcGR2MWN5ZndtTWtsak9nRFp1NzVz?=
> >>> =?utf-8?B?a3FWc2UzMldHMVNUV0R4VFI2czdqTXp4Y1RnQ1NHWExseG9nd05wRSt3aUF3?=
> >>> =?utf-8?B?MThzTDg3dXBSaE9zZCtrWlEzbkxTRkh5NG9maUxINzcydUdES0xpbTlUUVU1?=
> >>> =?utf-8?B?cGs3blB1Nm5RRUI0MS9sdDJSbzBWWGlCN1VRWlZhd1RHazVsZ1FHUHRHWnEv?=
> >>> =?utf-8?B?bGJPUnppSlVzTWp6c1ZqN3BBTlJXQnB2dis1VUpKN1RVeHhPMEtzNnhtN0Y2?=
> >>> =?utf-8?B?aGRNeVBrSVI4bmVmL0dFQm50VTNzc0NLKzlDOENwOUlZQWY1Nytod0FaVjBC?=
> >>> =?utf-8?B?cXFnaDVQWGxxSGFxZkZyS1ZhVkloM0twdWI3UU5jQnVtaWNJaHV1UGpKZklw?=
> >>> =?utf-8?B?MlF4dlZQODBHcTB1UmZmQjZFZ2tRdXR5a3Z5VEVxS3FucGd5WS9GNVZNcGI0?=
> >>> =?utf-8?B?SEVZaFlxQUU5RnRQYlVaMlpRcXQzUEpKVG5NYWcwZFMzanlBVERrdXlBckda?=
> >>> =?utf-8?B?cFQ4SGsxcGF3MGdOajNuL2NYVWhwOUx1MWtnUVo2MHhjNEcxM2JtaytYd1RQ?=
> >>> =?utf-8?B?VHlRRFY4ZFE0NnNuWEpyRURLVm9QeDFsdnNVdGt4V1dvMk1acXBUcE4zUm9T?=
> >>> =?utf-8?B?cVh0NWZtdjVjTHJIcHlvR2hYL3JxWXJqdkp6Y3gzUFVvUkZlVXlUVFVoeThN?=
> >>> =?utf-8?B?T2VJdElMMHl3TVdURGZOSkJJY2FDMVFvVVlOSFJGT0VPQzRrVi9GTVVESkMv?=
> >>> =?utf-8?B?MXVYMHRNUlpneHNvTUdjNGU5VVREby9MR0pnRkUvUjQ3UmJJUFVRd21CTW5w?=
> >>> =?utf-8?B?OFFWZzd3dFNWRXVoVWVHUlNGWUJVaGR6OXh5QTRxeTdHZnJqa2NCSE51eXdJ?=
> >>> =?utf-8?B?ckxTQXgrRDRCaFJMWk5kTGlHTGVPbnpMM2kyRm55anhIWGZiQWNocjRRRDJV?=
> >>> =?utf-8?B?UkpqdkVFUnZ3WnJBd09kWEN6dkRBbmNDbnJkUUNwSng3R010WWptM1RqZmtO?=
> >>> =?utf-8?B?dWZxOHkyQUtrT1lkYWJBVS9SRmNpSzh2b3ZJN0F0aStKTUxlSkM4d3N2dndr?=
> >>> =?utf-8?B?Rk80cFJzaG8yZW9pQWNXOENFRVJhMVJYNG5ldnpWQ2M3bE96QzlRMjQxNWl4?=
> >>> =?utf-8?B?MDJlUmpCeGQ1ODJ3SFkvSDFueFJVOUxEVGgvKzdRUzhEdXVUZThSNmJXdkxu?=
> >>> =?utf-8?B?WXZYU1NnQUJmNkJsVVg0S1RjM1l0Sk5mQzM3NHFlcnkwQXhEWlRvNTFZbC9N?=
> >>> =?utf-8?B?RVEzMm5pbUdtK25vbFl0L0diQXlhNktjRzZ3OVpnRTlLZURnSmlBUjd6dnRw?=
> >>> =?utf-8?B?SUN1OXlENnNPTEkxd0htV3RsdGNxbXc9PQ==?=
> >>> X-Microsoft-Exchange-Diagnostics:
> >>>   1;VI1PR0201MB1885;5:EY/Cj4S8FZb0OwNEWsqAFBW5UHN3TFN+IlQjPUF1F6xYd5sR8XPFSHSiHBvxPYoEH8cHhtDaZKpiqoEXIwPetdVtttcH84LtHEPp/i/lvtAbBULY+7p7r2HnTECdOJbIS4eYfa7SlZ9RqPUo+1gNDg==;24:mNdvUPEfGSyYrOPtJbStEjqthITeTYG8r3wwzbIC6NqyUYBR5gyy2wY0poWrCxl+Bw37xQ9cMSZYvHJ8SNBK3OSjEcwaA1NZNyWMuuj/CX0=;7:liJQNWtffHFiSZ2fb/HdIQCsMLIRKl8MGv5/yPrL/hrFSr+t9PpQPCFFzVNIsiczVrH4gOFryJZCZZkSp0qVWmk3yKmkKRenVgtPoK5fp0tITgvAPq2QysPppqFKAm6iAqwIz1mfb5A3XqzrZIJtzYr8sIjB4dLMMGxaUo13ZPBSRrm+cLdhk3uEztTTSci1
> >>> SpamDiagnosticOutput: 1:23
> >>> SpamDiagnosticMetadata: NSPM
> >>> X-OriginatorOrg: maynoothuniversity.onmicrosoft.com
> >>> X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 May 2016 21:00:37.1219 (UTC)
> >>> X-MS-Exchange-CrossTenant-Id: 1454f5cc-bb35-4685-bbd9-8621fd8055c9
> >>> X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
> >>> X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0201MB1885
> >>> X-MS-Exchange-CrossPremises-OriginalClientIPAddress: 193.1.219.120
> >>> X-MS-Exchange-CrossPremises-AuthSource: DB3FFO11FD009.protection.gbl
> >>> X-MS-Exchange-CrossPremises-AuthAs: Anonymous
> >>> X-MS-Exchange-CrossPremises-AVStamp-Service: 1.0
> >>> X-MS-Exchange-CrossPremises-SCL: 1
> >>> X-MS-Exchange-CrossPremises-Antispam-ScanContext:    DIR:Incoming;SFV:NSPM;SKIP:0;
> >>> X-MS-Exchange-CrossPremises-Processed-By-Journaling: Journal Agent
> >>> X-OrganizationHeadersPreserved: VI1PR0201MB1885.eurprd02.prod.outlook.com
> >>>
> >>> I managed to get luajit compiled with GCC.  I think everything is good
> >>> now except that my OSX system seems to have lost it's install of
> >>> Texlive when it updated to El Capitan.  It's downloading now (2.5 gb!)
> >>> and should be done in 15-20 minutes.  After that, I'll check that the
> >>> iOS and Android manuals are compiling for the release and, if so, will
> >>> finish off the release and notify here for uploading.
> >>>
> >>> On Mon, May 16, 2016 at 3:20 PM, Victor Lazzarini
> >>>  wrote:
> >>>> yes, it was while I was adding the new fft routines, I forgot to tidy it =
> >>> up, but when you
> >>>> spotted it, it was fixed.
> >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >>>> Dr Victor Lazzarini
> >>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>> Maynooth University,
> >>>> Maynooth, Co Kildare, Ireland
> >>>> Tel: 00 353 7086936
> >>>> Fax: 00 353 1 7086952
> >>>>
> >>>>> On 16 May 2016, at 20:13, Rory Walsh  wrote:
> >>>>>
> >>>>> Thanks guys. It was most likely before Victor tidied it up.
> >>>>>
> >>>>>
> >>>>> On 16 May 2016 at 20:12, Michael Gogins  wrote=
> >>> :
> >>>>> OK, I will remove it from the installer then.
> >>>>>
> >>>>> Regards,
> >>>>> Mike
> >>>>>
> >>>>> -----------------------------------------------------
> >>>>> Michael Gogins
> >>>>> Irreducible Productions
> >>>>> http://michaelgogins.tumblr.com
> >>>>> Michael dot Gogins at gmail dot com
> >>>>>
> >>>>>
> >>>>> On Mon, May 16, 2016 at 3:04 PM, Victor Lazzarini
> >>>>>  wrote:
> >>>>>> I think he is saying this because he had a problem before I moved the =
> >>> header.
> >>>>>>
> >>>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.h
> >>>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.c
> >>>>>> OOps/fftlib.c:#include "pffft.h"
> >>>>>> OOps/pffft.c:#include "pffft.h"
> >>>>>> Opcodes/mp3in.c:#include 
> >>>>>>
> >>>>>> See? It=E2=80=99s only included in three internal files. It=E2=80=99s =
> >>> nowhere in the public API. It should not be
> >>>>>> in /include.
> >>>>>>
> >>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> >>> =3D
> >>>>>> Dr Victor Lazzarini
> >>>>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>>>> Maynooth University,
> >>>>>> Maynooth, Co Kildare, Ireland
> >>>>>> Tel: 00 353 7086936
> >>>>>> Fax: 00 353 1 7086952
> >>>>>>
> >>>>>>> On 16 May 2016, at 19:46, Michael Gogins  w=
> >>> rote:
> >>>>>>>
> >>>>>>> That's not what Rory said.
> >>>>>>>
> >>>>>>> On May 16, 2016 2:35 PM, "Victor Lazzarini"  >>>> wrote:
> >>>>>>> I actually checked and I had moved the #include. So there is no need =
> >>> to add the
> >>>>>>> pffft.c to /include. It=E2=80=99s an internal header, only included i=
> >>> n fftlib.c and pffft.c.
> >>>>>>>
> >>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> >>> =3D
> >>>>>>> Dr Victor Lazzarini
> >>>>>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>>>>> Maynooth University,
> >>>>>>> Maynooth, Co Kildare, Ireland
> >>>>>>> Tel: 00 353 7086936
> >>>>>>> Fax: 00 353 1 7086952
> >>>>>>>
> >>>>>>>> On 16 May 2016, at 19:29, Victor Lazzarini  >>> e> wrote:
> >>>>>>>>
> >>>>>>>> No, the include should be removed from csoundCore.h and added to ff=
> >>> tlib.c .
> >>>>>>>>
> >>>>>>>> I thought I'd done that already, but obviously forgot about it.
> >>>>>>>>
> >>>>>>>> Victor Lazzarini
> >>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
> >>>>>>>> Maynooth University
> >>>>>>>> Ireland
> >>>>>>>>
> >>>>>>>>> On 16 May 2016, at 18:13, Michael Gogins  >>>> wrote:
> >>>>>>>>>
> >>>>>>>>> Perhaps pffft.h should be moved from H to include.
> >>>>>>>>>
> >>>>>>>>> Regards,
> >>>>>>>>> Mike
> >>>>>>>>>
> >>>>>>>>> -----------------------------------------------------
> >>>>>>>>> Michael Gogins
> >>>>>>>>> Irreducible Productions
> >>>>>>>>> http://michaelgogins.tumblr.com
> >>>>>>>>> Michael dot Gogins at gmail dot com
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wr=
> >>> ote:
> >>>>>>>>>> Mike, can you include pfftt.h in the include folder with the late=
> >>> st
> >>>>>>>>>> installer? I tried your latest installer and noticed that choosin=
> >>> g compact
> >>>>>>>>>> install will not actually install anything at all. I see from the=
> >>> iss file
> >>>>>>>>>> that no files are identified with the Compact installation. Would=
> >>> it be
> >>>>>>>>>> possible to use that option to install a very basic version of Cs=
> >>> ound, i.e.,
> >>>>>>>>>> everything needed to run the CLI, plugins and libs, and the Csoun=
> >>> d docs?
> >>>>>>>>>>
> >>>>>>>>>>> On 16 May 2016 at 03:45, Steven Yi  wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> I ran into an issue with Android and minSdkVersions (should be a=
> >>> n easy
> >>>>>>>>>>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs fur=
> >>> ther
> >>>>>>>>>>> investigation).  Will look into this tomorrow.
> >>>>>>>>>>>
> >>>>>>>>>>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
> >>>>>>>>>>>  wrote:
> >>>>>>>>>>>> I have built Csound 6.07 for Windows x64 from the release branc=
> >>> h, and
> >>>>>>>>>>>> it installs and runs. I have one or two minor changes to files =
> >>> in the
> >>>>>>>>>>>> release branch, but no source code changes. I am going to do a =
> >>> few
> >>>>>>>>>>>> more tests tomorrow.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Regards,
> >>>>>>>>>>>> Mike
> >>>>>>>>>>>>
> >>>>>>>>>>>> -----------------------------------------------------
> >>>>>>>>>>>> Michael Gogins
> >>>>>>>>>>>> Irreducible Productions
> >>>>>>>>>>>> http://michaelgogins.tumblr.com
> >>>>>>>>>>>> Michael dot Gogins at gmail dot com
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi  >>>> wrote:
> >>>>>>>>>>>>> Hi Francois,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Thanks!  I think having the manual with the main Csound releas=
> >>> e is
> >>>>>>>>>>>>> fine.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> For myself, I have so far built the Emscripten release.  I wil=
> >>> l look
> >>>>>>>>>>>>> at Android and static-lib version of iOS next.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> steven
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT  >>> l.com>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>> manual and manual-fr are now tagged on github. You can get th=
> >>> e built
> >>>>>>>>>>>>>> packages here:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> http://fggp.org/csound/manual-packages/
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Francois
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT  >>>> :
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Maybe the manual packages should be found in the same place =
> >>> (csound
> >>>>>>>>>>>>>>> repo)
> >>>>>>>>>>>>>>> than the csound packages, as it was on SF?
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Hi Francois,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> What do you think about doing a release for the manual on t=
> >>> he
> >>>>>>>>>>>>>>>> csound/manual github repo?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Thanks!
> >>>>>>>>>>>>>>>> steven
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT  >>> mail.com>
> >>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>> I'll build the manual in the different formats (10 package=
> >>> s) and
> >>>>>>>>>>>>>>>>> let
> >>>>>>>>>>>>>>>>> you get
> >>>>>>>>>>>>>>>>> it from my repo.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Francois
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> And apologies, it seems like a change to CMake  I made is=
> >>> n't
> >>>>>>>>>>>>>>>>>> working
> >>>>>>>>>>>>>>>>>> on Travis/Linux.  I will revert in both the develop and r=
> >>> elease
> >>>>>>>>>>>>>>>>>> branch.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi  >>> l.com>
> >>>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>> Hi All,
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The=
> >>> branch
> >>>>>>>>>>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>>> be
> >>>>>>>>>>>>>>>>>>> pulled by using:
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> git pull
> >>>>>>>>>>>>>>>>>>> git checkout release/6.07.0
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> I think the version.h has already been set to 6.07.0. In=
> >>> staller
> >>>>>>>>>>>>>>>>>>> scripts may need to be updated to reflect the new versio=
> >>> n.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> I believe we are using Github for the next release.  The=
> >>> re's a
> >>>>>>>>>>>>>>>>>>> bit
> >>>>>>>>>>>>>>>>>>> of
> >>>>>>>>>>>>>>>>>>> a chicken and egg issue with setting up a release: on Gi=
> >>> thub,
> >>>>>>>>>>>>>>>>>>> releases
> >>>>>>>>>>>>>>>>>>> are associated with tags, but we should wait to tag the =
> >>> release
> >>>>>>>>>>>>>>>>>>> as
> >>>>>>>>>>>>>>>>>>> part of "finishing" the release branch as part of git-fl=
> >>> ow.  I
> >>>>>>>>>>>>>>>>>>> would
> >>>>>>>>>>>>>>>>>>> propose: let's build the releases from the release branc=
> >>> h and
> >>>>>>>>>>>>>>>>>>> signal
> >>>>>>>>>>>>>>>>>>> here when a release is ready.  Once we've all built, I c=
> >>> an
> >>>>>>>>>>>>>>>>>>> finish
> >>>>>>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>> release branch which will tag the release and merge with
> >>>>>>>>>>>>>>>>>>> master.  At
> >>>>>>>>>>>>>>>>>>> that point, we can create the file release on Github and=
> >>> upload
> >>>>>>>>>>>>>>>>>>> builds
> >>>>>>>>>>>>>>>>>>> there.  Also to note, Github will auto-generated source
> >>>>>>>>>>>>>>>>>>> releases
> >>>>>>>>>>>>>>>>>>> (zip,
> >>>>>>>>>>>>>>>>>>> bz2 I think) for the release, so we will only have to wo=
> >>> rk on
> >>>>>>>>>>>>>>>>>>> compiled
> >>>>>>>>>>>>>>>>>>> releases.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> One last thing: since our releases often package in the
> >>>>>>>>>>>>>>>>>>> reference
> >>>>>>>>>>>>>>>>>>> manual, we should probably first tag and build the manua=
> >>> l.  Who
> >>>>>>>>>>>>>>>>>>> will
> >>>>>>>>>>>>>>>>>>> do this?
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Thanks!
> >>>>>>>>>>>>>>>>>>> steven

Still cannot find any link to releasesl where is it?


On Tue, 17 May 2016, Steven Yi wrote:

> 
> On the github project repo is a link for releases. Click there, then find the
> release for 6.07.0, which should be a draft release, then select edit. At the
> bottom should be an area for uploading files.
> 
> (About to take a flight and will be offline for the next four hours)
> 
> 
> On Tue, May 17, 2016, 8:52 AM Michael Gogins  wrote:
>
>       How and where to upload?
>
>       On May 17, 2016 3:57 AM, "Victor Lazzarini"
>        wrote:
>             Ok, uploaded my packages and added release notes.
>             ========================
>             Dr Victor Lazzarini
>             Dean of Arts, Celtic Studies and Philosophy,
>             Maynooth University,
>             Maynooth, Co Kildare, Ireland
>             Tel: 00 353 7086936
>             Fax: 00 353 1 7086952
>
>             > On 16 May 2016, at 22:40, Steven Yi
>              wrote:
>             >
>             > Seems to have linked alright.
>             >
>             > I've gone ahead and finished the release.  The summary
>             of actions from
>             > git-flow are:
>             >
>             > Summary of actions:
>             > - Release branch 'release/6.07.0' has been merged into
>             'master'
>             > - The release was tagged '6.07.0'
>             > - Release tag '6.07.0' has been back-merged into
>             'develop'
>             > - Release branch 'release/6.07.0' has been locally
>             deleted; it has
>             > been remotely deleted from 'origin'
>             > - You are now on branch 'develop'
>             >
>             > On github, I have setup a draft under file releases
>             for 6.07.0.  I
>             > will iOS, Android, and Emscripten builds now. 
>             Everyone here dealing
>             > with releases should have edit access to the release
>             and in there you
>             > can upload by dragging and dropping the artifact in
>             the browser.
>             >
>             > On Mon, May 16, 2016 at 5:37 PM, Victor Lazzarini
>             >  wrote:
>             >> With gcc? Will it link to clang-based Csound?
>             >>
>             >> Victor Lazzarini
>             >> Dean of Arts, Celtic Studies, and Philosophy
>             >> Maynooth University
>             >> Ireland
>             >>
>             >>> On 16 May 2016, at 22:00, Steven Yi
>              wrote:
>             >>>
>             >>> X-Microsoft-Antispam:
>             >>>  UriScan:;BCL:0;PCL:0;RULEID:(421252002)(3010002)(71701004)(71702002);SRVR:VI1P
>             R0201MB1885;
>             >>> X-Microsoft-Exchange-Diagnostics:
>             >>>  1;VI1PR0201MB1885;20:r3WYCIIW7i762/kJvtlKgxSBDxSvb5njRHAfldQIIu+i6+CLbyB+k2+pf
> KGasV15smXCKG7kFTe6Bcn32hoFvESJDnyScsRm0ZJvZ6AufKJVFRflKJwQsU79BtV3cJ1CPuqDOOQv
> f3Tbbcci9zhLnKWCyFXOBl3l+bxJNbwy50Ym/sJy9zK6FsxZvbjOBISHdMUc7gX5jbJuLRrJYv2rDbg
> rNYaGPl5Uk+aEpZU0KRAJm5HVMsGZw9KbeTWsXh5u;4:d2tzayJzv11I2lWiSoUm4EFQ4T4yyj4OgGH
> 950BzrjzFVjkbGrP2yahXYNGjSpWx9vbou0fqCdce+WASbcxUPmnrlzNg3Hk34grRRveS5QR6jwTG27
> or7gj3fCTNh/H9Z5MNS9mb37fb6xUCHPsxvS2LwhaWpomWV8sjg95UHc7PUVKRNWVfQPX1DyrDHt5Bc
> DYGNBzDxpBGJ4E2AHk6k7+wmuMoYRMMvPvDAIq0yG3oXKXkEo8BXLxWV7HF8oRlJv/bihNtfKzyAbRL
> PB57+HGZEcyThLio33AedYeSUArjdSfyUlLKLaHAVAb3DrqMYZqX06lbCpDBQ7zJIZUlDe6xRp+XrIi
> fcl6+bFgH+r9Qzztag3P1lV89MlUrYaAG66KhGXh9j77ApS1Bnx4KtV5zRaPrdHuvTP8b3VLqHIYX-E
>             xchange-Antispam-Report-Test: UriScan:;
>             >>> X-Exchange-Antispam-Report-CFA-Test:
>             >>>  BCL:0;PCL:0;RULEID:(9101531078)(601004)(2401047)(13018025)(13016025)(812150104
> 6)(10201501046)(3002001);SRVR:VI1PR0201MB1885;BCL:0;PCL:0;RULEID:;SRVR:VI1PR020
>             1MB1885;
>             >>> X-Microsoft-Exchange-Diagnostics:
>             >>> 
>              =?utf-8?B?MTtWSTFQUjAyMDFNQjE4ODU7MjM6S0ZqeXZVaGNjQ0paSWo3bEZxYS9JbVVi?=
>             >>>
>             =?utf-8?B?Ty9mbHZzQml2dnZ0aHRBbVBhV3FwTXVzYVJFRDFCWFNVVTkxdDByWHJEMTVi?=
>             >>>
>             =?utf-8?B?c3VxWUZNQlArRXRZZW96aTFlY0E4aTIxdm9wR2FIckhlcGNCTjdGMUtEbWVL?=
>             >>>
>             =?utf-8?B?amtvbzZUWVd1V3oxZFhuOWRiRFJXL1AyTVJPRFhVTzl3aW1YQysrWkdrdjlM?=
>             >>>
>             =?utf-8?B?OFpCRWlkN2FrT1VLUmpyMFhLWktjSE1UczdrTk96dlZxeDc4WmwwZ29PRTVZ?=
>             >>>
>             =?utf-8?B?d2FsUWxhYnZXc2ZWcW1mM1NKZDVHeG1wNVZqZzF4VDNacDlJemVaOVBQdTJN?=
>             >>>
>             =?utf-8?B?Q3FsTHpQb2s0QlZnRVpBbUZYNkdqVTQwNE93Y2xIUGNHTE04ZTdiei9PR3gr?=
>             >>>
>             =?utf-8?B?R2lPRExxalYrYzd1ZjZBd0RreGFZSUhtcktrNHpHRVBZbmMyVmpXcDJvRFlz?=
>             >>>
>             =?utf-8?B?SHozcWs2MDRjdmhTMDZxM0kvZkIzbjByYVJ6WEhVbEJFR3QvNlJ4dVdFQm1r?=
>             >>>
>             =?utf-8?B?TFRIaHNrbDdXd1phUUw4Y0tVZTdqZ0J3eWpwRmZCWE5Fa2psVWRpMGprQk1s?=
>             >>>
>             =?utf-8?B?ZXB1MjNkeitUV0hwTGhrZ0FjMjE4NnFwaVRORXU3RENOZ2lsd2pLSGdGalhX?=
>             >>>
>             =?utf-8?B?elE5cXFRVzV1REt2U3JxOFk1WXJGUVB2cDAzcC9aZGVLM2dyVDVXanVDL0RM?=
>             >>>
>             =?utf-8?B?U01KTDFtelRUdHRaRER0MFU3Z0FGdEJYU0h0UkpjUkcxS0FnUEZCV2Q5MzU1?=
>             >>>
>             =?utf-8?B?eXZoaHZLTnpobmRNZE4rZ2lNbnJrYXZOYUFjMy9yNlU1cStkK1JVczRzdk5u?=
>             >>>
>             =?utf-8?B?UVFQYkF6RmZCc3ptOWcyMlljZFc3Z3ZFcGR2MWN5ZndtTWtsak9nRFp1NzVz?=
>             >>>
>             =?utf-8?B?a3FWc2UzMldHMVNUV0R4VFI2czdqTXp4Y1RnQ1NHWExseG9nd05wRSt3aUF3?=
>             >>>
>             =?utf-8?B?MThzTDg3dXBSaE9zZCtrWlEzbkxTRkh5NG9maUxINzcydUdES0xpbTlUUVU1?=
>             >>>
>             =?utf-8?B?cGs3blB1Nm5RRUI0MS9sdDJSbzBWWGlCN1VRWlZhd1RHazVsZ1FHUHRHWnEv?=
>             >>>
>             =?utf-8?B?bGJPUnppSlVzTWp6c1ZqN3BBTlJXQnB2dis1VUpKN1RVeHhPMEtzNnhtN0Y2?=
>             >>>
>             =?utf-8?B?aGRNeVBrSVI4bmVmL0dFQm50VTNzc0NLKzlDOENwOUlZQWY1Nytod0FaVjBC?=
>             >>>
>             =?utf-8?B?cXFnaDVQWGxxSGFxZkZyS1ZhVkloM0twdWI3UU5jQnVtaWNJaHV1UGpKZklw?=
>             >>>
>             =?utf-8?B?MlF4dlZQODBHcTB1UmZmQjZFZ2tRdXR5a3Z5VEVxS3FucGd5WS9GNVZNcGI0?=
>             >>>
>             =?utf-8?B?SEVZaFlxQUU5RnRQYlVaMlpRcXQzUEpKVG5NYWcwZFMzanlBVERrdXlBckda?=
>             >>>
>             =?utf-8?B?cFQ4SGsxcGF3MGdOajNuL2NYVWhwOUx1MWtnUVo2MHhjNEcxM2JtaytYd1RQ?=
>             >>>
>             =?utf-8?B?VHlRRFY4ZFE0NnNuWEpyRURLVm9QeDFsdnNVdGt4V1dvMk1acXBUcE4zUm9T?=
>             >>>
>             =?utf-8?B?cVh0NWZtdjVjTHJIcHlvR2hYL3JxWXJqdkp6Y3gzUFVvUkZlVXlUVFVoeThN?=
>             >>>
>             =?utf-8?B?T2VJdElMMHl3TVdURGZOSkJJY2FDMVFvVVlOSFJGT0VPQzRrVi9GTVVESkMv?=
>             >>>
>             =?utf-8?B?MXVYMHRNUlpneHNvTUdjNGU5VVREby9MR0pnRkUvUjQ3UmJJUFVRd21CTW5w?=
>             >>>
>             =?utf-8?B?OFFWZzd3dFNWRXVoVWVHUlNGWUJVaGR6OXh5QTRxeTdHZnJqa2NCSE51eXdJ?=
>             >>>
>             =?utf-8?B?ckxTQXgrRDRCaFJMWk5kTGlHTGVPbnpMM2kyRm55anhIWGZiQWNocjRRRDJV?=
>             >>>
>             =?utf-8?B?UkpqdkVFUnZ3WnJBd09kWEN6dkRBbmNDbnJkUUNwSng3R010WWptM1RqZmtO?=
>             >>>
>             =?utf-8?B?dWZxOHkyQUtrT1lkYWJBVS9SRmNpSzh2b3ZJN0F0aStKTUxlSkM4d3N2dndr?=
>             >>>
>             =?utf-8?B?Rk80cFJzaG8yZW9pQWNXOENFRVJhMVJYNG5ldnpWQ2M3bE96QzlRMjQxNWl4?=
>             >>>
>             =?utf-8?B?MDJlUmpCeGQ1ODJ3SFkvSDFueFJVOUxEVGgvKzdRUzhEdXVUZThSNmJXdkxu?=
>             >>>
>             =?utf-8?B?WXZYU1NnQUJmNkJsVVg0S1RjM1l0Sk5mQzM3NHFlcnkwQXhEWlRvNTFZbC9N?=
>             >>>
>             =?utf-8?B?RVEzMm5pbUdtK25vbFl0L0diQXlhNktjRzZ3OVpnRTlLZURnSmlBUjd6dnRw?=
>             >>> =?utf-8?B?SUN1OXlENnNPTEkxd0htV3RsdGNxbXc9PQ==?=
>             >>> X-Microsoft-Exchange-Diagnostics:
>             >>>  1;VI1PR0201MB1885;5:EY/Cj4S8FZb0OwNEWsqAFBW5UHN3TFN+IlQjPUF1F6xYd5sR8XPFSHSiHB
> vxPYoEH8cHhtDaZKpiqoEXIwPetdVtttcH84LtHEPp/i/lvtAbBULY+7p7r2HnTECdOJbIS4eYfa7Sl
> Z9RqPUo+1gNDg==;24:mNdvUPEfGSyYrOPtJbStEjqthITeTYG8r3wwzbIC6NqyUYBR5gyy2wY0poWr
> Cxl+Bw37xQ9cMSZYvHJ8SNBK3OSjEcwaA1NZNyWMuuj/CX0=;7:liJQNWtffHFiSZ2fb/HdIQCsMLIR
> Kl8MGv5/yPrL/hrFSr+t9PpQPCFFzVNIsiczVrH4gOFryJZCZZkSp0qVWmk3yKmkKRenVgtPoK5fp0t
> ITgvAPq2QysPppqFKAm6iAqwIz1mfb5A3XqzrZIJtzYr8sIjB4dLMMGxaUo13ZPBSRrm+cLdhk3uEzt
>             TTSci1
>             >>> SpamDiagnosticOutput: 1:23
>             >>> SpamDiagnosticMetadata: NSPM
>             >>> X-OriginatorOrg: maynoothuniversity.onmicrosoft.com
>             >>> X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16
>             May 2016 21:00:37.1219 (UTC)
>             >>> X-MS-Exchange-CrossTenant-Id:
>             1454f5cc-bb35-4685-bbd9-8621fd8055c9
>             >>> X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
>             >>> X-MS-Exchange-Transport-CrossTenantHeadersStamped:
>             VI1PR0201MB1885
>             >>> X-MS-Exchange-CrossPremises-OriginalClientIPAddress:
>             193.1.219.120
>             >>> X-MS-Exchange-CrossPremises-AuthSource:
>             DB3FFO11FD009.protection.gbl
>             >>> X-MS-Exchange-CrossPremises-AuthAs: Anonymous
>             >>> X-MS-Exchange-CrossPremises-AVStamp-Service: 1.0
>             >>> X-MS-Exchange-CrossPremises-SCL: 1
>             >>> X-MS-Exchange-CrossPremises-Antispam-ScanContext:   
>             DIR:Incoming;SFV:NSPM;SKIP:0;
>             >>> X-MS-Exchange-CrossPremises-Processed-By-Journaling:
>             Journal Agent
>             >>> X-OrganizationHeadersPreserved:
>             VI1PR0201MB1885.eurprd02.prod.outlook.com
>             >>>
>             >>> I managed to get luajit compiled with GCC.  I think
>             everything is good
>             >>> now except that my OSX system seems to have lost
>             it's install of
>             >>> Texlive when it updated to El Capitan.  It's
>             downloading now (2.5 gb!)
>             >>> and should be done in 15-20 minutes.  After that,
>             I'll check that the
>             >>> iOS and Android manuals are compiling for the
>             release and, if so, will
>             >>> finish off the release and notify here for
>             uploading.
>             >>>
>             >>> On Mon, May 16, 2016 at 3:20 PM, Victor Lazzarini
>             >>>  wrote:
>             >>>> yes, it was while I was adding the new fft
>             routines, I forgot to tidy it =
>             >>> up, but when you
>             >>>> spotted it, it was fixed.
>             >>>>
>             =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>             >>>> Dr Victor Lazzarini
>             >>>> Dean of Arts, Celtic Studies and Philosophy,
>             >>>> Maynooth University,
>             >>>> Maynooth, Co Kildare, Ireland
>             >>>> Tel: 00 353 7086936
>             >>>> Fax: 00 353 1 7086952
>             >>>>
>             >>>>> On 16 May 2016, at 20:13, Rory Walsh
>              wrote:
>             >>>>>
>             >>>>> Thanks guys. It was most likely before Victor
>             tidied it up.
>             >>>>>
>             >>>>>
>             >>>>> On 16 May 2016 at 20:12, Michael Gogins
>              wrote=
>             >>> :
>             >>>>> OK, I will remove it from the installer then.
>             >>>>>
>             >>>>> Regards,
>             >>>>> Mike
>             >>>>>
>             >>>>>
>             -----------------------------------------------------
>             >>>>> Michael Gogins
>             >>>>> Irreducible Productions
>             >>>>> http://michaelgogins.tumblr.com
>             >>>>> Michael dot Gogins at gmail dot com
>             >>>>>
>             >>>>>
>             >>>>> On Mon, May 16, 2016 at 3:04 PM, Victor Lazzarini
>             >>>>>  wrote:
>             >>>>>> I think he is saying this because he had a
>             problem before I moved the =
>             >>> header.
>             >>>>>>
>             >>>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.h
>             >>>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.c
>             >>>>>> OOps/fftlib.c:#include "pffft.h"
>             >>>>>> OOps/pffft.c:#include "pffft.h"
>             >>>>>> Opcodes/mp3in.c:#include 
>             >>>>>>
>             >>>>>> See? It=E2=80=99s only included in three internal
>             files. It=E2=80=99s =
>             >>> nowhere in the public API. It should not be
>             >>>>>> in /include.
>             >>>>>>
>             >>>>>>
>             =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>             >>> =3D
>             >>>>>> Dr Victor Lazzarini
>             >>>>>> Dean of Arts, Celtic Studies and Philosophy,
>             >>>>>> Maynooth University,
>             >>>>>> Maynooth, Co Kildare, Ireland
>             >>>>>> Tel: 00 353 7086936
>             >>>>>> Fax: 00 353 1 7086952
>             >>>>>>
>             >>>>>>> On 16 May 2016, at 19:46, Michael Gogins
>              w=
>             >>> rote:
>             >>>>>>>
>             >>>>>>> That's not what Rory said.
>             >>>>>>>
>             >>>>>>> On May 16, 2016 2:35 PM, "Victor Lazzarini"
>                          >>>> wrote:
>             >>>>>>> I actually checked and I had moved the #include.
>             So there is no need =
>             >>> to add the
>             >>>>>>> pffft.c to /include. It=E2=80=99s an internal
>             header, only included i=
>             >>> n fftlib.c and pffft.c.
>             >>>>>>>
>             >>>>>>>
>             =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>             >>> =3D
>             >>>>>>> Dr Victor Lazzarini
>             >>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>             >>>>>>> Maynooth University,
>             >>>>>>> Maynooth, Co Kildare, Ireland
>             >>>>>>> Tel: 00 353 7086936
>             >>>>>>> Fax: 00 353 1 7086952
>             >>>>>>>
>             >>>>>>>> On 16 May 2016, at 19:29, Victor Lazzarini
>                          >>> e> wrote:
>             >>>>>>>>
>             >>>>>>>> No, the include should be removed from
>             csoundCore.h and added to ff=
>             >>> tlib.c .
>             >>>>>>>>
>             >>>>>>>> I thought I'd done that already, but obviously
>             forgot about it.
>             >>>>>>>>
>             >>>>>>>> Victor Lazzarini
>             >>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>             >>>>>>>> Maynooth University
>             >>>>>>>> Ireland
>             >>>>>>>>
>             >>>>>>>>> On 16 May 2016, at 18:13, Michael Gogins
>                          >>>> wrote:
>             >>>>>>>>>
>             >>>>>>>>> Perhaps pffft.h should be moved from H to
>             include.
>             >>>>>>>>>
>             >>>>>>>>> Regards,
>             >>>>>>>>> Mike
>             >>>>>>>>>
>             >>>>>>>>>
>             -----------------------------------------------------
>             >>>>>>>>> Michael Gogins
>             >>>>>>>>> Irreducible Productions
>             >>>>>>>>> http://michaelgogins.tumblr.com
>             >>>>>>>>> Michael dot Gogins at gmail dot com
>             >>>>>>>>>
>             >>>>>>>>>
>             >>>>>>>>>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh
>              wr=
>             >>> ote:
>             >>>>>>>>>> Mike, can you include pfftt.h in the include
>             folder with the late=
>             >>> st
>             >>>>>>>>>> installer? I tried your latest installer and
>             noticed that choosin=
>             >>> g compact
>             >>>>>>>>>> install will not actually install anything at
>             all. I see from the=
>             >>> iss file
>             >>>>>>>>>> that no files are identified with the Compact
>             installation. Would=
>             >>> it be
>             >>>>>>>>>> possible to use that option to install a very
>             basic version of Cs=
>             >>> ound, i.e.,
>             >>>>>>>>>> everything needed to run the CLI, plugins and
>             libs, and the Csoun=
>             >>> d docs?
>             >>>>>>>>>>
>             >>>>>>>>>>> On 16 May 2016 at 03:45, Steven Yi
>              wrote:
>             >>>>>>>>>>>
>             >>>>>>>>>>> I ran into an issue with Android and
>             minSdkVersions (should be a=
>             >>> n easy
>             >>>>>>>>>>> fix) and iOS with fftlib.c and xpc/xpc.h not
>             existing (needs fur=
>             >>> ther
>             >>>>>>>>>>> investigation).  Will look into this
>             tomorrow.
>             >>>>>>>>>>>
>             >>>>>>>>>>> On Sun, May 15, 2016 at 9:21 PM, Michael
>             Gogins
>             >>>>>>>>>>>  wrote:
>             >>>>>>>>>>>> I have built Csound 6.07 for Windows x64
>             from the release branc=
>             >>> h, and
>             >>>>>>>>>>>> it installs and runs. I have one or two
>             minor changes to files =
>             >>> in the
>             >>>>>>>>>>>> release branch, but no source code changes.
>             I am going to do a =
>             >>> few
>             >>>>>>>>>>>> more tests tomorrow.
>             >>>>>>>>>>>>
>             >>>>>>>>>>>> Regards,
>             >>>>>>>>>>>> Mike
>             >>>>>>>>>>>>
>             >>>>>>>>>>>>
>             -----------------------------------------------------
>             >>>>>>>>>>>> Michael Gogins
>             >>>>>>>>>>>> Irreducible Productions
>             >>>>>>>>>>>> http://michaelgogins.tumblr.com
>             >>>>>>>>>>>> Michael dot Gogins at gmail dot com
>             >>>>>>>>>>>>
>             >>>>>>>>>>>>
>             >>>>>>>>>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi
>                          >>>> wrote:
>             >>>>>>>>>>>>> Hi Francois,
>             >>>>>>>>>>>>>
>             >>>>>>>>>>>>> Thanks!  I think having the manual with
>             the main Csound releas=
>             >>> e is
>             >>>>>>>>>>>>> fine.
>             >>>>>>>>>>>>>
>             >>>>>>>>>>>>> For myself, I have so far built the
>             Emscripten release.  I wil=
>             >>> l look
>             >>>>>>>>>>>>> at Android and static-lib version of iOS
>             next.
>             >>>>>>>>>>>>>
>             >>>>>>>>>>>>> steven
>             >>>>>>>>>>>>>
>             >>>>>>>>>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois
>             PINOT              >>> l.com>
>             >>>>>>>>>>>>> wrote:
>             >>>>>>>>>>>>>> manual and manual-fr are now tagged on
>             github. You can get th=
>             >>> e built
>             >>>>>>>>>>>>>> packages here:
>             >>>>>>>>>>>>>>
>             >>>>>>>>>>>>>> http://fggp.org/csound/manual-packages/
>             >>>>>>>>>>>>>>
>             >>>>>>>>>>>>>> Francois
>             >>>>>>>>>>>>>>
>             >>>>>>>>>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT
>                          >>>> :
>             >>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>> Maybe the manual packages should be
>             found in the same place =
>             >>> (csound
>             >>>>>>>>>>>>>>> repo)
>             >>>>>>>>>>>>>>> than the csound packages, as it was on
>             SF?
>             >>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi
>             :
>             >>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>> Hi Francois,
>             >>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>> What do you think about doing a release
>             for the manual on t=
>             >>> he
>             >>>>>>>>>>>>>>>> csound/manual github repo?
>             >>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>> Thanks!
>             >>>>>>>>>>>>>>>> steven
>             >>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:20 PM,
>             Francois PINOT              >>> mail.com>
>             >>>>>>>>>>>>>>>> wrote:
>             >>>>>>>>>>>>>>>>> I'll build the manual in the different
>             formats (10 package=
>             >>> s) and
>             >>>>>>>>>>>>>>>>> let
>             >>>>>>>>>>>>>>>>> you get
>             >>>>>>>>>>>>>>>>> it from my repo.
>             >>>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>>> Francois
>             >>>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi
>             :
>             >>>>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>>>> And apologies, it seems like a change
>             to CMake  I made is=
>             >>> n't
>             >>>>>>>>>>>>>>>>>> working
>             >>>>>>>>>>>>>>>>>> on Travis/Linux.  I will revert in
>             both the develop and r=
>             >>> elease
>             >>>>>>>>>>>>>>>>>> branch.
>             >>>>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM,
>             Steven Yi              >>> l.com>
>             >>>>>>>>>>>>>>>>>> wrote:
>             >>>>>>>>>>>>>>>>>>> Hi All,
>             >>>>>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>>>>> I have setup a release branch for
>             6.07.0 on github.  The=
>             >>> branch
>             >>>>>>>>>>>>>>>>>>> can
>             >>>>>>>>>>>>>>>>>>> be
>             >>>>>>>>>>>>>>>>>>> pulled by using:
>             >>>>>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>>>>> git pull
>             >>>>>>>>>>>>>>>>>>> git checkout release/6.07.0
>             >>>>>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>>>>> I think the version.h has already
>             been set to 6.07.0. In=
>             >>> staller
>             >>>>>>>>>>>>>>>>>>> scripts may need to be updated to
>             reflect the new versio=
>             >>> n.
>             >>>>>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>>>>> I believe we are using Github for
>             the next release.  The=
>             >>> re's a
>             >>>>>>>>>>>>>>>>>>> bit
>             >>>>>>>>>>>>>>>>>>> of
>             >>>>>>>>>>>>>>>>>>> a chicken and egg issue with setting
>             up a release: on Gi=
>             >>> thub,
>             >>>>>>>>>>>>>>>>>>> releases
>             >>>>>>>>>>>>>>>>>>> are associated with tags, but we
>             should wait to tag the =
>             >>> release
>             >>>>>>>>>>>>>>>>>>> as
>             >>>>>>>>>>>>>>>>>>> part of "finishing" the release
>             branch as part of git-fl=
>             >>> ow.  I
>             >>>>>>>>>>>>>>>>>>> would
>             >>>>>>>>>>>>>>>>>>> propose: let's build the releases
>             from the release branc=
>             >>> h and
>             >>>>>>>>>>>>>>>>>>> signal
>             >>>>>>>>>>>>>>>>>>> here when a release is ready.  Once
>             we've all built, I c=
>             >>> an
>             >>>>>>>>>>>>>>>>>>> finish
>             >>>>>>>>>>>>>>>>>>> the
>             >>>>>>>>>>>>>>>>>>> release branch which will tag the
>             release and merge with
>             >>>>>>>>>>>>>>>>>>> master.  At
>             >>>>>>>>>>>>>>>>>>> that point, we can create the file
>             release on Github and=
>             >>> upload
>             >>>>>>>>>>>>>>>>>>> builds
>             >>>>>>>>>>>>>>>>>>> there.  Also to note, Github will
>             auto-generated source
>             >>>>>>>>>>>>>>>>>>> releases
>             >>>>>>>>>>>>>>>>>>> (zip,
>             >>>>>>>>>>>>>>>>>>> bz2 I think) for the release, so we
>             will only have to wo=
>             >>> rk on
>             >>>>>>>>>>>>>>>>>>> compiled
>             >>>>>>>>>>>>>>>>>>> releases.
>             >>>>>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>>>>> One last thing: since our releases
>             often package in the
>             >>>>>>>>>>>>>>>>>>> reference
>             >>>>>>>>>>>>>>>>>>> manual, we should probably first tag
>             and build the manua=
>             >>> l.  Who
>             >>>>>>>>>>>>>>>>>>> will
>             >>>>>>>>>>>>>>>>>>> do this?
>             >>>>>>>>>>>>>>>>>>>
>             >>>>>>>>>>>>>>>>>>> Thanks!
>             >>>>>>>>>>>>>>>>>>> steven
>             >>>>>
> 
> 
>

Why is the 6.06 manual in the release?

where? I don’t see it at

https://github.com/csound/csound/releases/tag/untagged-c5e62a0d037116d0c450


========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 17 May 2016, at 14:40, jpff  wrote:
> 
> Why is the 6.06 manual in the release?

I think I missed to endof 6.07 and endedin 6.06
I am finding github hard to navigate so I usually keep bookmarks.  The 
pages are too wide for my screen, the fonts too large, so butt0ns etc are 
not visible.  Lack of directories in te release also seems a pity 
especially related to the manual

What is missing from the release?

==John

yes, it’s not as good as sourceforge, but we did not have much alternative.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 17 May 2016, at 15:10, jpff  wrote:
> 
> I think I missed to endof 6.07 and endedin 6.06
> I am finding github hard to navigate so I usually keep bookmarks.  The pages are too wide for my screen, the fonts too large, so butt0ns etc are not visible.  Lack of directories in te release also seems a pity especially related to the manual
> 
> What is missing from the release?
> 
> ==John

Windows?
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 17 May 2016, at 15:10, jpff  wrote:
> 
> What is missing from the release?
> 

Sources are also missing.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 17 May 2016, at 15:10, jpff  wrote:
> 
> What is missing from the release?
> 
> ==John

I thought steven said it did tat automagically.  But happy to create 
source files

On Tue, 17 May 2016, Victor Lazzarini wrote:

> Sources are also missing.
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 17 May 2016, at 15:10, jpff  wrote:
>>
>> What is missing from the release?
>>
>> ==John
>> y

I am uploading the Windows installer now. Is there an FTP URL?

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Tue, May 17, 2016 at 9:01 AM, Victor Lazzarini
 wrote:
> https://github.com/csound/csound/releases/tag/untagged-c5e62a0d037116d0c450
>
> and then click on edit draft
>
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 17 May 2016, at 13:58, Michael Gogins  wrote:
>>
>> Thanks, will do.
>>
>> On May 17, 2016 8:57 AM, "Steven Yi"  wrote:
>> On the github project repo is a link for releases. Click there, then find the release for 6.07.0, which should be a draft release, then select edit. At the bottom should be an area for uploading files.
>>
>> (About to take a flight and will be offline for the next four hours)
>>
>>
>> On Tue, May 17, 2016, 8:52 AM Michael Gogins  wrote:
>> How and where to upload?
>>
>> On May 17, 2016 3:57 AM, "Victor Lazzarini"  wrote:
>> Ok, uploaded my packages and added release notes.
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>> > On 16 May 2016, at 22:40, Steven Yi  wrote:
>> >
>> > Seems to have linked alright.
>> >
>> > I've gone ahead and finished the release.  The summary of actions from
>> > git-flow are:
>> >
>> > Summary of actions:
>> > - Release branch 'release/6.07.0' has been merged into 'master'
>> > - The release was tagged '6.07.0'
>> > - Release tag '6.07.0' has been back-merged into 'develop'
>> > - Release branch 'release/6.07.0' has been locally deleted; it has
>> > been remotely deleted from 'origin'
>> > - You are now on branch 'develop'
>> >
>> > On github, I have setup a draft under file releases for 6.07.0.  I
>> > will iOS, Android, and Emscripten builds now.  Everyone here dealing
>> > with releases should have edit access to the release and in there you
>> > can upload by dragging and dropping the artifact in the browser.
>> >
>> > On Mon, May 16, 2016 at 5:37 PM, Victor Lazzarini
>> >  wrote:
>> >> With gcc? Will it link to clang-based Csound?
>> >>
>> >> Victor Lazzarini
>> >> Dean of Arts, Celtic Studies, and Philosophy
>> >> Maynooth University
>> >> Ireland
>> >>
>> >>> On 16 May 2016, at 22:00, Steven Yi  wrote:
>> >>>
>> >>> X-Microsoft-Antispam:
>> >>>   UriScan:;BCL:0;PCL:0;RULEID:(421252002)(3010002)(71701004)(71702002);SRVR:VI1PR0201MB1885;
>> >>> X-Microsoft-Exchange-Diagnostics:
>> >>>   1;VI1PR0201MB1885;20:r3WYCIIW7i762/kJvtlKgxSBDxSvb5njRHAfldQIIu+i6+CLbyB+k2+pfKGasV15smXCKG7kFTe6Bcn32hoFvESJDnyScsRm0ZJvZ6AufKJVFRflKJwQsU79BtV3cJ1CPuqDOOQvf3Tbbcci9zhLnKWCyFXOBl3l+bxJNbwy50Ym/sJy9zK6FsxZvbjOBISHdMUc7gX5jbJuLRrJYv2rDbgrNYaGPl5Uk+aEpZU0KRAJm5HVMsGZw9KbeTWsXh5u;4:d2tzayJzv11I2lWiSoUm4EFQ4T4yyj4OgGH950BzrjzFVjkbGrP2yahXYNGjSpWx9vbou0fqCdce+WASbcxUPmnrlzNg3Hk34grRRveS5QR6jwTG27or7gj3fCTNh/H9Z5MNS9mb37fb6xUCHPsxvS2LwhaWpomWV8sjg95UHc7PUVKRNWVfQPX1DyrDHt5BcDYGNBzDxpBGJ4E2AHk6k7+wmuMoYRMMvPvDAIq0yG3oXKXkEo8BXLxWV7HF8oRlJv/bihNtfKzyAbRLPB57+HGZEcyThLio33AedYeSUArjdSfyUlLKLaHAVAb3DrqMYZqX06lbCpDBQ7zJIZUlDe6xRp+XrIifcl6+bFgH+r9Qzztag3P1lV89MlUrYaAG66KhGXh9j77ApS1Bnx4KtV5zRaPrdHuvTP8b3VLqHIYX-Exchange-Antispam-Report-Test: UriScan:;
>> >>> X-Exchange-Antispam-Report-CFA-Test:
>> >>>   BCL:0;PCL:0;RULEID:(9101531078)(601004)(2401047)(13018025)(13016025)(8121501046)(10201501046)(3002001);SRVR:VI1PR0201MB1885;BCL:0;PCL:0;RULEID:;SRVR:VI1PR0201MB1885;
>> >>> X-Microsoft-Exchange-Diagnostics:
>> >>>   =?utf-8?B?MTtWSTFQUjAyMDFNQjE4ODU7MjM6S0ZqeXZVaGNjQ0paSWo3bEZxYS9JbVVi?=
>> >>> =?utf-8?B?Ty9mbHZzQml2dnZ0aHRBbVBhV3FwTXVzYVJFRDFCWFNVVTkxdDByWHJEMTVi?=
>> >>> =?utf-8?B?c3VxWUZNQlArRXRZZW96aTFlY0E4aTIxdm9wR2FIckhlcGNCTjdGMUtEbWVL?=
>> >>> =?utf-8?B?amtvbzZUWVd1V3oxZFhuOWRiRFJXL1AyTVJPRFhVTzl3aW1YQysrWkdrdjlM?=
>> >>> =?utf-8?B?OFpCRWlkN2FrT1VLUmpyMFhLWktjSE1UczdrTk96dlZxeDc4WmwwZ29PRTVZ?=
>> >>> =?utf-8?B?d2FsUWxhYnZXc2ZWcW1mM1NKZDVHeG1wNVZqZzF4VDNacDlJemVaOVBQdTJN?=
>> >>> =?utf-8?B?Q3FsTHpQb2s0QlZnRVpBbUZYNkdqVTQwNE93Y2xIUGNHTE04ZTdiei9PR3gr?=
>> >>> =?utf-8?B?R2lPRExxalYrYzd1ZjZBd0RreGFZSUhtcktrNHpHRVBZbmMyVmpXcDJvRFlz?=
>> >>> =?utf-8?B?SHozcWs2MDRjdmhTMDZxM0kvZkIzbjByYVJ6WEhVbEJFR3QvNlJ4dVdFQm1r?=
>> >>> =?utf-8?B?TFRIaHNrbDdXd1phUUw4Y0tVZTdqZ0J3eWpwRmZCWE5Fa2psVWRpMGprQk1s?=
>> >>> =?utf-8?B?ZXB1MjNkeitUV0hwTGhrZ0FjMjE4NnFwaVRORXU3RENOZ2lsd2pLSGdGalhX?=
>> >>> =?utf-8?B?elE5cXFRVzV1REt2U3JxOFk1WXJGUVB2cDAzcC9aZGVLM2dyVDVXanVDL0RM?=
>> >>> =?utf-8?B?U01KTDFtelRUdHRaRER0MFU3Z0FGdEJYU0h0UkpjUkcxS0FnUEZCV2Q5MzU1?=
>> >>> =?utf-8?B?eXZoaHZLTnpobmRNZE4rZ2lNbnJrYXZOYUFjMy9yNlU1cStkK1JVczRzdk5u?=
>> >>> =?utf-8?B?UVFQYkF6RmZCc3ptOWcyMlljZFc3Z3ZFcGR2MWN5ZndtTWtsak9nRFp1NzVz?=
>> >>> =?utf-8?B?a3FWc2UzMldHMVNUV0R4VFI2czdqTXp4Y1RnQ1NHWExseG9nd05wRSt3aUF3?=
>> >>> =?utf-8?B?MThzTDg3dXBSaE9zZCtrWlEzbkxTRkh5NG9maUxINzcydUdES0xpbTlUUVU1?=
>> >>> =?utf-8?B?cGs3blB1Nm5RRUI0MS9sdDJSbzBWWGlCN1VRWlZhd1RHazVsZ1FHUHRHWnEv?=
>> >>> =?utf-8?B?bGJPUnppSlVzTWp6c1ZqN3BBTlJXQnB2dis1VUpKN1RVeHhPMEtzNnhtN0Y2?=
>> >>> =?utf-8?B?aGRNeVBrSVI4bmVmL0dFQm50VTNzc0NLKzlDOENwOUlZQWY1Nytod0FaVjBC?=
>> >>> =?utf-8?B?cXFnaDVQWGxxSGFxZkZyS1ZhVkloM0twdWI3UU5jQnVtaWNJaHV1UGpKZklw?=
>> >>> =?utf-8?B?MlF4dlZQODBHcTB1UmZmQjZFZ2tRdXR5a3Z5VEVxS3FucGd5WS9GNVZNcGI0?=
>> >>> =?utf-8?B?SEVZaFlxQUU5RnRQYlVaMlpRcXQzUEpKVG5NYWcwZFMzanlBVERrdXlBckda?=
>> >>> =?utf-8?B?cFQ4SGsxcGF3MGdOajNuL2NYVWhwOUx1MWtnUVo2MHhjNEcxM2JtaytYd1RQ?=
>> >>> =?utf-8?B?VHlRRFY4ZFE0NnNuWEpyRURLVm9QeDFsdnNVdGt4V1dvMk1acXBUcE4zUm9T?=
>> >>> =?utf-8?B?cVh0NWZtdjVjTHJIcHlvR2hYL3JxWXJqdkp6Y3gzUFVvUkZlVXlUVFVoeThN?=
>> >>> =?utf-8?B?T2VJdElMMHl3TVdURGZOSkJJY2FDMVFvVVlOSFJGT0VPQzRrVi9GTVVESkMv?=
>> >>> =?utf-8?B?MXVYMHRNUlpneHNvTUdjNGU5VVREby9MR0pnRkUvUjQ3UmJJUFVRd21CTW5w?=
>> >>> =?utf-8?B?OFFWZzd3dFNWRXVoVWVHUlNGWUJVaGR6OXh5QTRxeTdHZnJqa2NCSE51eXdJ?=
>> >>> =?utf-8?B?ckxTQXgrRDRCaFJMWk5kTGlHTGVPbnpMM2kyRm55anhIWGZiQWNocjRRRDJV?=
>> >>> =?utf-8?B?UkpqdkVFUnZ3WnJBd09kWEN6dkRBbmNDbnJkUUNwSng3R010WWptM1RqZmtO?=
>> >>> =?utf-8?B?dWZxOHkyQUtrT1lkYWJBVS9SRmNpSzh2b3ZJN0F0aStKTUxlSkM4d3N2dndr?=
>> >>> =?utf-8?B?Rk80cFJzaG8yZW9pQWNXOENFRVJhMVJYNG5ldnpWQ2M3bE96QzlRMjQxNWl4?=
>> >>> =?utf-8?B?MDJlUmpCeGQ1ODJ3SFkvSDFueFJVOUxEVGgvKzdRUzhEdXVUZThSNmJXdkxu?=
>> >>> =?utf-8?B?WXZYU1NnQUJmNkJsVVg0S1RjM1l0Sk5mQzM3NHFlcnkwQXhEWlRvNTFZbC9N?=
>> >>> =?utf-8?B?RVEzMm5pbUdtK25vbFl0L0diQXlhNktjRzZ3OVpnRTlLZURnSmlBUjd6dnRw?=
>> >>> =?utf-8?B?SUN1OXlENnNPTEkxd0htV3RsdGNxbXc9PQ==?=
>> >>> X-Microsoft-Exchange-Diagnostics:
>> >>>   1;VI1PR0201MB1885;5:EY/Cj4S8FZb0OwNEWsqAFBW5UHN3TFN+IlQjPUF1F6xYd5sR8XPFSHSiHBvxPYoEH8cHhtDaZKpiqoEXIwPetdVtttcH84LtHEPp/i/lvtAbBULY+7p7r2HnTECdOJbIS4eYfa7SlZ9RqPUo+1gNDg==;24:mNdvUPEfGSyYrOPtJbStEjqthITeTYG8r3wwzbIC6NqyUYBR5gyy2wY0poWrCxl+Bw37xQ9cMSZYvHJ8SNBK3OSjEcwaA1NZNyWMuuj/CX0=;7:liJQNWtffHFiSZ2fb/HdIQCsMLIRKl8MGv5/yPrL/hrFSr+t9PpQPCFFzVNIsiczVrH4gOFryJZCZZkSp0qVWmk3yKmkKRenVgtPoK5fp0tITgvAPq2QysPppqFKAm6iAqwIz1mfb5A3XqzrZIJtzYr8sIjB4dLMMGxaUo13ZPBSRrm+cLdhk3uEztTTSci1
>> >>> SpamDiagnosticOutput: 1:23
>> >>> SpamDiagnosticMetadata: NSPM
>> >>> X-OriginatorOrg: maynoothuniversity.onmicrosoft.com
>> >>> X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 May 2016 21:00:37.1219 (UTC)
>> >>> X-MS-Exchange-CrossTenant-Id: 1454f5cc-bb35-4685-bbd9-8621fd8055c9
>> >>> X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
>> >>> X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0201MB1885
>> >>> X-MS-Exchange-CrossPremises-OriginalClientIPAddress: 193.1.219.120
>> >>> X-MS-Exchange-CrossPremises-AuthSource: DB3FFO11FD009.protection.gbl
>> >>> X-MS-Exchange-CrossPremises-AuthAs: Anonymous
>> >>> X-MS-Exchange-CrossPremises-AVStamp-Service: 1.0
>> >>> X-MS-Exchange-CrossPremises-SCL: 1
>> >>> X-MS-Exchange-CrossPremises-Antispam-ScanContext:    DIR:Incoming;SFV:NSPM;SKIP:0;
>> >>> X-MS-Exchange-CrossPremises-Processed-By-Journaling: Journal Agent
>> >>> X-OrganizationHeadersPreserved: VI1PR0201MB1885.eurprd02.prod.outlook.com
>> >>>
>> >>> I managed to get luajit compiled with GCC.  I think everything is good
>> >>> now except that my OSX system seems to have lost it's install of
>> >>> Texlive when it updated to El Capitan.  It's downloading now (2.5 gb!)
>> >>> and should be done in 15-20 minutes.  After that, I'll check that the
>> >>> iOS and Android manuals are compiling for the release and, if so, will
>> >>> finish off the release and notify here for uploading.
>> >>>
>> >>> On Mon, May 16, 2016 at 3:20 PM, Victor Lazzarini
>> >>>  wrote:
>> >>>> yes, it was while I was adding the new fft routines, I forgot to tidy it =
>> >>> up, but when you
>> >>>> spotted it, it was fixed.
>> >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> >>>> Dr Victor Lazzarini
>> >>>> Dean of Arts, Celtic Studies and Philosophy,
>> >>>> Maynooth University,
>> >>>> Maynooth, Co Kildare, Ireland
>> >>>> Tel: 00 353 7086936
>> >>>> Fax: 00 353 1 7086952
>> >>>>
>> >>>>> On 16 May 2016, at 20:13, Rory Walsh  wrote:
>> >>>>>
>> >>>>> Thanks guys. It was most likely before Victor tidied it up.
>> >>>>>
>> >>>>>
>> >>>>> On 16 May 2016 at 20:12, Michael Gogins  wrote=
>> >>> :
>> >>>>> OK, I will remove it from the installer then.
>> >>>>>
>> >>>>> Regards,
>> >>>>> Mike
>> >>>>>
>> >>>>> -----------------------------------------------------
>> >>>>> Michael Gogins
>> >>>>> Irreducible Productions
>> >>>>> http://michaelgogins.tumblr.com
>> >>>>> Michael dot Gogins at gmail dot com
>> >>>>>
>> >>>>>
>> >>>>> On Mon, May 16, 2016 at 3:04 PM, Victor Lazzarini
>> >>>>>  wrote:
>> >>>>>> I think he is saying this because he had a problem before I moved the =
>> >>> header.
>> >>>>>>
>> >>>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.h
>> >>>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.c
>> >>>>>> OOps/fftlib.c:#include "pffft.h"
>> >>>>>> OOps/pffft.c:#include "pffft.h"
>> >>>>>> Opcodes/mp3in.c:#include 
>> >>>>>>
>> >>>>>> See? It=E2=80=99s only included in three internal files. It=E2=80=99s =
>> >>> nowhere in the public API. It should not be
>> >>>>>> in /include.
>> >>>>>>
>> >>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>> >>> =3D
>> >>>>>> Dr Victor Lazzarini
>> >>>>>> Dean of Arts, Celtic Studies and Philosophy,
>> >>>>>> Maynooth University,
>> >>>>>> Maynooth, Co Kildare, Ireland
>> >>>>>> Tel: 00 353 7086936
>> >>>>>> Fax: 00 353 1 7086952
>> >>>>>>
>> >>>>>>> On 16 May 2016, at 19:46, Michael Gogins  w=
>> >>> rote:
>> >>>>>>>
>> >>>>>>> That's not what Rory said.
>> >>>>>>>
>> >>>>>>> On May 16, 2016 2:35 PM, "Victor Lazzarini" > >>>> wrote:
>> >>>>>>> I actually checked and I had moved the #include. So there is no need =
>> >>> to add the
>> >>>>>>> pffft.c to /include. It=E2=80=99s an internal header, only included i=
>> >>> n fftlib.c and pffft.c.
>> >>>>>>>
>> >>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>> >>> =3D
>> >>>>>>> Dr Victor Lazzarini
>> >>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>> >>>>>>> Maynooth University,
>> >>>>>>> Maynooth, Co Kildare, Ireland
>> >>>>>>> Tel: 00 353 7086936
>> >>>>>>> Fax: 00 353 1 7086952
>> >>>>>>>
>> >>>>>>>> On 16 May 2016, at 19:29, Victor Lazzarini > >>> e> wrote:
>> >>>>>>>>
>> >>>>>>>> No, the include should be removed from csoundCore.h and added to ff=
>> >>> tlib.c .
>> >>>>>>>>
>> >>>>>>>> I thought I'd done that already, but obviously forgot about it.
>> >>>>>>>>
>> >>>>>>>> Victor Lazzarini
>> >>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>> >>>>>>>> Maynooth University
>> >>>>>>>> Ireland
>> >>>>>>>>
>> >>>>>>>>> On 16 May 2016, at 18:13, Michael Gogins > >>>> wrote:
>> >>>>>>>>>
>> >>>>>>>>> Perhaps pffft.h should be moved from H to include.
>> >>>>>>>>>
>> >>>>>>>>> Regards,
>> >>>>>>>>> Mike
>> >>>>>>>>>
>> >>>>>>>>> -----------------------------------------------------
>> >>>>>>>>> Michael Gogins
>> >>>>>>>>> Irreducible Productions
>> >>>>>>>>> http://michaelgogins.tumblr.com
>> >>>>>>>>> Michael dot Gogins at gmail dot com
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wr=
>> >>> ote:
>> >>>>>>>>>> Mike, can you include pfftt.h in the include folder with the late=
>> >>> st
>> >>>>>>>>>> installer? I tried your latest installer and noticed that choosin=
>> >>> g compact
>> >>>>>>>>>> install will not actually install anything at all. I see from the=
>> >>> iss file
>> >>>>>>>>>> that no files are identified with the Compact installation. Would=
>> >>> it be
>> >>>>>>>>>> possible to use that option to install a very basic version of Cs=
>> >>> ound, i.e.,
>> >>>>>>>>>> everything needed to run the CLI, plugins and libs, and the Csoun=
>> >>> d docs?
>> >>>>>>>>>>
>> >>>>>>>>>>> On 16 May 2016 at 03:45, Steven Yi  wrote:
>> >>>>>>>>>>>
>> >>>>>>>>>>> I ran into an issue with Android and minSdkVersions (should be a=
>> >>> n easy
>> >>>>>>>>>>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs fur=
>> >>> ther
>> >>>>>>>>>>> investigation).  Will look into this tomorrow.
>> >>>>>>>>>>>
>> >>>>>>>>>>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
>> >>>>>>>>>>>  wrote:
>> >>>>>>>>>>>> I have built Csound 6.07 for Windows x64 from the release branc=
>> >>> h, and
>> >>>>>>>>>>>> it installs and runs. I have one or two minor changes to files =
>> >>> in the
>> >>>>>>>>>>>> release branch, but no source code changes. I am going to do a =
>> >>> few
>> >>>>>>>>>>>> more tests tomorrow.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Regards,
>> >>>>>>>>>>>> Mike
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> -----------------------------------------------------
>> >>>>>>>>>>>> Michael Gogins
>> >>>>>>>>>>>> Irreducible Productions
>> >>>>>>>>>>>> http://michaelgogins.tumblr.com
>> >>>>>>>>>>>> Michael dot Gogins at gmail dot com
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi > >>>> wrote:
>> >>>>>>>>>>>>> Hi Francois,
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Thanks!  I think having the manual with the main Csound releas=
>> >>> e is
>> >>>>>>>>>>>>> fine.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> For myself, I have so far built the Emscripten release.  I wil=
>> >>> l look
>> >>>>>>>>>>>>> at Android and static-lib version of iOS next.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> steven
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT > >>> l.com>
>> >>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>> manual and manual-fr are now tagged on github. You can get th=
>> >>> e built
>> >>>>>>>>>>>>>> packages here:
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> http://fggp.org/csound/manual-packages/
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Francois
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT > >>>> :
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Maybe the manual packages should be found in the same place =
>> >>> (csound
>> >>>>>>>>>>>>>>> repo)
>> >>>>>>>>>>>>>>> than the csound packages, as it was on SF?
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Hi Francois,
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> What do you think about doing a release for the manual on t=
>> >>> he
>> >>>>>>>>>>>>>>>> csound/manual github repo?
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Thanks!
>> >>>>>>>>>>>>>>>> steven
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT > >>> mail.com>
>> >>>>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>>>> I'll build the manual in the different formats (10 package=
>> >>> s) and
>> >>>>>>>>>>>>>>>>> let
>> >>>>>>>>>>>>>>>>> you get
>> >>>>>>>>>>>>>>>>> it from my repo.
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Francois
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> And apologies, it seems like a change to CMake  I made is=
>> >>> n't
>> >>>>>>>>>>>>>>>>>> working
>> >>>>>>>>>>>>>>>>>> on Travis/Linux.  I will revert in both the develop and r=
>> >>> elease
>> >>>>>>>>>>>>>>>>>> branch.
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi > >>> l.com>
>> >>>>>>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>>>>>> Hi All,
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The=
>> >>> branch
>> >>>>>>>>>>>>>>>>>>> can
>> >>>>>>>>>>>>>>>>>>> be
>> >>>>>>>>>>>>>>>>>>> pulled by using:
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> git pull
>> >>>>>>>>>>>>>>>>>>> git checkout release/6.07.0
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> I think the version.h has already been set to 6.07.0. In=
>> >>> staller
>> >>>>>>>>>>>>>>>>>>> scripts may need to be updated to reflect the new versio=
>> >>> n.
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> I believe we are using Github for the next release.  The=
>> >>> re's a
>> >>>>>>>>>>>>>>>>>>> bit
>> >>>>>>>>>>>>>>>>>>> of
>> >>>>>>>>>>>>>>>>>>> a chicken and egg issue with setting up a release: on Gi=
>> >>> thub,
>> >>>>>>>>>>>>>>>>>>> releases
>> >>>>>>>>>>>>>>>>>>> are associated with tags, but we should wait to tag the =
>> >>> release
>> >>>>>>>>>>>>>>>>>>> as
>> >>>>>>>>>>>>>>>>>>> part of "finishing" the release branch as part of git-fl=
>> >>> ow.  I
>> >>>>>>>>>>>>>>>>>>> would
>> >>>>>>>>>>>>>>>>>>> propose: let's build the releases from the release branc=
>> >>> h and
>> >>>>>>>>>>>>>>>>>>> signal
>> >>>>>>>>>>>>>>>>>>> here when a release is ready.  Once we've all built, I c=
>> >>> an
>> >>>>>>>>>>>>>>>>>>> finish
>> >>>>>>>>>>>>>>>>>>> the
>> >>>>>>>>>>>>>>>>>>> release branch which will tag the release and merge with
>> >>>>>>>>>>>>>>>>>>> master.  At
>> >>>>>>>>>>>>>>>>>>> that point, we can create the file release on Github and=
>> >>> upload
>> >>>>>>>>>>>>>>>>>>> builds
>> >>>>>>>>>>>>>>>>>>> there.  Also to note, Github will auto-generated source
>> >>>>>>>>>>>>>>>>>>> releases
>> >>>>>>>>>>>>>>>>>>> (zip,
>> >>>>>>>>>>>>>>>>>>> bz2 I think) for the release, so we will only have to wo=
>> >>> rk on
>> >>>>>>>>>>>>>>>>>>> compiled
>> >>>>>>>>>>>>>>>>>>> releases.
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> One last thing: since our releases often package in the
>> >>>>>>>>>>>>>>>>>>> reference
>> >>>>>>>>>>>>>>>>>>> manual, we should probably first tag and build the manua=
>> >>> l.  Who
>> >>>>>>>>>>>>>>>>>>> will
>> >>>>>>>>>>>>>>>>>>> do this?
>> >>>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>>> Thanks!
>> >>>>>>>>>>>>>>>>>>> steven

Maybe it does, let's wait for his confirmation.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 17 May 2016, at 16:01, jpff  wrote:
> 
> I thought steven said it did tat automagically.  But happy to create source files
> 
>> On Tue, 17 May 2016, Victor Lazzarini wrote:
>> 
>> Sources are also missing.
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>> 
>>> On 17 May 2016, at 15:10, jpff  wrote:
>>> 
>>> What is missing from the release?
>>> 
>>> ==John
>>> y

They are done automatically. At the end are links for .tar.gz and .zip
source packages.

On 17 May 2016 at 11:01, jpff  wrote:
> I thought steven said it did tat automagically.  But happy to create source
> files
>
>
> On Tue, 17 May 2016, Victor Lazzarini wrote:
>
>> Sources are also missing.
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>>> On 17 May 2016, at 15:10, jpff  wrote:
>>>
>>> What is missing from the release?
>>>
>>> ==John
>>> y
>>
>>
>



-- 

Saludos,

I haven't found one. 

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 17 May 2016, at 16:03, Michael Gogins  wrote:
> 
> I am uploading the Windows installer now. Is there an FTP URL?
> 
> Regards,
> Mike
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> 
> On Tue, May 17, 2016 at 9:01 AM, Victor Lazzarini
>  wrote:
>> https://github.com/csound/csound/releases/tag/untagged-c5e62a0d037116d0c450
>> 
>> and then click on edit draft
>> 
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>> 
>>> On 17 May 2016, at 13:58, Michael Gogins  wrote:
>>> 
>>> Thanks, will do.
>>> 
>>> On May 17, 2016 8:57 AM, "Steven Yi"  wrote:
>>> On the github project repo is a link for releases. Click there, then find the release for 6.07.0, which should be a draft release, then select edit. At the bottom should be an area for uploading files.
>>> 
>>> (About to take a flight and will be offline for the next four hours)
>>> 
>>> 
>>> On Tue, May 17, 2016, 8:52 AM Michael Gogins  wrote:
>>> How and where to upload?
>>> 
>>> On May 17, 2016 3:57 AM, "Victor Lazzarini"  wrote:
>>> Ok, uploaded my packages and added release notes.
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>> 
>>>> On 16 May 2016, at 22:40, Steven Yi  wrote:
>>>> 
>>>> Seems to have linked alright.
>>>> 
>>>> I've gone ahead and finished the release.  The summary of actions from
>>>> git-flow are:
>>>> 
>>>> Summary of actions:
>>>> - Release branch 'release/6.07.0' has been merged into 'master'
>>>> - The release was tagged '6.07.0'
>>>> - Release tag '6.07.0' has been back-merged into 'develop'
>>>> - Release branch 'release/6.07.0' has been locally deleted; it has
>>>> been remotely deleted from 'origin'
>>>> - You are now on branch 'develop'
>>>> 
>>>> On github, I have setup a draft under file releases for 6.07.0.  I
>>>> will iOS, Android, and Emscripten builds now.  Everyone here dealing
>>>> with releases should have edit access to the release and in there you
>>>> can upload by dragging and dropping the artifact in the browser.
>>>> 
>>>> On Mon, May 16, 2016 at 5:37 PM, Victor Lazzarini
>>>>  wrote:
>>>>> With gcc? Will it link to clang-based Csound?
>>>>> 
>>>>> Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>> Maynooth University
>>>>> Ireland
>>>>> 
>>>>>> On 16 May 2016, at 22:00, Steven Yi  wrote:
>>>>>> 
>>>>>> X-Microsoft-Antispam:
>>>>>>  UriScan:;BCL:0;PCL:0;RULEID:(421252002)(3010002)(71701004)(71702002);SRVR:VI1PR0201MB1885;
>>>>>> X-Microsoft-Exchange-Diagnostics:
>>>>>>  1;VI1PR0201MB1885;20:r3WYCIIW7i762/kJvtlKgxSBDxSvb5njRHAfldQIIu+i6+CLbyB+k2+pfKGasV15smXCKG7kFTe6Bcn32hoFvESJDnyScsRm0ZJvZ6AufKJVFRflKJwQsU79BtV3cJ1CPuqDOOQvf3Tbbcci9zhLnKWCyFXOBl3l+bxJNbwy50Ym/sJy9zK6FsxZvbjOBISHdMUc7gX5jbJuLRrJYv2rDbgrNYaGPl5Uk+aEpZU0KRAJm5HVMsGZw9KbeTWsXh5u;4:d2tzayJzv11I2lWiSoUm4EFQ4T4yyj4OgGH950BzrjzFVjkbGrP2yahXYNGjSpWx9vbou0fqCdce+WASbcxUPmnrlzNg3Hk34grRRveS5QR6jwTG27or7gj3fCTNh/H9Z5MNS9mb37fb6xUCHPsxvS2LwhaWpomWV8sjg95UHc7PUVKRNWVfQPX1DyrDHt5BcDYGNBzDxpBGJ4E2AHk6k7+wmuMoYRMMvPvDAIq0yG3oXKXkEo8BXLxWV7HF8oRlJv/bihNtfKzyAbRLPB57+HGZEcyThLio33AedYeSUArjdSfyUlLKLaHAVAb3DrqMYZqX06lbCpDBQ7zJIZUlDe6xRp+XrIifcl6+bFgH+r9Qzztag3P1lV89MlUrYaAG66KhGXh9j77ApS1Bnx4KtV5zRaPrdHuvTP8b3VLqHIYX-Exchange-Antispam-Report-Test: UriScan:;
>>>>>> X-Exchange-Antispam-Report-CFA-Test:
>>>>>>  BCL:0;PCL:0;RULEID:(9101531078)(601004)(2401047)(13018025)(13016025)(8121501046)(10201501046)(3002001);SRVR:VI1PR0201MB1885;BCL:0;PCL:0;RULEID:;SRVR:VI1PR0201MB1885;
>>>>>> X-Microsoft-Exchange-Diagnostics:
>>>>>>  =?utf-8?B?MTtWSTFQUjAyMDFNQjE4ODU7MjM6S0ZqeXZVaGNjQ0paSWo3bEZxYS9JbVVi?=
>>>>>> =?utf-8?B?Ty9mbHZzQml2dnZ0aHRBbVBhV3FwTXVzYVJFRDFCWFNVVTkxdDByWHJEMTVi?=
>>>>>> =?utf-8?B?c3VxWUZNQlArRXRZZW96aTFlY0E4aTIxdm9wR2FIckhlcGNCTjdGMUtEbWVL?=
>>>>>> =?utf-8?B?amtvbzZUWVd1V3oxZFhuOWRiRFJXL1AyTVJPRFhVTzl3aW1YQysrWkdrdjlM?=
>>>>>> =?utf-8?B?OFpCRWlkN2FrT1VLUmpyMFhLWktjSE1UczdrTk96dlZxeDc4WmwwZ29PRTVZ?=
>>>>>> =?utf-8?B?d2FsUWxhYnZXc2ZWcW1mM1NKZDVHeG1wNVZqZzF4VDNacDlJemVaOVBQdTJN?=
>>>>>> =?utf-8?B?Q3FsTHpQb2s0QlZnRVpBbUZYNkdqVTQwNE93Y2xIUGNHTE04ZTdiei9PR3gr?=
>>>>>> =?utf-8?B?R2lPRExxalYrYzd1ZjZBd0RreGFZSUhtcktrNHpHRVBZbmMyVmpXcDJvRFlz?=
>>>>>> =?utf-8?B?SHozcWs2MDRjdmhTMDZxM0kvZkIzbjByYVJ6WEhVbEJFR3QvNlJ4dVdFQm1r?=
>>>>>> =?utf-8?B?TFRIaHNrbDdXd1phUUw4Y0tVZTdqZ0J3eWpwRmZCWE5Fa2psVWRpMGprQk1s?=
>>>>>> =?utf-8?B?ZXB1MjNkeitUV0hwTGhrZ0FjMjE4NnFwaVRORXU3RENOZ2lsd2pLSGdGalhX?=
>>>>>> =?utf-8?B?elE5cXFRVzV1REt2U3JxOFk1WXJGUVB2cDAzcC9aZGVLM2dyVDVXanVDL0RM?=
>>>>>> =?utf-8?B?U01KTDFtelRUdHRaRER0MFU3Z0FGdEJYU0h0UkpjUkcxS0FnUEZCV2Q5MzU1?=
>>>>>> =?utf-8?B?eXZoaHZLTnpobmRNZE4rZ2lNbnJrYXZOYUFjMy9yNlU1cStkK1JVczRzdk5u?=
>>>>>> =?utf-8?B?UVFQYkF6RmZCc3ptOWcyMlljZFc3Z3ZFcGR2MWN5ZndtTWtsak9nRFp1NzVz?=
>>>>>> =?utf-8?B?a3FWc2UzMldHMVNUV0R4VFI2czdqTXp4Y1RnQ1NHWExseG9nd05wRSt3aUF3?=
>>>>>> =?utf-8?B?MThzTDg3dXBSaE9zZCtrWlEzbkxTRkh5NG9maUxINzcydUdES0xpbTlUUVU1?=
>>>>>> =?utf-8?B?cGs3blB1Nm5RRUI0MS9sdDJSbzBWWGlCN1VRWlZhd1RHazVsZ1FHUHRHWnEv?=
>>>>>> =?utf-8?B?bGJPUnppSlVzTWp6c1ZqN3BBTlJXQnB2dis1VUpKN1RVeHhPMEtzNnhtN0Y2?=
>>>>>> =?utf-8?B?aGRNeVBrSVI4bmVmL0dFQm50VTNzc0NLKzlDOENwOUlZQWY1Nytod0FaVjBC?=
>>>>>> =?utf-8?B?cXFnaDVQWGxxSGFxZkZyS1ZhVkloM0twdWI3UU5jQnVtaWNJaHV1UGpKZklw?=
>>>>>> =?utf-8?B?MlF4dlZQODBHcTB1UmZmQjZFZ2tRdXR5a3Z5VEVxS3FucGd5WS9GNVZNcGI0?=
>>>>>> =?utf-8?B?SEVZaFlxQUU5RnRQYlVaMlpRcXQzUEpKVG5NYWcwZFMzanlBVERrdXlBckda?=
>>>>>> =?utf-8?B?cFQ4SGsxcGF3MGdOajNuL2NYVWhwOUx1MWtnUVo2MHhjNEcxM2JtaytYd1RQ?=
>>>>>> =?utf-8?B?VHlRRFY4ZFE0NnNuWEpyRURLVm9QeDFsdnNVdGt4V1dvMk1acXBUcE4zUm9T?=
>>>>>> =?utf-8?B?cVh0NWZtdjVjTHJIcHlvR2hYL3JxWXJqdkp6Y3gzUFVvUkZlVXlUVFVoeThN?=
>>>>>> =?utf-8?B?T2VJdElMMHl3TVdURGZOSkJJY2FDMVFvVVlOSFJGT0VPQzRrVi9GTVVESkMv?=
>>>>>> =?utf-8?B?MXVYMHRNUlpneHNvTUdjNGU5VVREby9MR0pnRkUvUjQ3UmJJUFVRd21CTW5w?=
>>>>>> =?utf-8?B?OFFWZzd3dFNWRXVoVWVHUlNGWUJVaGR6OXh5QTRxeTdHZnJqa2NCSE51eXdJ?=
>>>>>> =?utf-8?B?ckxTQXgrRDRCaFJMWk5kTGlHTGVPbnpMM2kyRm55anhIWGZiQWNocjRRRDJV?=
>>>>>> =?utf-8?B?UkpqdkVFUnZ3WnJBd09kWEN6dkRBbmNDbnJkUUNwSng3R010WWptM1RqZmtO?=
>>>>>> =?utf-8?B?dWZxOHkyQUtrT1lkYWJBVS9SRmNpSzh2b3ZJN0F0aStKTUxlSkM4d3N2dndr?=
>>>>>> =?utf-8?B?Rk80cFJzaG8yZW9pQWNXOENFRVJhMVJYNG5ldnpWQ2M3bE96QzlRMjQxNWl4?=
>>>>>> =?utf-8?B?MDJlUmpCeGQ1ODJ3SFkvSDFueFJVOUxEVGgvKzdRUzhEdXVUZThSNmJXdkxu?=
>>>>>> =?utf-8?B?WXZYU1NnQUJmNkJsVVg0S1RjM1l0Sk5mQzM3NHFlcnkwQXhEWlRvNTFZbC9N?=
>>>>>> =?utf-8?B?RVEzMm5pbUdtK25vbFl0L0diQXlhNktjRzZ3OVpnRTlLZURnSmlBUjd6dnRw?=
>>>>>> =?utf-8?B?SUN1OXlENnNPTEkxd0htV3RsdGNxbXc9PQ==?=
>>>>>> X-Microsoft-Exchange-Diagnostics:
>>>>>>  1;VI1PR0201MB1885;5:EY/Cj4S8FZb0OwNEWsqAFBW5UHN3TFN+IlQjPUF1F6xYd5sR8XPFSHSiHBvxPYoEH8cHhtDaZKpiqoEXIwPetdVtttcH84LtHEPp/i/lvtAbBULY+7p7r2HnTECdOJbIS4eYfa7SlZ9RqPUo+1gNDg==;24:mNdvUPEfGSyYrOPtJbStEjqthITeTYG8r3wwzbIC6NqyUYBR5gyy2wY0poWrCxl+Bw37xQ9cMSZYvHJ8SNBK3OSjEcwaA1NZNyWMuuj/CX0=;7:liJQNWtffHFiSZ2fb/HdIQCsMLIRKl8MGv5/yPrL/hrFSr+t9PpQPCFFzVNIsiczVrH4gOFryJZCZZkSp0qVWmk3yKmkKRenVgtPoK5fp0tITgvAPq2QysPppqFKAm6iAqwIz1mfb5A3XqzrZIJtzYr8sIjB4dLMMGxaUo13ZPBSRrm+cLdhk3uEztTTSci1
>>>>>> SpamDiagnosticOutput: 1:23
>>>>>> SpamDiagnosticMetadata: NSPM
>>>>>> X-OriginatorOrg: maynoothuniversity.onmicrosoft.com
>>>>>> X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 May 2016 21:00:37.1219 (UTC)
>>>>>> X-MS-Exchange-CrossTenant-Id: 1454f5cc-bb35-4685-bbd9-8621fd8055c9
>>>>>> X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
>>>>>> X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0201MB1885
>>>>>> X-MS-Exchange-CrossPremises-OriginalClientIPAddress: 193.1.219.120
>>>>>> X-MS-Exchange-CrossPremises-AuthSource: DB3FFO11FD009.protection.gbl
>>>>>> X-MS-Exchange-CrossPremises-AuthAs: Anonymous
>>>>>> X-MS-Exchange-CrossPremises-AVStamp-Service: 1.0
>>>>>> X-MS-Exchange-CrossPremises-SCL: 1
>>>>>> X-MS-Exchange-CrossPremises-Antispam-ScanContext:    DIR:Incoming;SFV:NSPM;SKIP:0;
>>>>>> X-MS-Exchange-CrossPremises-Processed-By-Journaling: Journal Agent
>>>>>> X-OrganizationHeadersPreserved: VI1PR0201MB1885.eurprd02.prod.outlook.com
>>>>>> 
>>>>>> I managed to get luajit compiled with GCC.  I think everything is good
>>>>>> now except that my OSX system seems to have lost it's install of
>>>>>> Texlive when it updated to El Capitan.  It's downloading now (2.5 gb!)
>>>>>> and should be done in 15-20 minutes.  After that, I'll check that the
>>>>>> iOS and Android manuals are compiling for the release and, if so, will
>>>>>> finish off the release and notify here for uploading.
>>>>>> 
>>>>>> On Mon, May 16, 2016 at 3:20 PM, Victor Lazzarini
>>>>>>  wrote:
>>>>>>> yes, it was while I was adding the new fft routines, I forgot to tidy it =
>>>>>> up, but when you
>>>>>>> spotted it, it was fixed.
>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>>>> Dr Victor Lazzarini
>>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>>> Maynooth University,
>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>> Tel: 00 353 7086936
>>>>>>> Fax: 00 353 1 7086952
>>>>>>> 
>>>>>>>> On 16 May 2016, at 20:13, Rory Walsh  wrote:
>>>>>>>> 
>>>>>>>> Thanks guys. It was most likely before Victor tidied it up.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On 16 May 2016 at 20:12, Michael Gogins  wrote=
>>>>>> :
>>>>>>>> OK, I will remove it from the installer then.
>>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> Mike
>>>>>>>> 
>>>>>>>> -----------------------------------------------------
>>>>>>>> Michael Gogins
>>>>>>>> Irreducible Productions
>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Mon, May 16, 2016 at 3:04 PM, Victor Lazzarini
>>>>>>>>  wrote:
>>>>>>>>> I think he is saying this because he had a problem before I moved the =
>>>>>> header.
>>>>>>>>> 
>>>>>>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.h
>>>>>>>>> ligeti:csound6 victor$ grep "pffft.h"  */*.c
>>>>>>>>> OOps/fftlib.c:#include "pffft.h"
>>>>>>>>> OOps/pffft.c:#include "pffft.h"
>>>>>>>>> Opcodes/mp3in.c:#include 
>>>>>>>>> 
>>>>>>>>> See? It=E2=80=99s only included in three internal files. It=E2=80=99s =
>>>>>> nowhere in the public API. It should not be
>>>>>>>>> in /include.
>>>>>>>>> 
>>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>>>>>> =3D
>>>>>>>>> Dr Victor Lazzarini
>>>>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>>>>> Maynooth University,
>>>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>>>> Tel: 00 353 7086936
>>>>>>>>> Fax: 00 353 1 7086952
>>>>>>>>> 
>>>>>>>>>> On 16 May 2016, at 19:46, Michael Gogins  w=
>>>>>> rote:
>>>>>>>>>> 
>>>>>>>>>> That's not what Rory said.
>>>>>>>>>> 
>>>>>>>>>> On May 16, 2016 2:35 PM, "Victor Lazzarini" >>>>>> wrote:
>>>>>>>>>> I actually checked and I had moved the #include. So there is no need =
>>>>>> to add the
>>>>>>>>>> pffft.c to /include. It=E2=80=99s an internal header, only included i=
>>>>>> n fftlib.c and pffft.c.
>>>>>>>>>> 
>>>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>>>>>> =3D
>>>>>>>>>> Dr Victor Lazzarini
>>>>>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>>>>>> Maynooth University,
>>>>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>>>>> Tel: 00 353 7086936
>>>>>>>>>> Fax: 00 353 1 7086952
>>>>>>>>>> 
>>>>>>>>>>> On 16 May 2016, at 19:29, Victor Lazzarini >>>>> e> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> No, the include should be removed from csoundCore.h and added to ff=
>>>>>> tlib.c .
>>>>>>>>>>> 
>>>>>>>>>>> I thought I'd done that already, but obviously forgot about it.
>>>>>>>>>>> 
>>>>>>>>>>> Victor Lazzarini
>>>>>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>>>>>>>> Maynooth University
>>>>>>>>>>> Ireland
>>>>>>>>>>> 
>>>>>>>>>>>> On 16 May 2016, at 18:13, Michael Gogins >>>>>> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> Perhaps pffft.h should be moved from H to include.
>>>>>>>>>>>> 
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Mike
>>>>>>>>>>>> 
>>>>>>>>>>>> -----------------------------------------------------
>>>>>>>>>>>> Michael Gogins
>>>>>>>>>>>> Irreducible Productions
>>>>>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>>> On Mon, May 16, 2016 at 4:38 AM, Rory Walsh  wr=
>>>>>> ote:
>>>>>>>>>>>>> Mike, can you include pfftt.h in the include folder with the late=
>>>>>> st
>>>>>>>>>>>>> installer? I tried your latest installer and noticed that choosin=
>>>>>> g compact
>>>>>>>>>>>>> install will not actually install anything at all. I see from the=
>>>>>> iss file
>>>>>>>>>>>>> that no files are identified with the Compact installation. Would=
>>>>>> it be
>>>>>>>>>>>>> possible to use that option to install a very basic version of Cs=
>>>>>> ound, i.e.,
>>>>>>>>>>>>> everything needed to run the CLI, plugins and libs, and the Csoun=
>>>>>> d docs?
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On 16 May 2016 at 03:45, Steven Yi  wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I ran into an issue with Android and minSdkVersions (should be a=
>>>>>> n easy
>>>>>>>>>>>>>> fix) and iOS with fftlib.c and xpc/xpc.h not existing (needs fur=
>>>>>> ther
>>>>>>>>>>>>>> investigation).  Will look into this tomorrow.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Sun, May 15, 2016 at 9:21 PM, Michael Gogins
>>>>>>>>>>>>>>  wrote:
>>>>>>>>>>>>>>> I have built Csound 6.07 for Windows x64 from the release branc=
>>>>>> h, and
>>>>>>>>>>>>>>> it installs and runs. I have one or two minor changes to files =
>>>>>> in the
>>>>>>>>>>>>>>> release branch, but no source code changes. I am going to do a =
>>>>>> few
>>>>>>>>>>>>>>> more tests tomorrow.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>> Mike
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> -----------------------------------------------------
>>>>>>>>>>>>>>> Michael Gogins
>>>>>>>>>>>>>>> Irreducible Productions
>>>>>>>>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 7:08 PM, Steven Yi >>>>>> wrote:
>>>>>>>>>>>>>>>> Hi Francois,
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Thanks!  I think having the manual with the main Csound releas=
>>>>>> e is
>>>>>>>>>>>>>>>> fine.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> For myself, I have so far built the Emscripten release.  I wil=
>>>>>> l look
>>>>>>>>>>>>>>>> at Android and static-lib version of iOS next.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> steven
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 6:58 PM, Francois PINOT >>>>> l.com>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> manual and manual-fr are now tagged on github. You can get th=
>>>>>> e built
>>>>>>>>>>>>>>>>> packages here:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> http://fggp.org/csound/manual-packages/
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Francois
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 2016-05-15 23:13 GMT+02:00 Francois PINOT >>>>>> :
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Maybe the manual packages should be found in the same place =
>>>>>> (csound
>>>>>>>>>>>>>>>>>> repo)
>>>>>>>>>>>>>>>>>> than the csound packages, as it was on SF?
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 2016-05-15 22:30 GMT+02:00 Steven Yi :
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> Hi Francois,
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> What do you think about doing a release for the manual on t=
>>>>>> he
>>>>>>>>>>>>>>>>>>> csound/manual github repo?
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>>>>> steven
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:20 PM, Francois PINOT >>>>> mail.com>
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>> I'll build the manual in the different formats (10 package=
>>>>>> s) and
>>>>>>>>>>>>>>>>>>>> let
>>>>>>>>>>>>>>>>>>>> you get
>>>>>>>>>>>>>>>>>>>> it from my repo.
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> Francois
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> 2016-05-15 22:17 GMT+02:00 Steven Yi :
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> And apologies, it seems like a change to CMake  I made is=
>>>>>> n't
>>>>>>>>>>>>>>>>>>>>> working
>>>>>>>>>>>>>>>>>>>>> on Travis/Linux.  I will revert in both the develop and r=
>>>>>> elease
>>>>>>>>>>>>>>>>>>>>> branch.
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> On Sun, May 15, 2016 at 4:15 PM, Steven Yi >>>>> l.com>
>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>> Hi All,
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> I have setup a release branch for 6.07.0 on github.  The=
>>>>>> branch
>>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>>> be
>>>>>>>>>>>>>>>>>>>>>> pulled by using:
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> git pull
>>>>>>>>>>>>>>>>>>>>>> git checkout release/6.07.0
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> I think the version.h has already been set to 6.07.0. In=
>>>>>> staller
>>>>>>>>>>>>>>>>>>>>>> scripts may need to be updated to reflect the new versio=
>>>>>> n.
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> I believe we are using Github for the next release.  The=
>>>>>> re's a
>>>>>>>>>>>>>>>>>>>>>> bit
>>>>>>>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>>>>>> a chicken and egg issue with setting up a release: on Gi=
>>>>>> thub,
>>>>>>>>>>>>>>>>>>>>>> releases
>>>>>>>>>>>>>>>>>>>>>> are associated with tags, but we should wait to tag the =
>>>>>> release
>>>>>>>>>>>>>>>>>>>>>> as
>>>>>>>>>>>>>>>>>>>>>> part of "finishing" the release branch as part of git-fl=
>>>>>> ow.  I
>>>>>>>>>>>>>>>>>>>>>> would
>>>>>>>>>>>>>>>>>>>>>> propose: let's build the releases from the release branc=
>>>>>> h and
>>>>>>>>>>>>>>>>>>>>>> signal
>>>>>>>>>>>>>>>>>>>>>> here when a release is ready.  Once we've all built, I c=
>>>>>> an
>>>>>>>>>>>>>>>>>>>>>> finish
>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>> release branch which will tag the release and merge with
>>>>>>>>>>>>>>>>>>>>>> master.  At
>>>>>>>>>>>>>>>>>>>>>> that point, we can create the file release on Github and=
>>>>>> upload
>>>>>>>>>>>>>>>>>>>>>> builds
>>>>>>>>>>>>>>>>>>>>>> there.  Also to note, Github will auto-generated source
>>>>>>>>>>>>>>>>>>>>>> releases
>>>>>>>>>>>>>>>>>>>>>> (zip,
>>>>>>>>>>>>>>>>>>>>>> bz2 I think) for the release, so we will only have to wo=
>>>>>> rk on
>>>>>>>>>>>>>>>>>>>>>> compiled
>>>>>>>>>>>>>>>>>>>>>> releases.
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> One last thing: since our releases often package in the
>>>>>>>>>>>>>>>>>>>>>> reference
>>>>>>>>>>>>>>>>>>>>>> manual, we should probably first tag and build the manua=
>>>>>> l.  Who
>>>>>>>>>>>>>>>>>>>>>> will
>>>>>>>>>>>>>>>>>>>>>> do this?
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>>>>>>>> steven

I have uploaded the Windows installer to the draft release page.

Soon I will update the Csound for Android app in the Google Play app store.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Tue, May 17, 2016 at 11:09 AM, Felipe Sateler  wrote:
> They are done automatically. At the end are links for .tar.gz and .zip
> source packages.
>
> On 17 May 2016 at 11:01, jpff  wrote:
>> I thought steven said it did tat automagically.  But happy to create source
>> files
>>
>>
>> On Tue, 17 May 2016, Victor Lazzarini wrote:
>>
>>> Sources are also missing.
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>>> On 17 May 2016, at 15:10, jpff  wrote:
>>>>
>>>> What is missing from the release?
>>>>
>>>> ==John
>>>> y
>>>
>>>
>>
>
>
>
> --
>
> Saludos,