BuildingTheFactJniLibrary - Revision history

Tredmond: /* The C++ compile */

2009-12-16T22:07:17Z

‎The C++ compile

2009-05-06T13:55:51Z

2008-04-27T14:38:13Z

‎The Java Compile

2008-04-27T14:15:35Z

‎The Java Compile

2008-04-25T22:32:50Z

‎The Java Compile

2008-04-25T22:31:48Z

‎The Java Compile

2008-04-25T22:20:42Z

‎Handling Problems with FaCT++ not Finding Libraries

2008-04-25T22:04:33Z

‎Linking the JNI Library in os x.

2008-04-25T21:04:11Z

2008-04-18T16:08:05Z

‎Handling Problems with FaCT++ not Finding Libraries

@@ Line 13: / Line 13: @@
 == The C++ compile ==
-Note that if you do this on a Mac then Xcode 2.2 or greater is recommended in order to get a universal binary.
+On Ubuntu I used
+<pre>
-First checkout FaCT++ with the command line call:
+   export CPLUS_INCLUDE_PATH=${JAVA_HOME}/include:${JAVA_HOME}/include/linux
- svn checkout http://factplusplus.googlecode.com/svn/trunk/ factplusplus.
+   sudo apt-get install libxerces-c2-dev
-We now need to edit the Makefile.include to use the options associated with the correct version of gcc.  First we find the version of gcc with the command line
+</pre>
 == The Java Compile ==

← Older revision		Revision as of 13:55, May 6, 2009
Line 1:		Line 1:
	= Handling Problems with FaCT++ not Finding Libraries =		= Handling Problems with FaCT++ not Finding Libraries =
		+
		+
		+	== Building The FaCT++ jni library ==
		+
		+	Because FaCT++ is written in C++, it is a little harder to get it to compile properly across platforms. In particular, a user may see errors such as
		+	Link (dyld) error:
		+	Symbol not found: _clock$UNIX2003
		+	or a java.lang.UnsatisfiedLinkError with a message similar to the following
		+	libFaCTPlusPlusJNI.so: /usr/lib/libstdc++.so.6: version `GL IBCXX_3.4.9' not found (required by libFaCTPlusPlusJNI.so)
		+	This happens because the version of FaCT++ that was compiled into the Protege 4 owl editor is not compatible with the libraries in the users operating system. If this happens on a windows or an OS X machine then send a message to the [mailto:p4-feedback@lists.stanford.edu P4 mailing list] because the developers probably should fix this situation. (If you are not subscribed to this list look at [https://mailman.stanford.edu/mailman/listinfo/p4-feedback this web page].) However on a linux or other operating system this is much more difficult because there are too many different variants. In this case you will probably have to build you own version of FaCT++. Hence we added the following page to make the work a little easier.
		+

	== The C++ compile ==		== The C++ compile ==

@@ Line 31: / Line 31: @@
 == The Java Compile ==
-There is no build file for the java file so we go back to command line style.  Set the owlapi variable to the location of the owlapi jar file, e.g.
+There is no build file for the java file so we go back to basic java commands.  Set the owlapi variable to the location of the owlapi jar file, e.g.
   owlapi=~/dev/workspaces/protege4/owleditor/plugins/org.semanticweb.owl.owlapi/lib/owlapi-bin.jar
 Then the command line

@@ Line 31: / Line 31: @@
 == The Java Compile ==
-There is no build file for the java file so we go back to caveman style.  Set the owlapi variable to the location of the owlapi jar file, e.g.
+There is no build file for the java file so we go back to command line style.  Set the owlapi variable to the location of the owlapi jar file, e.g.
   owlapi=~/dev/workspaces/protege4/owleditor/plugins/org.semanticweb.owl.owlapi/lib/owlapi-bin.jar
 Then the command line

@@ Line 31: / Line 31: @@
 == The Java Compile ==
-Set the owlapi variable to the location of the owlapi jar file, e.g.
+There is no build file for the java file so we go back to caveman style.  Set the owlapi variable to the location of the owlapi jar file, e.g.
   owlapi=~/dev/workspaces/protege4/owleditor/plugins/org.semanticweb.owl.owlapi/lib/owlapi-bin.jar
 Then the command line

@@ Line 35: / Line 35: @@
 Then the command line
   javac -cp $owlapi -d classes -g `find FaCT++.Java -name "*.java"`
-almost works.
+works - though there were some compile errors that were easily fixed and I agreed with the compiler.  Then
 == Troubleshooting ==
 [http://xerces.apache.org/xerces-c The xerces C Library Home Page]

@@ Line 1: / Line 1: @@
 = Handling Problems with FaCT++ not Finding Libraries =
 '''In Progress...'''
@@ Line 18: / Line 19: @@
 Now much of the building progresses fine.  But it seems that building the jnilibrary does not work on most machines.  So here are some machine specific options for how to finish the build.
-== Linking the JNI Library in os x. ==
+=== Linking the JNI Library in os x. ===
 The commands
@@ Line 27: / Line 28: @@
 compile but don't work at runtime.
 == Troubleshooting ==
 [http://xerces.apache.org/xerces-c The xerces C Library Home Page]

@@ Line 16: / Line 16: @@
 So I modified the Makefile.include so that the GENERAL_DEFINES were
   GENERAL_DEFINES = $(GCC_OPT_OPT) $(GCC_34_OPT) $(ALL_DEF)
 == Troubleshooting ==
 [http://xerces.apache.org/xerces-c The xerces C Library Home Page]