Re: [Nxtcommand-developers] Supporting Multiple Platforms - Using the SJPP Simple Java PreProcessor

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

I have some speech stuff to check in. This brings up another question - the 
icommand.vision and icommand.speech packages rely on external JAR files. For 
speech it needs some sphinx4 jar files (2) and the Java Speech API (1 more 
jar).

Do you think we should branch icommand.vision and icommand.speech into a 
seperate project in subversion? We should we just add these jars to the 
build-icommand/lib directory, same as rxtx and jmf.

- Brian

----- Original Message ----- 
From: "Peter Joosten" <ptg...@ch...>
To: "Brian Bagnall" <bba...@mt...>; "iCommand Developers" 
<nxt...@li...>
Sent: Sunday, December 17, 2006 4:40 PM
Subject: Supporting Multiple Platforms - Using the SJPP Simple Java 
PreProcessor


> In order to support multiple platforms I will make some changes to
> subversion.
>
> The first change I will make is to move the java sources of the icommand
> project
> to a new icommand-sources project.
>
> Actions:
> 1. I would ask you to finish your current work on the icommand project.
> 2. After this I will make the change. during this short period no commit 
> is
> allowed
> 3. I will send an e-mail when I have finished action 2.
>
> After the change you must DELETE the icommand project in your workspace, 
> and
> check out the project icommand and icommand-sources from subversion.
>
> You have to link the sources of the icommand-sources project to the 
> icommand
> project. Than you can start editing the icommand sources from within 
> the -->
> icommand <-- project, like before.
>
> I will  send instructions how to link the sources of the icommand-sources
> project to the icommand project, for both eclipse and netbeans.
>
> Please let me know if you still have some work on icommand that you want 
> to
> finish.
> I like to start with action 2 at wednesday. But if every one has commited
> his
> changes, I will start with action 2 now.
>
>
> Peter.
>