Re: [Nxtcommand-developers] CLDC

[Brian B. <bba...@mt...>]

With this setup will we still be able to make changes to iCommand code and 
use it "realtime" in Eclipse? Or will we have to manually run an ANT build 
after every change to the iCommand source?

----- Original Message ----- 
From: "Peter Joosten" <ptg...@ch...>
To: "Brian Bagnall" <bba...@mt...>; "iCommand Developers" 
<nxt...@li...>
Sent: Friday, December 15, 2006 10:23 AM
Subject: RE: [Nxtcommand-developers] CLDC


> Supporting multiple runtime environments / platforms
> with different development kits, requieres different
> project settings. These can not coexist in 1 project.
> (In eclipse terms: there can only be 1 .project, 1
> .classpath, and 1 .settings). Therefore each platform
> should have its own project(s). I suggest the next setup:
>
> project icommand-sources : contains only the java sources
> (with prepocessor commands) these sources are linked into
> the other projects as an external source folder.
>
> project icommand : the sources of icommand-sources are linked
> as an external source folder in this project and prepocessed &
> compiled according the settings of the icommand project.
>
> project icommand-cldc : the sources of icommand-sources are linked
> as an external source folder in this project and prepocessed &
> compiled according the settings of the icommand-cldc project.
>
> The name of the project "icommand-cldc" is just an example.
>
> - In this ways every project only has 1 set of files for the project
> settings.
> - In this way we can use netbeans (if requied) for one project and
>  eclipse for another.
> - we have 1 source tree in the project icommand-sources
>
> - This will break the ant build system, but that can be fixed.
>
> Agree/Disagree ? Questions ? If I get a GO a start implementing it, and
> will integrate icommand-0.5_CLDCpre2.zip into icommand-sources.
>
> Stefano, is icommand-0.5_CLDCpre2.zip the latest version ?
>
> Peter.
>