Actually it was an issue with ";" vs ":" seperator in classpath
for windows vs linux. So instead of org.ibex.nestedvm.Compiler
interpreting the command options, 'java' itself was interpreting
then options and spooked me to think why 'java' is being called
incorrectly.

Ya, I too realized cygwin compile getting difficult. The issue
I faced with linux builds was that some of the 'curl' downloads
mysteriously failed. (cygwin based builds or running the failing
curl invocation in linux shell worked!) Then I tried replacing
the failing curl invocations in Makefile's with 'wget'
but unfortunately some of the makefile's themselves getting
generated wiping out my tweaks. So I finally replaced 'curl' with
a shell script that called 'wget' for failed 'curl's' and curl
for others as it is. Then linux build went quite a while and built
the jdbc nested jar. That was enough for me. It loads and works.
Build still failed in some test case building etc but I did not
explore further.

Thanks a lot for all the help and advice. Really appreciate it.

On May 7, 6:33 pm, "David Crawshaw" <[EMAIL PROTECTED]> wrote:
> 2008/5/8 jackie <[EMAIL PROTECTED]> wrote:
> >  However my attempt was to build the nested jdbc jar.
>
> I only build the nested version on a linux machine, it's probably not
> going to build anywhere else.
>
> >  So I have to use Makefile.nested, correct?
>
> Yes, run: make -f Makefile.nested
>
> >  java -cp nestedvm-2007-06-30/build;nestedvm-2007-06-30/upstream/build/
> >  classgen/build \
> >             org.ibex.nestedvm.Compiler \
> >             -outformat class -d build -o unixRuntime \
> >             org.sqlite.SQLite build/SQLite.mips
>
> >  java command does not have some of these options.
>
> Those are options to the NestedVM compiler,
> org.ibex.nestedvm.Compiler. I would need the actual error message to
> help, but I recommend building the nested driver on a linux machine.
>
> d
--~--~---------~--~----~------------~-------~--~----~
Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en
To unsubscribe, send email to [EMAIL PROTECTED]
-~----------~----~----~----~------~----~------~--~---

Reply via email to