Is there a way of using my plugin opcodes on android device while
using the old Csound android app?

Pete

Yes, you will need to compile it as a plugin for the appropriate CPU
architecture (mostly likely just armeabi-v7a will do just fine to
start). You will also need to have the opcode library loaded by
Csound.  I think you can use a --opcode-lib=/path/to/lib flag in
CsOptions to do this (note: I have not tested this approach).  Michael
or others could probably comment if a folder is designated as
OPCODE6DIR by the application, or if that can be set by the user.

To build the plugin, you will need the Android Native Development Kit
(NDK).  After that, it's probably easiest to download a copy of the
Csound sources, go into the android/pluginlibs folder, and then copy
one of the existing plugin project folders and adjust for your own
plugin opcode.

On Fri, Mar 25, 2016 at 12:48 PM, Peter Burgess
 wrote:
> Is there a way of using my plugin opcodes on android device while
> using the old Csound android app?
>
> Pete
>
> --
> http://algorythmradio.com
> https://soundcloud.com/algorythmradio
>
> 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

Ah right, I can set the full path in the options rather than just the
filename. That's alright, that gives me some options.

I'd quite forgotten I'll have to build the pluggins for android, but I
need to get up and running on the android development soon anyway,
could be a good test run! I've got the NDK already, but haven't set up
an android compiler yet.

To divert somewhat from my question, have you ever built for android
outside of android studio before? I'm hoping to set up all my cross
build environments in a single IDE, which is currently CodeBlocks.
Windows was easy enough to set up, but I spent ages reading about it
for android, and watching videos, and it sounded like the normal
practice was to just use android studio.

Cheers very much!

Pete

On Fri, Mar 25, 2016 at 4:59 PM, Steven Yi  wrote:
> Yes, you will need to compile it as a plugin for the appropriate CPU
> architecture (mostly likely just armeabi-v7a will do just fine to
> start). You will also need to have the opcode library loaded by
> Csound.  I think you can use a --opcode-lib=/path/to/lib flag in
> CsOptions to do this (note: I have not tested this approach).  Michael
> or others could probably comment if a folder is designated as
> OPCODE6DIR by the application, or if that can be set by the user.
>
> To build the plugin, you will need the Android Native Development Kit
> (NDK).  After that, it's probably easiest to download a copy of the
> Csound sources, go into the android/pluginlibs folder, and then copy
> one of the existing plugin project folders and adjust for your own
> plugin opcode.
>
> On Fri, Mar 25, 2016 at 12:48 PM, Peter Burgess
>  wrote:
>> Is there a way of using my plugin opcodes on android device while
>> using the old Csound android app?
>>
>> Pete
>>
>> --
>> http://algorythmradio.com
>> https://soundcloud.com/algorythmradio
>>
>> 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

For what it's worth I use -opcode-lib to include to OSC Opcode's with Cabbage on Android. You should probably make sure you are building your plugin with the same API. There have been quite a few bumps in the past years.

what do you mean by the same API?

On Fri, Mar 25, 2016 at 5:16 PM, Rory Walsh  wrote:
> For what it's worth I use -opcode-lib to include to OSC Opcode's with
> Cabbage on Android. You should probably make sure you are building your
> plugin with the same API. There have been quite a few bumps in the past
> years.
>
> On 25 Mar 2016 17:59, "Steven Yi"  wrote:
>>
>> Yes, you will need to compile it as a plugin for the appropriate CPU
>> architecture (mostly likely just armeabi-v7a will do just fine to
>> start). You will also need to have the opcode library loaded by
>> Csound.  I think you can use a --opcode-lib=/path/to/lib flag in
>> CsOptions to do this (note: I have not tested this approach).  Michael
>> or others could probably comment if a folder is designated as
>> OPCODE6DIR by the application, or if that can be set by the user.
>>
>> To build the plugin, you will need the Android Native Development Kit
>> (NDK).  After that, it's probably easiest to download a copy of the
>> Csound sources, go into the android/pluginlibs folder, and then copy
>> one of the existing plugin project folders and adjust for your own
>> plugin opcode.
>>
>> On Fri, Mar 25, 2016 at 12:48 PM, Peter Burgess
>>  wrote:
>> > Is there a way of using my plugin opcodes on android device while
>> > using the old Csound android app?
>> >
>> > Pete
>> >
>> > --
>> > http://algorythmradio.com
>> > https://soundcloud.com/algorythmradio
>> >
>> > 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 have not done any Android development outside of the standard
environments (previously, Eclipse, and currently, Android Studio).
Android Studio uses the Gradle build system now, which can be run on
its own outside of the IDE.  Other than that, I don't have much
experience with CodeBlocks so cannot offer much other advice.  Good
luck on getting it all working!

steven

On Fri, Mar 25, 2016 at 1:14 PM, Peter Burgess
 wrote:
