Hi Michael,

I'd rather we not use static libs. It seems to me that the dynamic
libs is now working after the change I committed yesterday, at least
in terms of loading (the crash issue needs resolution).

The problems I see with the static lib approach:

1. Adds a lot of #ifdef's in the core codebase
2. Makes all the extra libs now mandatory for building Csound:  this
is a big no-no for me here, as this makes the library much bigger for
everyone, even if they don't need the opcodes.  Also, this makes it
much harder to compile for those building from scratch.
3. Adding new opcode libraries becomes difficult, as it requires
numerous edits to get the static initializers added to the core's
loading.
4. This limits users who might have their own opcode libs from getting
them loaded.

I think with the dynamic libs, we're pretty close.  They load now,
projects that use the opcodes from the libs work, just need to resolve
the crashing issue on 2nd run and that should do it.

Could you do a build from the latest from the master branch and also
post that for general testing?  I'd do one but all of the APK's so far
have been signed with your certificate so it'd be better if you could
do it.

Thanks!
steven

On Sat, Jun 29, 2013 at 4:19 PM, Michael Gogins
 wrote:
> I have pushed a new branch of Csound 6 for Android to SourceForget git. The
> branch is named "static_plugins".
>
> In this branch, all native code for Csound 6, including the former opcode
> shared libraries for the Lua opcodes, the FluidSynth "fluid" opcodes, and
> the signal flow graph opcodes, is linked in one self-contained shared
> library. All the code in the "pluginlibs" projects is compiled to static
> libraries. These are "included" in the CsoundAndroid project, which will
> enforce build dependencies.
>
> This code runs on my Samsung Galaxy S4 smartphone. I have succesfully tested
> the signal flow graph opcodes and the Lua opcodes.
>
> I have uploaded the app to a new directory in the SourceForge files tree:
>
> http://sourceforge.net/projects/csound/files/csound6/Csound6.0rc4/static_plugins/Csound6.apk/download
>
> I would very much appreciate it if some of the people who have had trouble
> running the older app would try this one and let me know if it runs.
>
> It may be a good idea to merge this code back into the master branch, but I
> would like to wait until we are sure this code runs on other devices, and
> until we have tried to get the shared library approach to work.
>
> Regards,
> Mike
>
> ===========================
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Yes I will do a new build.

I saw some things that looked wrong to me on the master branch. The gnustl lib should not be linked statically in more than one module in the same process. When I built and ran it this morning it froze with a black screen. But this may be a load order difference on devices.

But I will try it again with a completely fresh clone and rebuild.

But you also should should try running the static app.

Best, Mike

That seems to point to issues with whatever version of GIT you have
there.  The command that gets called from that script is:

git clone  http://bitbucket.org/kunstmusik/libsndfile-android.git
git clone  http://bitbucket.org/kunstmusik/fluidsynth-android.git

Do those commands work manually from the command prompt/terminal you are using?

On Sat, Jun 29, 2013 at 6:54 PM, Michael Gogins
 wrote:
> I'm getting this again:
>
> $ ./downloadDependencies.sh
> Using NDK_MODULE_PATH: /c/Users/new/csound-csound6-git/android/pluginlibs\n
> Cloning libsndfile-android...
> Cloning into 'libsndfile-android'...
> error: Protocol https not supported or disabled in libcurl while accessing
> http://bitbucket.org/kunstmusik/libsndfile-android.git/in
> fo/refs?service=git-upload-pack
> fatal: HTTP request failed
> Cloning fluidsynth-android...
> Cloning into 'fluidsynth-android'...
> error: Protocol https not supported or disabled in libcurl while accessing
> http://bitbucket.org/kunstmusik/fluidsynth-android.git/in
> fo/refs?service=git-upload-pack
>
> Best,
> Mike
>
>
> ===========================
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sat, Jun 29, 2013 at 6:32 PM, Michael Gogins 
> wrote:
>>
>> Yes I will do a new build.
>>
>> I saw some things that looked wrong to me on the master branch. The gnustl
>> lib should not be linked statically in more than one module in the same
>> process. When I built and ran it this morning it froze with a black screen.
>> But this may be a load order difference on devices.
>>
>> But I will try it again with a completely fresh clone and rebuild.
>>
>> But you also should should try running the static app.
>>
>> Best, Mike
>>
>> On Jun 29, 2013 5:32 PM, "Steven Yi"  wrote:
>>>
>>> Hi Michael,
>>>
>>> I'd rather we not use static libs. It seems to me that the dynamic
>>> libs is now working after the change I committed yesterday, at least
>>> in terms of loading (the crash issue needs resolution).
>>>
>>> The problems I see with the static lib approach:
>>>
>>> 1. Adds a lot of #ifdef's in the core codebase
>>> 2. Makes all the extra libs now mandatory for building Csound:  this
>>> is a big no-no for me here, as this makes the library much bigger for
>>> everyone, even if they don't need the opcodes.  Also, this makes it
>>> much harder to compile for those building from scratch.
>>> 3. Adding new opcode libraries becomes difficult, as it requires
>>> numerous edits to get the static initializers added to the core's
>>> loading.
>>> 4. This limits users who might have their own opcode libs from getting
>>> them loaded.
>>>
>>> I think with the dynamic libs, we're pretty close.  They load now,
>>> projects that use the opcodes from the libs work, just need to resolve
>>> the crashing issue on 2nd run and that should do it.
>>>
>>> Could you do a build from the latest from the master branch and also
>>> post that for general testing?  I'd do one but all of the APK's so far
>>> have been signed with your certificate so it'd be better if you could
>>> do it.
>>>
>>> Thanks!
>>> steven
>>>
>>> On Sat, Jun 29, 2013 at 4:19 PM, Michael Gogins
>>>  wrote:
>>> > I have pushed a new branch of Csound 6 for Android to SourceForget git.
>>> > The
>>> > branch is named "static_plugins".
>>> >
>>> > In this branch, all native code for Csound 6, including the former
>>> > opcode
>>> > shared libraries for the Lua opcodes, the FluidSynth "fluid" opcodes,
>>> > and
>>> > the signal flow graph opcodes, is linked in one self-contained shared
>>> > library. All the code in the "pluginlibs" projects is compiled to
>>> > static
>>> > libraries. These are "included" in the CsoundAndroid project, which
>>> > will
>>> > enforce build dependencies.
>>> >
>>> > This code runs on my Samsung Galaxy S4 smartphone. I have succesfully
>>> > tested
>>> > the signal flow graph opcodes and the Lua opcodes.
>>> >
>>> > I have uploaded the app to a new directory in the SourceForge files
>>> > tree:
>>> >
>>> >
>>> > http://sourceforge.net/projects/csound/files/csound6/Csound6.0rc4/static_plugins/Csound6.apk/download
>>> >
>>> > I would very much appreciate it if some of the people who have had
>>> > trouble
>>> > running the older app would try this one and let me know if it runs.
>>> >
>>> > It may be a good idea to merge this code back into the master branch,
>>> > but I
>>> > would like to wait until we are sure this code runs on other devices,
>>> > and
>>> > until we have tried to get the shared library approach to work.
>>> >
>>> > Regards,
>>> > Mike
>>> >
>>> > ===========================
>>> > Michael Gogins
>>> > Irreducible Productions
>>> > http://michaelgogins.tumblr.com
>>> > Michael dot Gogins at gmail dot com
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>

Seems then the script is alright and that libcurl on your side doesn't
have https support.  I googled this:

https://code.google.com/p/msysgit/issues/detail?id=280

It seems from that link that msysgit should already be fixed.  Perhaps
another version of libcurl is getting picked up that doesn't have
https support?

On Sat, Jun 29, 2013 at 7:24 PM, Michael Gogins
 wrote:
