0
@@ -21,6 +21,30 @@ using namespace boost::filesystem;
0
 
0
 using namespace std;
0
 
0
+#if defined(_WIN32)
0
+/* [dm] this being undefined without us adding it here means there is 
0
+        no tss cleanup on windows for boost lib?
0
+        we don't care for now esp on windows only
0
+
0
+		the boost source says:
0
+
0
+		  This function's sole purpose is to cause a link error in cases where
0
+		  automatic tss cleanup is not implemented by Boost.Threads as a
0
+		  reminder that user code is responsible for calling the necessary
0
+		  functions at the appropriate times (and for implementing an a
0
+		  tss_cleanup_implemented() function to eliminate the linker's
0
+		  missing symbol error).
0
+
0
+		  If Boost.Threads later implements automatic tss cleanup in cases
0
+		  where it currently doesn't (which is the plan), the duplicate
0
+		  symbol error will warn the user that their custom solution is no
0
+		  longer needed and can be removed. 
0
+*/
0
+extern "C" void tss_cleanup_implemented(void) {
0
+	cout << "tss_cleanup_implemented called" << endl;
0
+}
0
+#endif
0
+
0
 JavaJSImpl * JavaJS = 0;
0
 
0
 void myJNIClean( JNIEnv * env ){