> Ah right, I can set the full path in the options rather than just the
> filename. That's alright, that gives me some options.
>
> I'd quite forgotten I'll have to build the pluggins for android, but I
> need to get up and running on the android development soon anyway,
> could be a good test run! I've got the NDK already, but haven't set up
> an android compiler yet.
>
> To divert somewhat from my question, have you ever built for android
> outside of android studio before? I'm hoping to set up all my cross
> build environments in a single IDE, which is currently CodeBlocks.
> Windows was easy enough to set up, but I spent ages reading about it
> for android, and watching videos, and it sounded like the normal
> practice was to just use android studio.
>
> Cheers very much!
>
> Pete
>
> On Fri, Mar 25, 2016 at 4:59 PM, Steven Yi  wrote:
>> Yes, you will need to compile it as a plugin for the appropriate CPU
>> architecture (mostly likely just armeabi-v7a will do just fine to
>> start). You will also need to have the opcode library loaded by
>> Csound.  I think you can use a --opcode-lib=/path/to/lib flag in
>> CsOptions to do this (note: I have not tested this approach).  Michael
>> or others could probably comment if a folder is designated as
>> OPCODE6DIR by the application, or if that can be set by the user.
>>
>> To build the plugin, you will need the Android Native Development Kit
>> (NDK).  After that, it's probably easiest to download a copy of the
>> Csound sources, go into the android/pluginlibs folder, and then copy
>> one of the existing plugin project folders and adjust for your own
>> plugin opcode.
>>
>> On Fri, Mar 25, 2016 at 12:48 PM, Peter Burgess
>>  wrote:
>>> Is there a way of using my plugin opcodes on android device while
>>> using the old Csound android app?
>>>
>>> Pete
>>>
>>> --
>>> http://algorythmradio.com
>>> https://soundcloud.com/algorythmradio
>>>
>>> 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
>
>
>
> --
> http://algorythmradio.com
> https://soundcloud.com/algorythmradio
>
> 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

In general I would advise using the tools most other people on the
platform use. Particularly if the platform is complex as Android is.

Regards,
Mike

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


On Fri, Mar 25, 2016 at 8:34 PM, Steven Yi  wrote:
> I have not done any Android development outside of the standard
> environments (previously, Eclipse, and currently, Android Studio).
> Android Studio uses the Gradle build system now, which can be run on
> its own outside of the IDE.  Other than that, I don't have much
> experience with CodeBlocks so cannot offer much other advice.  Good
> luck on getting it all working!
>
> steven
>
> On Fri, Mar 25, 2016 at 1:14 PM, Peter Burgess
>  wrote:
>> Ah right, I can set the full path in the options rather than just the
>> filename. That's alright, that gives me some options.
>>
>> I'd quite forgotten I'll have to build the pluggins for android, but I
>> need to get up and running on the android development soon anyway,
>> could be a good test run! I've got the NDK already, but haven't set up
>> an android compiler yet.
>>
>> To divert somewhat from my question, have you ever built for android
>> outside of android studio before? I'm hoping to set up all my cross
>> build environments in a single IDE, which is currently CodeBlocks.
>> Windows was easy enough to set up, but I spent ages reading about it
>> for android, and watching videos, and it sounded like the normal
>> practice was to just use android studio.
>>
>> Cheers very much!
>>
>> Pete
>>
>> On Fri, Mar 25, 2016 at 4:59 PM, Steven Yi  wrote:
>>> Yes, you will need to compile it as a plugin for the appropriate CPU
>>> architecture (mostly likely just armeabi-v7a will do just fine to
>>> start). You will also need to have the opcode library loaded by
>>> Csound.  I think you can use a --opcode-lib=/path/to/lib flag in
>>> CsOptions to do this (note: I have not tested this approach).  Michael
>>> or others could probably comment if a folder is designated as
>>> OPCODE6DIR by the application, or if that can be set by the user.
>>>
>>> To build the plugin, you will need the Android Native Development Kit
>>> (NDK).  After that, it's probably easiest to download a copy of the
>>> Csound sources, go into the android/pluginlibs folder, and then copy
>>> one of the existing plugin project folders and adjust for your own
>>> plugin opcode.
>>>
>>> On Fri, Mar 25, 2016 at 12:48 PM, Peter Burgess
>>>  wrote:
>>>> Is there a way of using my plugin opcodes on android device while
>>>> using the old Csound android app?
>>>>
>>>> Pete
>>>>
>>>> --
>>>> http://algorythmradio.com
>>>> https://soundcloud.com/algorythmradio
>>>>
>>>> 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
>>
>>
>>
>> --
>> http://algorythmradio.com
>> https://soundcloud.com/algorythmradio
>>
>> 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

Cool, that's probably good advice. maybe once I've used android studio
for a while and actually built some android bits and pieces, then I
can think about moving it to codeblocks

On Fri, Mar 25, 2016 at 5:44 PM, Michael Gogins
 wrote:
