There was a lengthy discussion about moving to Android Studio and
everything was done in the open. This was done in response to
community requests to support Android Studio.  If you're using Csound
6.05, I'm assuming you're still using Eclipse?  Are you looking at
files from Git or a binary release?    CsoundAndroid still contains
all of the JNI and native files, and it is built using the build.sh
script within that folder.  Afterwards, the update-android-studio.sh
(found in the csound/android folder) is used to update the library in
CsoundForAndroid/CsoundAndroid.

On Mon, Apr 25, 2016 at 9:19 AM, Rory Walsh  wrote:
> I'm just looking to upgrade some Android projects from Csound6.05 to
> Csound6.06. Things seems to have changed completely here? There used to be a
> CsoundAndroid folder that contained everything I needed to develop
> applications. Now there is a CsoundForAndroid folder. Where did
> AndroidCsound.cpp/hpp go? I can't find any of the jni files that were
> included in previous versions. It's frustrating when major changes like this
> happen because it means frontend developers have to go and rewrite a lot of
> make files in order to update their projects.
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

It’s still possible to use CsoundAndroid and the Eclipse projects, I have been doing that
all along (because the project I work on has not moved to Android Studio). That’s 
directly from GIT. Once you have the NDK and libsndfile srcs, building the jni interface
is straightforward.

NB: the recommendation from Android Developers is to move to clang, so I have updated
the .mk files to allow for that. At first hand, it appears to generate more efficient binaries.

========================
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 25 Apr 2016, at 14:41, Steven Yi  wrote:
> 
> There was a lengthy discussion about moving to Android Studio and
> everything was done in the open. This was done in response to
> community requests to support Android Studio.  If you're using Csound
> 6.05, I'm assuming you're still using Eclipse?  Are you looking at
> files from Git or a binary release?    CsoundAndroid still contains
> all of the JNI and native files, and it is built using the build.sh
> script within that folder.  Afterwards, the update-android-studio.sh
> (found in the csound/android folder) is used to update the library in
> CsoundForAndroid/CsoundAndroid.
> 
> On Mon, Apr 25, 2016 at 9:19 AM, Rory Walsh  wrote:
>> I'm just looking to upgrade some Android projects from Csound6.05 to
>> Csound6.06. Things seems to have changed completely here? There used to be a
>> CsoundAndroid folder that contained everything I needed to develop
>> applications. Now there is a CsoundForAndroid folder. Where did
>> AndroidCsound.cpp/hpp go? I can't find any of the jni files that were
>> included in previous versions. It's frustrating when major changes like this
>> happen because it means frontend developers have to go and rewrite a lot of
>> make files in order to update their projects.
>> Csound mailing list Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> https://github.com/csound/csound/issues Discussions of bugs and features can
>> be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

I'm not sure what the problem is, could you describe how you were
using it before and what you're seeing now?  I only tested as far as
the examples and Csound app applications and others reported having
success too with that at least.  If there's something else not
working, email the details.

On Mon, Apr 25, 2016 at 11:19 AM, Rory Walsh  wrote:
> Thanks guys, I've no doubt it was discussed in an open and transparent way,
> it just seemed to slip under the radar for me. I've never used eclipse to
> build any my projects. I know it's not recommended, but I've been using ant
> to build the Android version of Cabbage.
>
> Steven: I've been using the zip files available on sourceforge. For what
> it's worth, I've never had any issue using these binaries in Android Studio.
> All the way back to Csound6.03. Two of my current (non-Cabbage) projects are
> built with Android Studio and they are using 6.05. What is the problem
> there? I guess I need to look over the archives. Perhaps some plugin libs
> were causing problems?
>
> Victor, I'll have ago at building CsoundAndroid myself. Thanks.
>
> On 25 April 2016 at 15:28, Victor Lazzarini 
> wrote:
>>
>> It’s still possible to use CsoundAndroid and the Eclipse projects, I have
>> been doing that
>> all along (because the project I work on has not moved to Android Studio).
>> That’s
>> directly from GIT. Once you have the NDK and libsndfile srcs, building the
>> jni interface
>> is straightforward.
>>
>> NB: the recommendation from Android Developers is to move to clang, so I
>> have updated
>> the .mk files to allow for that. At first hand, it appears to generate
>> more efficient binaries.
>>
>> ========================
>> 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 25 Apr 2016, at 14:41, Steven Yi  wrote:
>> >
>> > There was a lengthy discussion about moving to Android Studio and
>> > everything was done in the open. This was done in response to
>> > community requests to support Android Studio.  If you're using Csound
>> > 6.05, I'm assuming you're still using Eclipse?  Are you looking at
>> > files from Git or a binary release?    CsoundAndroid still contains
>> > all of the JNI and native files, and it is built using the build.sh
>> > script within that folder.  Afterwards, the update-android-studio.sh
>> > (found in the csound/android folder) is used to update the library in
>> > CsoundForAndroid/CsoundAndroid.
>> >
>> > On Mon, Apr 25, 2016 at 9:19 AM, Rory Walsh  wrote:
>> >> I'm just looking to upgrade some Android projects from Csound6.05 to
>> >> Csound6.06. Things seems to have changed completely here? There used to
>> >> be a
>> >> CsoundAndroid folder that contained everything I needed to develop
>> >> applications. Now there is a CsoundForAndroid folder. Where did
>> >> AndroidCsound.cpp/hpp go? I can't find any of the jni files that were
>> >> included in previous versions. It's frustrating when major changes like
>> >> this
>> >> happen because it means frontend developers have to go and rewrite a
>> >> lot of
>> >> make files in order to update their projects.
>> >> Csound mailing list Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> >> https://github.com/csound/csound/issues Discussions of bugs and
>> >> features can
>> >> be posted here
>> >
>> > Csound mailing list
>> > Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> > Send bugs reports to
>> >        https://github.com/csound/csound/issues
>> > Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

