Re: build longwell on windows

From: Stefano Mazzocchi <stefanom_at_mit.edu>
Date: Fri, 15 Jul 2005 11:28:01 -0400

Jon Crump wrote:
> Dear all,
>
> So far my use of Longwell has been confined to a linux server and a Mac
> OS X laptop. Since we hope to encourage the use of Longwell here among
> faculty and other researchers, I thought I'd better make sure I could
> get it up and running on Windows platforms as well. This turned out
> (naturally) to engender problems. I don't know if this is because
> Windows is stupid or I am. After I got the right Java SDK installed, the
> build.bat reported a log of actions and errors ending in this:
>
> <<
> BUILD FAILED
> C:\Documents and Settings\jjcrump\My
> Documents\SimileTesting\longwell-1.1\tools\
> targets\compile-build.xml:73: Compile failed; see the compiler error
> output for
> details.
>
> Total time: 2 seconds
>
>>>
>
> I've attached the compiler output as an attachment (is that kosher?). If
> anyone can give me some clues I'd be grateful. I know little about windows.
>
> Thanks,
> Jon
> __________
> J.J. Crump
> Dept. of History 353560
> University of Washington
> Seattle, WA. 98195
>
>
> ------------------------------------------------------------------------
>
> Buildfile: build.xml
>
> init:
>
> start:
> ======================================================================
> SIMILE Longwell 1.1 [2003-2005]
> ======================================================================
> Building with Apache Ant version 1.6.1 compiled on February 12 2004
> ----------------------------------------------------------------------
> Using build file C:\Documents and Settings\jjcrump\My Documents\SimileTesting\longwell-1.1\build.xml
> ----------------------------------------------------------------------
> Running on Java version 1.4
> ----------------------------------------------------------------------
> Compiler options:
> - debug ......... [on]
> - optimize ...... [on]
> - deprecation ... [on]
> ======================================================================
>
> Building Longwell using ${bundle} data bundle
>
>
>
> prepare:
>
> prepare-external-check:
>
> prepare-vocabularies:
>
> compile-vocabularies:
> Ontologies are up-to-date
>
> compile:
> Compiling 50 source files to C:\Documents and Settings\jjcrump\My Documents\SimileTesting\longwell-1.1\build\classes
> C:\Documents and Settings\jjcrump\My Documents\SimileTesting\longwell-1.1\src\java\edu\mit\simile\inferencing\SimileReasoner.java:19: package edu.mit.simile.vocabularies does not exist
> import edu.mit.simile.vocabularies.Artstor;
> ^
> C:\Documents and Settings\jjcrump\My Documents\SimileTesting\longwell-1.1\src\java\edu\mit\simile\inferencing\SimileReasoner.java:20: package edu.mit.simile.vocabularies does not exist
> import edu.mit.simile.vocabularies.Display;
> ^
> C:\Documents and Settings\jjcrump\My Documents\SimileTesting\longwell-1.1\src\java\edu\mit\simile\inferencing\SimileReasoner.java:21: package edu.mit.simile.vocabularies does not exist
> import edu.mit.simile.vocabularies.SkosCore;
> ^
> C:\Documents and Settings\jjcrump\My Documents\SimileTesting\longwell-1.1\src\java\edu\mit\simile\inferencing\SimileReasoner.java:22: package edu.mit.simile.vocabularies does not exist
> import edu.mit.simile.vocabularies.VRACore;
> ^
> C:\Documents and Settings\jjcrump\My Documents\SimileTesting\longwell-1.1\src\java\edu\mit\simile\longwell\BrowserConfig.java:23: package edu.mit.simile.vocabularies does not exist
> import edu.mit.simile.vocabularies.Display;
> ^
> C:\Documents and Settings\jjcrump\My Documents\SimileTesting\longwell-1.1\src\java\edu\mit\simile\longwell\values\ResourceImage.java:7: package edu.mit.simile.vocabularies does not exist
> import edu.mit.simile.vocabularies.Display;
> ^
> C:\Documents and Settings\jjcrump\My Documents\SimileTesting\longwell-1.1\src\java\edu\mit\simile\longwell\model\FacetModel.java:37: package edu.mit.simile.vocabularies does not exist
> import edu.mit.simile.vocabularies.Display;

Jon,

Try to change line 73 of the file "tools/targets/compile-build.xml" from

    classpath="${vocabularies.dest}">

to

    classpath="${vocabularies.bytecode}">


and tell me what happens.

[I think you find a bug/typo in our build files... what I don't
understand is why it works at all on the other platforms! weird]

-- 
Stefano Mazzocchi
Research Scientist                 Digital Libraries Research Group
Massachusetts Institute of Technology            location: E25-131C
77 Massachusetts Ave                   telephone: +1 (617) 253-1096
Cambridge, MA  02139-4307              email: stefanom at mit . edu
-------------------------------------------------------------------
Received on Fri Jul 15 2005 - 15:25:22 EDT

This archive was generated by hypermail 2.3.0 : Thu Aug 09 2012 - 16:39:18 EDT