> In general I would advise using the tools most other people on the
> platform use. Particularly if the platform is complex as Android is.
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Fri, Mar 25, 2016 at 8:34 PM, Steven Yi  wrote:
>> I have not done any Android development outside of the standard
>> environments (previously, Eclipse, and currently, Android Studio).
>> Android Studio uses the Gradle build system now, which can be run on
>> its own outside of the IDE.  Other than that, I don't have much
>> experience with CodeBlocks so cannot offer much other advice.  Good
>> luck on getting it all working!
>>
>> steven
>>
>> On Fri, Mar 25, 2016 at 1:14 PM, Peter Burgess
>>  wrote:
>>> Ah right, I can set the full path in the options rather than just the
>>> filename. That's alright, that gives me some options.
>>>
>>> I'd quite forgotten I'll have to build the pluggins for android, but I
>>> need to get up and running on the android development soon anyway,
>>> could be a good test run! I've got the NDK already, but haven't set up
>>> an android compiler yet.
>>>
>>> To divert somewhat from my question, have you ever built for android
>>> outside of android studio before? I'm hoping to set up all my cross
>>> build environments in a single IDE, which is currently CodeBlocks.
>>> Windows was easy enough to set up, but I spent ages reading about it
>>> for android, and watching videos, and it sounded like the normal
>>> practice was to just use android studio.
>>>
>>> Cheers very much!
>>>
>>> Pete
>>>
>>> On Fri, Mar 25, 2016 at 4:59 PM, Steven Yi  wrote:
>>>> Yes, you will need to compile it as a plugin for the appropriate CPU
>>>> architecture (mostly likely just armeabi-v7a will do just fine to
>>>> start). You will also need to have the opcode library loaded by
>>>> Csound.  I think you can use a --opcode-lib=/path/to/lib flag in
>>>> CsOptions to do this (note: I have not tested this approach).  Michael
>>>> or others could probably comment if a folder is designated as
>>>> OPCODE6DIR by the application, or if that can be set by the user.
>>>>
>>>> To build the plugin, you will need the Android Native Development Kit
>>>> (NDK).  After that, it's probably easiest to download a copy of the
>>>> Csound sources, go into the android/pluginlibs folder, and then copy
>>>> one of the existing plugin project folders and adjust for your own
>>>> plugin opcode.
>>>>
>>>> On Fri, Mar 25, 2016 at 12:48 PM, Peter Burgess
>>>>  wrote:
>>>>> Is there a way of using my plugin opcodes on android device while
>>>>> using the old Csound android app?
>>>>>
>>>>> Pete
>>>>>
>>>>> --
>>>>> http://algorythmradio.com
>>>>> https://soundcloud.com/algorythmradio
>>>>>
>>>>> 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
>>>
>>>
>>>
>>> --
>>> http://algorythmradio.com
>>> https://soundcloud.com/algorythmradio
>>>
>>> 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

Sorry, to correct one thing I mentioned, standard Android projects
(i.e., Java) are built using Gradle. I haven't followed if gradle
support for NDK is now standard or if still experimental.  For
building NDK stuff, particularly Csound opcode plugins, you need only
use the NDK's build tools to build from a ccommandline or from and
IDE.

On Fri, Mar 25, 2016 at 2:07 PM, Peter Burgess
 wrote:
> Cool, that's probably good advice. maybe once I've used android studio
> for a while and actually built some android bits and pieces, then I
> can think about moving it to codeblocks
>
> On Fri, Mar 25, 2016 at 5:44 PM, Michael Gogins
>  wrote:
>> In general I would advise using the tools most other people on the
>> platform use. Particularly if the platform is complex as Android is.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Fri, Mar 25, 2016 at 8:34 PM, Steven Yi  wrote:
>>> I have not done any Android development outside of the standard
>>> environments (previously, Eclipse, and currently, Android Studio).
>>> Android Studio uses the Gradle build system now, which can be run on
>>> its own outside of the IDE.  Other than that, I don't have much
>>> experience with CodeBlocks so cannot offer much other advice.  Good
>>> luck on getting it all working!
>>>
>>> steven
>>>
>>> On Fri, Mar 25, 2016 at 1:14 PM, Peter Burgess
>>>  wrote:
>>>> Ah right, I can set the full path in the options rather than just the
>>>> filename. That's alright, that gives me some options.
>>>>
>>>> I'd quite forgotten I'll have to build the pluggins for android, but I
>>>> need to get up and running on the android development soon anyway,
>>>> could be a good test run! I've got the NDK already, but haven't set up
>>>> an android compiler yet.
>>>>
>>>> To divert somewhat from my question, have you ever built for android
>>>> outside of android studio before? I'm hoping to set up all my cross
>>>> build environments in a single IDE, which is currently CodeBlocks.
>>>> Windows was easy enough to set up, but I spent ages reading about it
>>>> for android, and watching videos, and it sounded like the normal
>>>> practice was to just use android studio.
>>>>
>>>> Cheers very much!
>>>>
>>>> Pete
>>>>
>>>> On Fri, Mar 25, 2016 at 4:59 PM, Steven Yi  wrote:
>>>>> Yes, you will need to compile it as a plugin for the appropriate CPU
>>>>> architecture (mostly likely just armeabi-v7a will do just fine to
>>>>> start). You will also need to have the opcode library loaded by
>>>>> Csound.  I think you can use a --opcode-lib=/path/to/lib flag in
>>>>> CsOptions to do this (note: I have not tested this approach).  Michael
>>>>> or others could probably comment if a folder is designated as
>>>>> OPCODE6DIR by the application, or if that can be set by the user.
>>>>>
>>>>> To build the plugin, you will need the Android Native Development Kit
>>>>> (NDK).  After that, it's probably easiest to download a copy of the
>>>>> Csound sources, go into the android/pluginlibs folder, and then copy
>>>>> one of the existing plugin project folders and adjust for your own
>>>>> plugin opcode.
>>>>>
>>>>> On Fri, Mar 25, 2016 at 12:48 PM, Peter Burgess
>>>>>  wrote:
>>>>>> Is there a way of using my plugin opcodes on android device while
>>>>>> using the old Csound android app?
>>>>>>
>>>>>> Pete
>>>>>>
>>>>>> --
>>>>>> http://algorythmradio.com
>>>>>> https://soundcloud.com/algorythmradio
>>>>>>
>>>>>> 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
>>>>
>>>>
>>>>
>>>> --
>>>> http://algorythmradio.com
>>>> https://soundcloud.com/algorythmradio
>>>>
>>>> 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
>
>
>
> --
> http://algorythmradio.com
> https://soundcloud.com/algorythmradio
>
> 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