> $ git version
> git version 1.8.1.msysgit.1
>
> $ git clone http://bitbucket.org/kunstmusik/fluidsynth-android.git
> Cloning into 'fluidsynth-android'...
> error: Protocol https not supported or disabled in libcurl while accessing
> http://bitbucket.org/kunstmusik/fluidsynth-android.git/in
> fo/refs?service=git-upload-pack
> fatal: HTTP request failed
>
> $ git clone http://bitbucket.org/kunstmusik/libsndfile-android.git
> Cloning into 'libsndfile-android'...
> error: Protocol https not supported or disabled in libcurl while accessing
> http://bitbucket.org/kunstmusik/libsndfile-android.git/in
> fo/refs?service=git-upload-pack
> fatal: HTTP request failed
>
>
>
> ===========================
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sat, Jun 29, 2013 at 6:54 PM, Michael Gogins 
> wrote:
>>
>> I'm getting this again:
>>
>> $ ./downloadDependencies.sh
>> Using NDK_MODULE_PATH:
>> /c/Users/new/csound-csound6-git/android/pluginlibs\n
>> Cloning libsndfile-android...
>> Cloning into 'libsndfile-android'...
>> error: Protocol https not supported or disabled in libcurl while accessing
>> http://bitbucket.org/kunstmusik/libsndfile-android.git/in
>> fo/refs?service=git-upload-pack
>> fatal: HTTP request failed
>> Cloning fluidsynth-android...
>> Cloning into 'fluidsynth-android'...
>> error: Protocol https not supported or disabled in libcurl while accessing
>> http://bitbucket.org/kunstmusik/fluidsynth-android.git/in
>> fo/refs?service=git-upload-pack
>>
>> Best,
>> Mike
>>
>>
>> ===========================
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sat, Jun 29, 2013 at 6:32 PM, Michael Gogins 
>> wrote:
>>>
>>> Yes I will do a new build.
>>>
>>> I saw some things that looked wrong to me on the master branch. The
>>> gnustl lib should not be linked statically in more than one module in the
>>> same process. When I built and ran it this morning it froze with a black
>>> screen. But this may be a load order difference on devices.
>>>
>>> But I will try it again with a completely fresh clone and rebuild.
>>>
>>> But you also should should try running the static app.
>>>
>>> Best, Mike
>>>
>>> On Jun 29, 2013 5:32 PM, "Steven Yi"  wrote:
>>>>
>>>> Hi Michael,
>>>>
>>>> I'd rather we not use static libs. It seems to me that the dynamic
>>>> libs is now working after the change I committed yesterday, at least
>>>> in terms of loading (the crash issue needs resolution).
>>>>
>>>> The problems I see with the static lib approach:
>>>>
>>>> 1. Adds a lot of #ifdef's in the core codebase
>>>> 2. Makes all the extra libs now mandatory for building Csound:  this
>>>> is a big no-no for me here, as this makes the library much bigger for
>>>> everyone, even if they don't need the opcodes.  Also, this makes it
>>>> much harder to compile for those building from scratch.
>>>> 3. Adding new opcode libraries becomes difficult, as it requires
>>>> numerous edits to get the static initializers added to the core's
>>>> loading.
>>>> 4. This limits users who might have their own opcode libs from getting
>>>> them loaded.
>>>>
>>>> I think with the dynamic libs, we're pretty close.  They load now,
>>>> projects that use the opcodes from the libs work, just need to resolve
>>>> the crashing issue on 2nd run and that should do it.
>>>>
>>>> Could you do a build from the latest from the master branch and also
>>>> post that for general testing?  I'd do one but all of the APK's so far
>>>> have been signed with your certificate so it'd be better if you could
>>>> do it.
>>>>
>>>> Thanks!
>>>> steven
>>>>
>>>> On Sat, Jun 29, 2013 at 4:19 PM, Michael Gogins
>>>>  wrote:
>>>> > I have pushed a new branch of Csound 6 for Android to SourceForget
>>>> > git. The
>>>> > branch is named "static_plugins".
>>>> >
>>>> > In this branch, all native code for Csound 6, including the former
>>>> > opcode
>>>> > shared libraries for the Lua opcodes, the FluidSynth "fluid" opcodes,
>>>> > and
>>>> > the signal flow graph opcodes, is linked in one self-contained shared
>>>> > library. All the code in the "pluginlibs" projects is compiled to
>>>> > static
>>>> > libraries. These are "included" in the CsoundAndroid project, which
>>>> > will
>>>> > enforce build dependencies.
>>>> >
>>>> > This code runs on my Samsung Galaxy S4 smartphone. I have succesfully
>>>> > tested
>>>> > the signal flow graph opcodes and the Lua opcodes.
>>>> >
>>>> > I have uploaded the app to a new directory in the SourceForge files
>>>> > tree:
>>>> >
>>>> >
>>>> > http://sourceforge.net/projects/csound/files/csound6/Csound6.0rc4/static_plugins/Csound6.apk/download
>>>> >
>>>> > I would very much appreciate it if some of the people who have had
>>>> > trouble
>>>> > running the older app would try this one and let me know if it runs.
>>>> >
>>>> > It may be a good idea to merge this code back into the master branch,
>>>> > but I
>>>> > would like to wait until we are sure this code runs on other devices,
>>>> > and
>>>> > until we have tried to get the shared library approach to work.
>>>> >
>>>> > Regards,
>>>> > Mike
>>>> >
>>>> > ===========================
>>>> > Michael Gogins
>>>> > Irreducible Productions
>>>> > http://michaelgogins.tumblr.com
>>>> > Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>
>

Yes I will do a new build.

I saw some things that looked wrong to me on the master branch. The gnustl lib should not be linked statically in more than one module in the same process. When I built and ran it this morning it froze with a black screen. But this may be a load order difference on devices.

But I will try it again with a completely fresh clone and rebuild.

But you also should should try running the static app.

Best, Mike

Thanks for the feedback,
Mike