The build of the native library did not change.  The projects that are
packaged up for release were redone as an Android Studio project.
Previously, they were only packaged as Eclipse projects.  That you
were previously using them in Android Studio is great, but it wasn't
something we had designed for and, thus, I have no idea what process
you used or what are your expectations. The structure of the various
sub-projects should now adhere correctly for Android Studio to now
just open up and run. You should be able to import the CsoundAndroid
sub-project from the CsoundForAndroid folder to your existing project,
if I'm not mistaken.  And like I said, if there's a problem, just
explain what you're seeing and what you were expecting and we can look
at how to address it.



On Mon, Apr 25, 2016 at 2:59 PM, Rory Walsh  wrote:
> My point was why did it change when it worked fine with Android Studio in
> the past. You said it changed because users wanted to use it with Android
> Studio, but when was there ever a problem using Android Studio? Anyhow, I
> managed to roll my own hybrid monster that works Ok. I'll return to it again
> when I have more time.
>
> On 25 April 2016 at 19:53, Steven Yi  wrote:
>>
>> I'm not sure what the problem is, could you describe how you were
>> using it before and what you're seeing now?  I only tested as far as
>> the examples and Csound app applications and others reported having
>> success too with that at least.  If there's something else not
>> working, email the details.
>>
>> On Mon, Apr 25, 2016 at 11:19 AM, Rory Walsh  wrote:
>> > Thanks guys, I've no doubt it was discussed in an open and transparent
>> > way,
>> > it just seemed to slip under the radar for me. I've never used eclipse
>> > to
>> > build any my projects. I know it's not recommended, but I've been using
>> > ant
>> > to build the Android version of Cabbage.
>> >
>> > Steven: I've been using the zip files available on sourceforge. For what
>> > it's worth, I've never had any issue using these binaries in Android
>> > Studio.
>> > All the way back to Csound6.03. Two of my current (non-Cabbage) projects
>> > are
>> > built with Android Studio and they are using 6.05. What is the problem
>> > there? I guess I need to look over the archives. Perhaps some plugin
>> > libs
>> > were causing problems?
>> >
>> > Victor, I'll have ago at building CsoundAndroid myself. Thanks.
>> >
>> > On 25 April 2016 at 15:28, Victor Lazzarini 
>> > wrote:
>> >>
>> >> It’s still possible to use CsoundAndroid and the Eclipse projects, I
>> >> have
>> >> been doing that
>> >> all along (because the project I work on has not moved to Android
>> >> Studio).
>> >> That’s
>> >> directly from GIT. Once you have the NDK and libsndfile srcs, building
>> >> the
>> >> jni interface
>> >> is straightforward.
>> >>
>> >> NB: the recommendation from Android Developers is to move to clang, so
>> >> I
>> >> have updated
>> >> the .mk files to allow for that. At first hand, it appears to generate
>> >> more efficient binaries.
>> >>
>> >> ========================
>> >> 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 25 Apr 2016, at 14:41, Steven Yi  wrote:
>> >> >
>> >> > There was a lengthy discussion about moving to Android Studio and
>> >> > everything was done in the open. This was done in response to
>> >> > community requests to support Android Studio.  If you're using Csound
>> >> > 6.05, I'm assuming you're still using Eclipse?  Are you looking at
>> >> > files from Git or a binary release?    CsoundAndroid still contains
>> >> > all of the JNI and native files, and it is built using the build.sh
>> >> > script within that folder.  Afterwards, the update-android-studio.sh
>> >> > (found in the csound/android folder) is used to update the library in
>> >> > CsoundForAndroid/CsoundAndroid.
>> >> >
>> >> > On Mon, Apr 25, 2016 at 9:19 AM, Rory Walsh  wrote:
>> >> >> I'm just looking to upgrade some Android projects from Csound6.05 to
>> >> >> Csound6.06. Things seems to have changed completely here? There used
>> >> >> to
>> >> >> be a
>> >> >> CsoundAndroid folder that contained everything I needed to develop
>> >> >> applications. Now there is a CsoundForAndroid folder. Where did
>> >> >> AndroidCsound.cpp/hpp go? I can't find any of the jni files that
>> >> >> were
>> >> >> included in previous versions. It's frustrating when major changes
>> >> >> like
>> >> >> this
>> >> >> happen because it means frontend developers have to go and rewrite a
>> >> >> lot of
>> >> >> make files in order to update their projects.
>> >> >> Csound mailing list Csound@listserv.heanet.ie
>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> >> >> https://github.com/csound/csound/issues Discussions of bugs and
>> >> >> features can
>> >> >> be posted here
>> >> >
>> >> > Csound mailing list
>> >> > Csound@listserv.heanet.ie
>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> > Send bugs reports to
>> >> >        https://github.com/csound/csound/issues
>> >> > Discussions of bugs and features can be posted here
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> >
>> > Csound mailing list Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> > https://github.com/csound/csound/issues Discussions of bugs and features
>> > can
>> > be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