Ah, is that because Csound is running the pluggin, so it doesn't
directly need java compatibility?

On Fri, Mar 25, 2016 at 6:13 PM, Steven Yi  wrote:
> Sorry, to correct one thing I mentioned, standard Android projects
> (i.e., Java) are built using Gradle. I haven't followed if gradle
> support for NDK is now standard or if still experimental.  For
> building NDK stuff, particularly Csound opcode plugins, you need only
> use the NDK's build tools to build from a ccommandline or from and
> IDE.
>
> On Fri, Mar 25, 2016 at 2:07 PM, Peter Burgess
>  wrote:
>> Cool, that's probably good advice. maybe once I've used android studio
>> for a while and actually built some android bits and pieces, then I
>> can think about moving it to codeblocks
>>
>> On Fri, Mar 25, 2016 at 5:44 PM, Michael Gogins
>>  wrote:
>>> In general I would advise using the tools most other people on the
>>> platform use. Particularly if the platform is complex as Android is.
>>>
>>> Regards,
>>> Mike
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Fri, Mar 25, 2016 at 8:34 PM, Steven Yi  wrote:
>>>> I have not done any Android development outside of the standard
>>>> environments (previously, Eclipse, and currently, Android Studio).
>>>> Android Studio uses the Gradle build system now, which can be run on
>>>> its own outside of the IDE.  Other than that, I don't have much
>>>> experience with CodeBlocks so cannot offer much other advice.  Good
>>>> luck on getting it all working!
>>>>
>>>> steven
>>>>
>>>> On Fri, Mar 25, 2016 at 1:14 PM, Peter Burgess
>>>>  wrote:
>>>>> Ah right, I can set the full path in the options rather than just the
>>>>> filename. That's alright, that gives me some options.
>>>>>
>>>>> I'd quite forgotten I'll have to build the pluggins for android, but I
>>>>> need to get up and running on the android development soon anyway,
>>>>> could be a good test run! I've got the NDK already, but haven't set up
>>>>> an android compiler yet.
>>>>>
>>>>> To divert somewhat from my question, have you ever built for android
>>>>> outside of android studio before? I'm hoping to set up all my cross
>>>>> build environments in a single IDE, which is currently CodeBlocks.
>>>>> Windows was easy enough to set up, but I spent ages reading about it
>>>>> for android, and watching videos, and it sounded like the normal
>>>>> practice was to just use android studio.
>>>>>
>>>>> Cheers very much!
>>>>>
>>>>> Pete
>>>>>
>>>>> On Fri, Mar 25, 2016 at 4:59 PM, Steven Yi  wrote:
>>>>>> Yes, you will need to compile it as a plugin for the appropriate CPU
>>>>>> architecture (mostly likely just armeabi-v7a will do just fine to
>>>>>> start). You will also need to have the opcode library loaded by
>>>>>> Csound.  I think you can use a --opcode-lib=/path/to/lib flag in
>>>>>> CsOptions to do this (note: I have not tested this approach).  Michael
>>>>>> or others could probably comment if a folder is designated as
>>>>>> OPCODE6DIR by the application, or if that can be set by the user.
>>>>>>
>>>>>> To build the plugin, you will need the Android Native Development Kit
>>>>>> (NDK).  After that, it's probably easiest to download a copy of the
>>>>>> Csound sources, go into the android/pluginlibs folder, and then copy
>>>>>> one of the existing plugin project folders and adjust for your own
>>>>>> plugin opcode.
>>>>>>
>>>>>> On Fri, Mar 25, 2016 at 12:48 PM, Peter Burgess
>>>>>>  wrote:
>>>>>>> Is there a way of using my plugin opcodes on android device while
>>>>>>> using the old Csound android app?
>>>>>>>
>>>>>>> Pete
>>>>>>>
>>>>>>> --
>>>>>>> http://algorythmradio.com
>>>>>>> https://soundcloud.com/algorythmradio
>>>>>>>
>>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> http://algorythmradio.com
>>>>> https://soundcloud.com/algorythmradio
>>>>>
>>>>> 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
>>
>>
>>
>> --
>> http://algorythmradio.com
>> https://soundcloud.com/algorythmradio
>>
>> 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 runs as a native library in a Java library in a Java app.

Regards,
Mike

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


On Fri, Mar 25, 2016 at 9:15 PM, Peter Burgess
 wrote:
> Ah, is that because Csound is running the pluggin, so it doesn't
> directly need java compatibility?
>
> On Fri, Mar 25, 2016 at 6:13 PM, Steven Yi  wrote:
>> Sorry, to correct one thing I mentioned, standard Android projects
>> (i.e., Java) are built using Gradle. I haven't followed if gradle
>> support for NDK is now standard or if still experimental.  For
>> building NDK stuff, particularly Csound opcode plugins, you need only
>> use the NDK's build tools to build from a ccommandline or from and
>> IDE.
>>
>> On Fri, Mar 25, 2016 at 2:07 PM, Peter Burgess
>>  wrote:
>>> Cool, that's probably good advice. maybe once I've used android studio
>>> for a while and actually built some android bits and pieces, then I
>>> can think about moving it to codeblocks
>>>
>>> On Fri, Mar 25, 2016 at 5:44 PM, Michael Gogins
>>>  wrote:
>>>> In general I would advise using the tools most other people on the
>>>> platform use. Particularly if the platform is complex as Android is.
>>>>
>>>> Regards,
>>>> Mike
>>>>
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>> On Fri, Mar 25, 2016 at 8:34 PM, Steven Yi  wrote:
>>>>> I have not done any Android development outside of the standard
>>>>> environments (previously, Eclipse, and currently, Android Studio).
>>>>> Android Studio uses the Gradle build system now, which can be run on
>>>>> its own outside of the IDE.  Other than that, I don't have much
>>>>> experience with CodeBlocks so cannot offer much other advice.  Good
>>>>> luck on getting it all working!
>>>>>
>>>>> steven
>>>>>
>>>>> On Fri, Mar 25, 2016 at 1:14 PM, Peter Burgess
>>>>>  wrote:
>>>>>> Ah right, I can set the full path in the options rather than just the
>>>>>> filename. That's alright, that gives me some options.
>>>>>>
>>>>>> I'd quite forgotten I'll have to build the pluggins for android, but I
>>>>>> need to get up and running on the android development soon anyway,
>>>>>> could be a good test run! I've got the NDK already, but haven't set up
>>>>>> an android compiler yet.
>>>>>>
>>>>>> To divert somewhat from my question, have you ever built for android
>>>>>> outside of android studio before? I'm hoping to set up all my cross
>>>>>> build environments in a single IDE, which is currently CodeBlocks.
>>>>>> Windows was easy enough to set up, but I spent ages reading about it
>>>>>> for android, and watching videos, and it sounded like the normal
>>>>>> practice was to just use android studio.
>>>>>>
>>>>>> Cheers very much!
>>>>>>
>>>>>> Pete
>>>>>>
>>>>>> On Fri, Mar 25, 2016 at 4:59 PM, Steven Yi  wrote:
>>>>>>> Yes, you will need to compile it as a plugin for the appropriate CPU
>>>>>>> architecture (mostly likely just armeabi-v7a will do just fine to
>>>>>>> start). You will also need to have the opcode library loaded by
>>>>>>> Csound.  I think you can use a --opcode-lib=/path/to/lib flag in
>>>>>>> CsOptions to do this (note: I have not tested this approach).  Michael
>>>>>>> or others could probably comment if a folder is designated as
>>>>>>> OPCODE6DIR by the application, or if that can be set by the user.
>>>>>>>
>>>>>>> To build the plugin, you will need the Android Native Development Kit
>>>>>>> (NDK).  After that, it's probably easiest to download a copy of the
>>>>>>> Csound sources, go into the android/pluginlibs folder, and then copy
>>>>>>> one of the existing plugin project folders and adjust for your own
>>>>>>> plugin opcode.
>>>>>>>
>>>>>>> On Fri, Mar 25, 2016 at 12:48 PM, Peter Burgess
>>>>>>>  wrote:
>>>>>>>> Is there a way of using my plugin opcodes on android device while
>>>>>>>> using the old Csound android app?
>>>>>>>>
>>>>>>>> Pete
>>>>>>>>
>>>>>>>> --
>>>>>>>> http://algorythmradio.com
>>>>>>>> https://soundcloud.com/algorythmradio
>>>>>>>>
>>>>>>>> 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
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> http://algorythmradio.com
>>>>>> https://soundcloud.com/algorythmradio
>>>>>>
>>>>>> 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
>>>
>>>
>>>
>>> --
>>> http://algorythmradio.com
>>> https://soundcloud.com/algorythmradio
>>>
>>> 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
>
>
>
> --
> http://algorythmradio.com
> https://soundcloud.com/algorythmradio
>
> 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

Sorry, I still don't entirely follow... Are you saying that Csound
runs in java, but the pluggin won't need to be built with gradle
because it is interfacing with java through Csound? Or just that NDK
stuff doesn't need gradle in general?

On Fri, Mar 25, 2016 at 6:22 PM, Michael Gogins
 wrote:
> Csound runs as a native library in a Java library in a Java app.
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Fri, Mar 25, 2016 at 9:15 PM, Peter Burgess
>  wrote:
>> Ah, is that because Csound is running the pluggin, so it doesn't
>> directly need java compatibility?
>>
>> On Fri, Mar 25, 2016 at 6:13 PM, Steven Yi  wrote:
>>> Sorry, to correct one thing I mentioned, standard Android projects
>>> (i.e., Java) are built using Gradle. I haven't followed if gradle
>>> support for NDK is now standard or if still experimental.  For
>>> building NDK stuff, particularly Csound opcode plugins, you need only
>>> use the NDK's build tools to build from a ccommandline or from and
>>> IDE.
>>>
>>> On Fri, Mar 25, 2016 at 2:07 PM, Peter Burgess
>>>  wrote:
>>>> Cool, that's probably good advice. maybe once I've used android studio
>>>> for a while and actually built some android bits and pieces, then I
>>>> can think about moving it to codeblocks
>>>>
>>>> On Fri, Mar 25, 2016 at 5:44 PM, Michael Gogins
>>>>  wrote:
>>>>> In general I would advise using the tools most other people on the
>>>>> platform use. Particularly if the platform is complex as Android is.
>>>>>
>>>>> Regards,
>>>>> Mike
>>>>>
>>>>> -----------------------------------------------------
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://michaelgogins.tumblr.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>>
>>>>> On Fri, Mar 25, 2016 at 8:34 PM, Steven Yi  wrote:
>>>>>> I have not done any Android development outside of the standard
>>>>>> environments (previously, Eclipse, and currently, Android Studio).
>>>>>> Android Studio uses the Gradle build system now, which can be run on
>>>>>> its own outside of the IDE.  Other than that, I don't have much
>>>>>> experience with CodeBlocks so cannot offer much other advice.  Good
>>>>>> luck on getting it all working!
>>>>>>
>>>>>> steven
>>>>>>
>>>>>> On Fri, Mar 25, 2016 at 1:14 PM, Peter Burgess
>>>>>>  wrote:
>>>>>>> Ah right, I can set the full path in the options rather than just the
>>>>>>> filename. That's alright, that gives me some options.
>>>>>>>
>>>>>>> I'd quite forgotten I'll have to build the pluggins for android, but I
>>>>>>> need to get up and running on the android development soon anyway,
>>>>>>> could be a good test run! I've got the NDK already, but haven't set up
>>>>>>> an android compiler yet.
>>>>>>>
>>>>>>> To divert somewhat from my question, have you ever built for android
>>>>>>> outside of android studio before? I'm hoping to set up all my cross
>>>>>>> build environments in a single IDE, which is currently CodeBlocks.
>>>>>>> Windows was easy enough to set up, but I spent ages reading about it
>>>>>>> for android, and watching videos, and it sounded like the normal
>>>>>>> practice was to just use android studio.
>>>>>>>
>>>>>>> Cheers very much!
>>>>>>>
>>>>>>> Pete
>>>>>>>
>>>>>>> On Fri, Mar 25, 2016 at 4:59 PM, Steven Yi  wrote:
>>>>>>>> Yes, you will need to compile it as a plugin for the appropriate CPU
>>>>>>>> architecture (mostly likely just armeabi-v7a will do just fine to
>>>>>>>> start). You will also need to have the opcode library loaded by
>>>>>>>> Csound.  I think you can use a --opcode-lib=/path/to/lib flag in
>>>>>>>> CsOptions to do this (note: I have not tested this approach).  Michael
>>>>>>>> or others could probably comment if a folder is designated as
>>>>>>>> OPCODE6DIR by the application, or if that can be set by the user.
>>>>>>>>
>>>>>>>> To build the plugin, you will need the Android Native Development Kit
>>>>>>>> (NDK).  After that, it's probably easiest to download a copy of the
>>>>>>>> Csound sources, go into the android/pluginlibs folder, and then copy
>>>>>>>> one of the existing plugin project folders and adjust for your own
>>>>>>>> plugin opcode.
>>>>>>>>
>>>>>>>> On Fri, Mar 25, 2016 at 12:48 PM, Peter Burgess
>>>>>>>>  wrote:
>>>>>>>>> Is there a way of using my plugin opcodes on android device while
>>>>>>>>> using the old Csound android app?
>>>>>>>>>
>>>>>>>>> Pete
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> http://algorythmradio.com
>>>>>>>>> https://soundcloud.com/algorythmradio
>>>>>>>>>
>>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> http://algorythmradio.com
>>>>>>> https://soundcloud.com/algorythmradio
>>>>>>>
>>>>>>> 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
>>>>
>>>>
>>>>
>>>> --
>>>> http://algorythmradio.com
>>>> https://soundcloud.com/algorythmradio
>>>>
>>>> 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
>>
>>
>>
>> --
>> http://algorythmradio.com
>> https://soundcloud.com/algorythmradio
>>
>> 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 does not matter how the plugin is built, as it simply ends up as a
native shared library. We build plugins with NDK command line
tools.Apparently they can also be built with gradle but I hate having
to learn a new build system every time somebody invents one.

The user interface and framework of the app is written in Java.

Csound itself is a native shared library that the app loads using JNI
(Java Native Interface).

Csound itself uses regular C system calls to load the plugin shared libraries.

Hope this is clearer,
Mike

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


On Fri, Mar 25, 2016 at 9:36 PM, Peter Burgess
 wrote:
> Sorry, I still don't entirely follow... Are you saying that Csound
> runs in java, but the pluggin won't need to be built with gradle
> because it is interfacing with java through Csound? Or just that NDK
> stuff doesn't need gradle in general?
>
> On Fri, Mar 25, 2016 at 6:22 PM, Michael Gogins
>  wrote:
>> Csound runs as a native library in a Java library in a Java app.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Fri, Mar 25, 2016 at 9:15 PM, Peter Burgess
>>  wrote:
>>> Ah, is that because Csound is running the pluggin, so it doesn't
>>> directly need java compatibility?
>>>
>>> On Fri, Mar 25, 2016 at 6:13 PM, Steven Yi  wrote:
>>>> Sorry, to correct one thing I mentioned, standard Android projects
>>>> (i.e., Java) are built using Gradle. I haven't followed if gradle
>>>> support for NDK is now standard or if still experimental.  For
>>>> building NDK stuff, particularly Csound opcode plugins, you need only
>>>> use the NDK's build tools to build from a ccommandline or from and
>>>> IDE.
>>>>
>>>> On Fri, Mar 25, 2016 at 2:07 PM, Peter Burgess
>>>>  wrote:
>>>>> Cool, that's probably good advice. maybe once I've used android studio
>>>>> for a while and actually built some android bits and pieces, then I
>>>>> can think about moving it to codeblocks
>>>>>
>>>>> On Fri, Mar 25, 2016 at 5:44 PM, Michael Gogins
>>>>>  wrote:
>>>>>> In general I would advise using the tools most other people on the
>>>>>> platform use. Particularly if the platform is complex as Android is.
>>>>>>
>>>>>> Regards,
>>>>>> Mike
>>>>>>
>>>>>> -----------------------------------------------------
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://michaelgogins.tumblr.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>>
>>>>>>
>>>>>> On Fri, Mar 25, 2016 at 8:34 PM, Steven Yi  wrote:
>>>>>>> I have not done any Android development outside of the standard
>>>>>>> environments (previously, Eclipse, and currently, Android Studio).
>>>>>>> Android Studio uses the Gradle build system now, which can be run on
>>>>>>> its own outside of the IDE.  Other than that, I don't have much
>>>>>>> experience with CodeBlocks so cannot offer much other advice.  Good
>>>>>>> luck on getting it all working!
>>>>>>>
>>>>>>> steven
>>>>>>>
>>>>>>> On Fri, Mar 25, 2016 at 1:14 PM, Peter Burgess
>>>>>>>  wrote:
>>>>>>>> Ah right, I can set the full path in the options rather than just the
>>>>>>>> filename. That's alright, that gives me some options.
>>>>>>>>
>>>>>>>> I'd quite forgotten I'll have to build the pluggins for android, but I
>>>>>>>> need to get up and running on the android development soon anyway,
>>>>>>>> could be a good test run! I've got the NDK already, but haven't set up
>>>>>>>> an android compiler yet.
>>>>>>>>
>>>>>>>> To divert somewhat from my question, have you ever built for android
>>>>>>>> outside of android studio before? I'm hoping to set up all my cross
>>>>>>>> build environments in a single IDE, which is currently CodeBlocks.
>>>>>>>> Windows was easy enough to set up, but I spent ages reading about it
>>>>>>>> for android, and watching videos, and it sounded like the normal
>>>>>>>> practice was to just use android studio.
>>>>>>>>
>>>>>>>> Cheers very much!
>>>>>>>>
>>>>>>>> Pete
>>>>>>>>
>>>>>>>> On Fri, Mar 25, 2016 at 4:59 PM, Steven Yi  wrote:
>>>>>>>>> Yes, you will need to compile it as a plugin for the appropriate CPU
>>>>>>>>> architecture (mostly likely just armeabi-v7a will do just fine to
>>>>>>>>> start). You will also need to have the opcode library loaded by
>>>>>>>>> Csound.  I think you can use a --opcode-lib=/path/to/lib flag in
>>>>>>>>> CsOptions to do this (note: I have not tested this approach).  Michael
>>>>>>>>> or others could probably comment if a folder is designated as
>>>>>>>>> OPCODE6DIR by the application, or if that can be set by the user.
>>>>>>>>>
>>>>>>>>> To build the plugin, you will need the Android Native Development Kit
>>>>>>>>> (NDK).  After that, it's probably easiest to download a copy of the
>>>>>>>>> Csound sources, go into the android/pluginlibs folder, and then copy
>>>>>>>>> one of the existing plugin project folders and adjust for your own
>>>>>>>>> plugin opcode.
>>>>>>>>>
>>>>>>>>> On Fri, Mar 25, 2016 at 12:48 PM, Peter Burgess
>>>>>>>>>  wrote:
>>>>>>>>>> Is there a way of using my plugin opcodes on android device while
>>>>>>>>>> using the old Csound android app?
>>>>>>>>>>
>>>>>>>>>> Pete
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> http://algorythmradio.com
>>>>>>>>>> https://soundcloud.com/algorythmradio
>>>>>>>>>>
>>>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> http://algorythmradio.com
>>>>>>>> https://soundcloud.com/algorythmradio
>>>>>>>>
>>>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> http://algorythmradio.com
>>>>> https://soundcloud.com/algorythmradio
>>>>>
>>>>> 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
>>>
>>>
>>>
>>> --
>>> http://algorythmradio.com
>>> https://soundcloud.com/algorythmradio
>>>
>>> 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
>
>
>
> --
> http://algorythmradio.com
> https://soundcloud.com/algorythmradio
>
> 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

ok excellent, that's much clearer in my head now, cheers! :D

Pete

On Fri, Mar 25, 2016 at 6:46 PM, Michael Gogins
 wrote:
