Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [sequoyah-dev] starting discussions on Android Native developmentsupport
I am worried that concentrating on an Android specific problem may hurt contributions for other technologies, and technology providers. I believe, it is important for Sequoyah project to remain at an equal distance from all the technologies and their providers in order to provide a home for all Eclipse mobile developers.
--
Gorkem


On Tue, Apr 13, 2010 at 5:47 PM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:
My dream is that Google opens their hearts and contributes all of the ADT to Sequoyah so we can work on it in the open. But there are many hurdles that prevent that.
My goal is to promote CDT for Android app native development and it's much easier for me to contribute it to Eclipse.


On Tue, Apr 13, 2010 at 8:01 AM, Ruth Fabiana Soliani <ruth.soliani@xxxxxxxxxxxxxxx> wrote:

Hi Gorkem,

 

Ideally there should be no direct dependency.

If the Android NDK is installed, Sequoyah should support its use; if not, perhaps some specific features will be disabled or it may be transparent to the user. The solution is not closed yet, so I guess there isn’t a complete answer to your question currently.

 

Best regards,

Ruth

 

From: sequoyah-dev-bounces@xxxxxxxxxxx [mailto:sequoyah-dev-bounces@xxxxxxxxxxx] On Behalf Of Gorkem Ercan
Sent: Tuesday, April 13, 2010 5:10 AM
To: Sequoyah Developers
Subject: Re: [sequoyah-dev] starting discussions on Android Native developmentsupport

 

Does that mean that Sequoyah project intends to distribute, or have dependency to Android tools?
--
Gorkem

On Mon, Apr 12, 2010 at 11:23 PM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:

I can give a quick update on what I'm doing.

 

Essentially, I'm doing two things. First is a Project conversion wizard that adds CDT capabilities to Android projects. This includes generation of a Makefile and build settings and setting the appropriate source and output folders to ensure CDT ignores the non native stuff. The second part is a toolchain definition for the CDT's build system so that we can configure paths appropriately for build time and to properly configure CDT's indexer to find the header files in the NDK.

 

That is all I plan on working on. Once gdbserver is supported properly for NDK apps, you'll likely want to hook that up to CDT's debug system. You may also want to do some further code generation to be able to create skeletal native code for Java native methods. I can help advise on that.

 

Let me know if you have any questions.

Doug.

On Mon, Apr 12, 2010 at 3:42 PM, Ruth Fabiana Soliani <ruth.soliani@xxxxxxxxxxxxxxx> wrote:

Hi Everybody,

 

On our next Open Call (Apr 19th) we intend to discuss what Doug has already done regarding Android NDK x CDT integration, as well as plan our next steps about Android Native support.

If you are interested in this subject, join our discussion!

 

There should be other topics in the agenda (which will be available on the project page timely). If necessary, we may schedule a separate meeting specific for this topic, but let’s try to fit it into our regular call first.

 

Best regards,

Ruth Soliani

 

_______________________________________________
sequoyah-dev mailing list
sequoyah-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev

 


_______________________________________________
sequoyah-dev mailing list
sequoyah-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev

 


_______________________________________________
sequoyah-dev mailing list
sequoyah-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev



_______________________________________________
sequoyah-dev mailing list
sequoyah-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev


Back to the top