No worries.  This thread though does raise an issue that there could
be better information about the release for Android Studio and newer
practices around that.  We should probably review the README and the
documentation as I'm not sure I had updated those when organizing the
new projects for Android Studio.

On Mon, Apr 25, 2016 at 3:19 PM, Rory Walsh  wrote:
> Thanks Steven. I wasn't thinking of the applications that came with it. I
> just had a d'oh moment!
>
> On 25 April 2016 at 20:13, Steven Yi  wrote:
>>
>> The build of the native library did not change.  The projects that are
>> packaged up for release were redone as an Android Studio project.
>> Previously, they were only packaged as Eclipse projects.  That you
>> were previously using them in Android Studio is great, but it wasn't
>> something we had designed for and, thus, I have no idea what process
>> you used or what are your expectations. The structure of the various
>> sub-projects should now adhere correctly for Android Studio to now
>> just open up and run. You should be able to import the CsoundAndroid
>> sub-project from the CsoundForAndroid folder to your existing project,
>> if I'm not mistaken.  And like I said, if there's a problem, just
>> explain what you're seeing and what you were expecting and we can look
>> at how to address it.
>>
>>
>>
>> On Mon, Apr 25, 2016 at 2:59 PM, Rory Walsh  wrote:
>> > My point was why did it change when it worked fine with Android Studio
>> > in
>> > the past. You said it changed because users wanted to use it with
>> > Android
>> > Studio, but when was there ever a problem using Android Studio? Anyhow,
>> > I
>> > managed to roll my own hybrid monster that works Ok. I'll return to it
>> > again
>> > when I have more time.
>> >
>> > On 25 April 2016 at 19:53, Steven Yi  wrote:
>> >>
>> >> I'm not sure what the problem is, could you describe how you were
>> >> using it before and what you're seeing now?  I only tested as far as
>> >> the examples and Csound app applications and others reported having
>> >> success too with that at least.  If there's something else not
>> >> working, email the details.
>> >>
>> >> On Mon, Apr 25, 2016 at 11:19 AM, Rory Walsh  wrote:
>> >> > Thanks guys, I've no doubt it was discussed in an open and
>> >> > transparent
>> >> > way,
>> >> > it just seemed to slip under the radar for me. I've never used
>> >> > eclipse
>> >> > to
>> >> > build any my projects. I know it's not recommended, but I've been
>> >> > using
>> >> > ant
>> >> > to build the Android version of Cabbage.
>> >> >
>> >> > Steven: I've been using the zip files available on sourceforge. For
>> >> > what
>> >> > it's worth, I've never had any issue using these binaries in Android
>> >> > Studio.
>> >> > All the way back to Csound6.03. Two of my current (non-Cabbage)
>> >> > projects
>> >> > are
>> >> > built with Android Studio and they are using 6.05. What is the
>> >> > problem
>> >> > there? I guess I need to look over the archives. Perhaps some plugin
>> >> > libs
>> >> > were causing problems?
>> >> >
>> >> > Victor, I'll have ago at building CsoundAndroid myself. Thanks.
>> >> >
>> >> > On 25 April 2016 at 15:28, Victor Lazzarini
>> >> > 
>> >> > wrote:
>> >> >>
>> >> >> It’s still possible to use CsoundAndroid and the Eclipse projects, I
>> >> >> have
>> >> >> been doing that
>> >> >> all along (because the project I work on has not moved to Android
>> >> >> Studio).
>> >> >> That’s
>> >> >> directly from GIT. Once you have the NDK and libsndfile srcs,
>> >> >> building
>> >> >> the
>> >> >> jni interface
>> >> >> is straightforward.
>> >> >>
>> >> >> NB: the recommendation from Android Developers is to move to clang,
>> >> >> so
>> >> >> I
>> >> >> have updated
>> >> >> the .mk files to allow for that. At first hand, it appears to
>> >> >> generate
>> >> >> more efficient binaries.
>> >> >>
>> >> >> ========================
>> >> >> 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 25 Apr 2016, at 14:41, Steven Yi  wrote:
>> >> >> >
>> >> >> > There was a lengthy discussion about moving to Android Studio and
>> >> >> > everything was done in the open. This was done in response to
>> >> >> > community requests to support Android Studio.  If you're using
>> >> >> > Csound
>> >> >> > 6.05, I'm assuming you're still using Eclipse?  Are you looking at
>> >> >> > files from Git or a binary release?    CsoundAndroid still
>> >> >> > contains
>> >> >> > all of the JNI and native files, and it is built using the
>> >> >> > build.sh
>> >> >> > script within that folder.  Afterwards, the
>> >> >> > update-android-studio.sh
>> >> >> > (found in the csound/android folder) is used to update the library
>> >> >> > in
>> >> >> > CsoundForAndroid/CsoundAndroid.
>> >> >> >
>> >> >> > On Mon, Apr 25, 2016 at 9:19 AM, Rory Walsh 
>> >> >> > wrote:
>> >> >> >> I'm just looking to upgrade some Android projects from Csound6.05
>> >> >> >> to
>> >> >> >> Csound6.06. Things seems to have changed completely here? There
>> >> >> >> used
>> >> >> >> to
>> >> >> >> be a
>> >> >> >> CsoundAndroid folder that contained everything I needed to
>> >> >> >> develop
>> >> >> >> applications. Now there is a CsoundForAndroid folder. Where did
>> >> >> >> AndroidCsound.cpp/hpp go? I can't find any of the jni files that
>> >> >> >> were
>> >> >> >> included in previous versions. It's frustrating when major
>> >> >> >> changes
>> >> >> >> like
>> >> >> >> this
>> >> >> >> happen because it means frontend developers have to go and
>> >> >> >> rewrite a
>> >> >> >> lot of
>> >> >> >> make files in order to update their projects.
>> >> >> >> Csound mailing list Csound@listserv.heanet.ie
>> >> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>> >> >> >> to
>> >> >> >> https://github.com/csound/csound/issues Discussions of bugs and
>> >> >> >> features can
>> >> >> >> be posted here
>> >> >> >
>> >> >> > Csound mailing list
>> >> >> > Csound@listserv.heanet.ie
>> >> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> >> > Send bugs reports to
>> >> >> >        https://github.com/csound/csound/issues
>> >> >> > Discussions of bugs and features can be posted here
>> >> >>
>> >> >> Csound mailing list
>> >> >> Csound@listserv.heanet.ie
>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> >> Send bugs reports to
>> >> >>         https://github.com/csound/csound/issues
>> >> >> Discussions of bugs and features can be posted here
>> >> >
>> >> >
>> >> > Csound mailing list Csound@listserv.heanet.ie
>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> >> > https://github.com/csound/csound/issues Discussions of bugs and
>> >> > features
>> >> > can
>> >> > be posted here
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> >
>> > Csound mailing list Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> > https://github.com/csound/csound/issues Discussions of bugs and features
>> > can
>> > be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here