> It does not matter how the plugin is built, as it simply ends up as a
> native shared library. We build plugins with NDK command line
> tools.Apparently they can also be built with gradle but I hate having
> to learn a new build system every time somebody invents one.
>
> The user interface and framework of the app is written in Java.
>
> Csound itself is a native shared library that the app loads using JNI
> (Java Native Interface).
>
> Csound itself uses regular C system calls to load the plugin shared libraries.
>
> Hope this is clearer,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Fri, Mar 25, 2016 at 9:36 PM, Peter Burgess
>  wrote:
>> Sorry, I still don't entirely follow... Are you saying that Csound
>> runs in java, but the pluggin won't need to be built with gradle
>> because it is interfacing with java through Csound? Or just that NDK
>> stuff doesn't need gradle in general?
>>
>> On Fri, Mar 25, 2016 at 6:22 PM, Michael Gogins
>>  wrote:
>>> Csound runs as a native library in a Java library in a Java app.
>>>
>>> Regards,
>>> Mike
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Fri, Mar 25, 2016 at 9:15 PM, Peter Burgess
>>>  wrote:
>>>> Ah, is that because Csound is running the pluggin, so it doesn't
>>>> directly need java compatibility?
>>>>
>>>> On Fri, Mar 25, 2016 at 6:13 PM, Steven Yi  wrote:
>>>>> Sorry, to correct one thing I mentioned, standard Android projects
>>>>> (i.e., Java) are built using Gradle. I haven't followed if gradle
>>>>> support for NDK is now standard or if still experimental.  For
>>>>> building NDK stuff, particularly Csound opcode plugins, you need only
>>>>> use the NDK's build tools to build from a ccommandline or from and
>>>>> IDE.
>>>>>
>>>>> On Fri, Mar 25, 2016 at 2:07 PM, Peter Burgess
>>>>>  wrote:
>>>>>> Cool, that's probably good advice. maybe once I've used android studio
>>>>>> for a while and actually built some android bits and pieces, then I
>>>>>> can think about moving it to codeblocks
>>>>>>
>>>>>> On Fri, Mar 25, 2016 at 5:44 PM, Michael Gogins
>>>>>>  wrote:
>>>>>>> In general I would advise using the tools most other people on the
>>>>>>> platform use. Particularly if the platform is complex as Android is.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Mike
>>>>>>>
>>>>>>> -----------------------------------------------------
>>>>>>> Michael Gogins
>>>>>>> Irreducible Productions
>>>>>>> http://michaelgogins.tumblr.com
>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Mar 25, 2016 at 8:34 PM, Steven Yi  wrote:
>>>>>>>> I have not done any Android development outside of the standard
>>>>>>>> environments (previously, Eclipse, and currently, Android Studio).
>>>>>>>> Android Studio uses the Gradle build system now, which can be run on
>>>>>>>> its own outside of the IDE.  Other than that, I don't have much
>>>>>>>> experience with CodeBlocks so cannot offer much other advice.  Good
>>>>>>>> luck on getting it all working!
>>>>>>>>
>>>>>>>> steven
>>>>>>>>
>>>>>>>> On Fri, Mar 25, 2016 at 1:14 PM, Peter Burgess
>>>>>>>>  wrote:
>>>>>>>>> Ah right, I can set the full path in the options rather than just the
>>>>>>>>> filename. That's alright, that gives me some options.
>>>>>>>>>
>>>>>>>>> I'd quite forgotten I'll have to build the pluggins for android, but I
>>>>>>>>> need to get up and running on the android development soon anyway,
>>>>>>>>> could be a good test run! I've got the NDK already, but haven't set up
>>>>>>>>> an android compiler yet.
>>>>>>>>>
>>>>>>>>> To divert somewhat from my question, have you ever built for android
>>>>>>>>> outside of android studio before? I'm hoping to set up all my cross
>>>>>>>>> build environments in a single IDE, which is currently CodeBlocks.
>>>>>>>>> Windows was easy enough to set up, but I spent ages reading about it
>>>>>>>>> for android, and watching videos, and it sounded like the normal
>>>>>>>>> practice was to just use android studio.
>>>>>>>>>
>>>>>>>>> Cheers very much!
>>>>>>>>>
>>>>>>>>> Pete
>>>>>>>>>
>>>>>>>>> On Fri, Mar 25, 2016 at 4:59 PM, Steven Yi  wrote:
>>>>>>>>>> Yes, you will need to compile it as a plugin for the appropriate CPU
>>>>>>>>>> architecture (mostly likely just armeabi-v7a will do just fine to
>>>>>>>>>> start). You will also need to have the opcode library loaded by
>>>>>>>>>> Csound.  I think you can use a --opcode-lib=/path/to/lib flag in
>>>>>>>>>> CsOptions to do this (note: I have not tested this approach).  Michael
>>>>>>>>>> or others could probably comment if a folder is designated as
>>>>>>>>>> OPCODE6DIR by the application, or if that can be set by the user.
>>>>>>>>>>
>>>>>>>>>> To build the plugin, you will need the Android Native Development Kit
>>>>>>>>>> (NDK).  After that, it's probably easiest to download a copy of the
>>>>>>>>>> Csound sources, go into the android/pluginlibs folder, and then copy
>>>>>>>>>> one of the existing plugin project folders and adjust for your own
>>>>>>>>>> plugin opcode.
>>>>>>>>>>
>>>>>>>>>> On Fri, Mar 25, 2016 at 12:48 PM, Peter Burgess
>>>>>>>>>>  wrote:
>>>>>>>>>>> Is there a way of using my plugin opcodes on android device while
>>>>>>>>>>> using the old Csound android app?
>>>>>>>>>>>
>>>>>>>>>>> Pete
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> http://algorythmradio.com
>>>>>>>>>>> https://soundcloud.com/algorythmradio
>>>>>>>>>>>
>>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> http://algorythmradio.com
>>>>>>>>> https://soundcloud.com/algorythmradio
>>>>>>>>>
>>>>>>>>> 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
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> http://algorythmradio.com
>>>>>> https://soundcloud.com/algorythmradio
>>>>>>
>>>>>> 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
>>>>
>>>>
>>>>
>>>> --
>>>> http://algorythmradio.com
>>>> https://soundcloud.com/algorythmradio
>>>>
>>>> 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
>>
>>
>>
>> --
>> http://algorythmradio.com
>> https://soundcloud.com/algorythmradio
>>
>> 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