Re: [CLucene-dev] Compiling v.2.3.3.4 with VC6

2011-10-28 Thread Veit Jahns
Hi Celto,

I'm sorry. I was distracted by other things from your e-mail.

2011/10/17 cel tix44 celti...@gmail.com:
 Veit
 A couple of minor problems in the latest update ---
 1) When generating code, CMAKE throws this error:
 CMake Error at src/core/CMakeLists.txt:194 (add_library):
   Cannot find source file:
     ./CLucene/util/workaround/vc6/operators.cpp
 This is because the WORKAROUND folder sits under CLUCENE, not under UTIL.
 To fix, open src/core/CMakeLists.txt and remove UTIL\ from line 178 and 179,
 so that they read:
 IF (${MSVC_VERSION} EQUAL 1200)
   SET(clucene_workaround_Files ./CLucene/workaround/vc6/operators.cpp)
   SET(HEADERS_workaround ./CLucene/workaround/vc6/operators.h)
 ENDIF ()

Done.

 2) SegmentInfos.cpp compiles with these errors:
 D:\cl_2334_git_master\src\core\CLucene/workaround/vc6/operators.h(12) :
 error C2653: 'std' : is not a class or namespace name
 D:\cl_2334_git_master\src\core\CLucene/workaround/vc6/operators.h(12) :
 error C2143: syntax error : missing ';' before ''
 ...etc.
 To fix, open operators.h and add #include iostream above std::ostream, so
 that the file reads:
 #include iostream
 std::ostream operator  (std::ostream os, __int64 i);
 With these corrections, CORE  SHARED compile okay.

Done.

 3) A question re: _lucene_workaround_vc6_DocumentsWriter_ in operators.h,
 please -- the file currently reads:
 #ifndef  _lucene_workaround_vc6_DocumentsWriter_
          implement the fix for vc6
 #endif
 In which situation would _lucene_workaround_vc6_DocumentsWriter_ need to be
 defined to get the fix for vc6 suppressed ?

This should be a guard macro, but forgot the #define. Thanks for
pointing these errors out. I hope everything works now with VC6.

Kind regards,

Veit

--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
CLucene-developers mailing list
CLucene-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clucene-developers


Re: [CLucene-dev] Compiling v.2.3.3.4 with VC6

2011-10-16 Thread cel tix44
Veit

A couple of minor problems in the latest update ---

1) When generating code, CMAKE throws this error:
CMake Error at src/core/CMakeLists.txt:194 (add_library):
  Cannot find source file:
./CLucene/util/workaround/vc6/operators.cpp

This is because the WORKAROUND folder sits under CLUCENE, not under UTIL.

To fix, open src/core/CMakeLists.txt and remove UTIL\ from line 178 and 179,
so that they read:

IF (${MSVC_VERSION} EQUAL 1200)
  SET(clucene_workaround_Files ./CLucene/workaround/vc6/operators.cpp)
  SET(HEADERS_workaround ./CLucene/workaround/vc6/operators.h)
ENDIF ()

2) SegmentInfos.cpp compiles with these errors:
D:\cl_2334_git_master\src\core\CLucene/workaround/vc6/operators.h(12) :
error C2653: 'std' : is not a class or namespace name
D:\cl_2334_git_master\src\core\CLucene/workaround/vc6/operators.h(12) :
error C2143: syntax error : missing ';' before ''
...etc.

To fix, open operators.h and add #include iostream above std::ostream, so
that the file reads:
#include iostream
std::ostream operator  (std::ostream os, __int64 i);

With these corrections, CORE  SHARED compile okay.

3) A question re: _lucene_workaround_vc6_DocumentsWriter_ in operators.h,
please -- the file currently reads:

#ifndef  _lucene_workaround_vc6_DocumentsWriter_
 implement the fix for vc6
#endif

In which situation would _lucene_workaround_vc6_DocumentsWriter_ need to be
defined to get the fix for vc6 suppressed ?

Regards
Celto

On Sat, Oct 15, 2011 at 6:56 AM, Veit Jahns nuncupa...@googlemail.comwrote:

 2011/10/10 Veit Jahns nuncupa...@googlemail.com:
  Microsoft suggests this:
  #ifdef _MSC_VER
  #if _MSC_VER == 1200
  std::ostream operator(std::ostream os, __int64 i ) // borrowed from
  http://support.microsoft.com/kb/168440
  {
  char buf[20];
  sprintf(buf,%I64d, i );
  os  buf;
  return os;
  }
  #endif
  #endif
  With either of the 2 fixes above, both CLUCENE_CORE and CLUCENE_SHARED
  compile okay.
 
  I will then integrate the later one.

 Added this workaround to th vc6-branch.

 Kind regards,

 Veit Jahns


 --
 All the data continuously generated in your IT infrastructure contains a
 definitive record of customers, application performance, security
 threats, fraudulent activity and more. Splunk takes this data and makes
 sense of it. Business sense. IT sense. Common sense.
 http://p.sf.net/sfu/splunk-d2d-oct
 ___
 CLucene-developers mailing list
 CLucene-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/clucene-developers

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct___
CLucene-developers mailing list
CLucene-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clucene-developers


Re: [CLucene-dev] Compiling v.2.3.3.4 with VC6

2011-10-14 Thread Veit Jahns
2011/10/10 Veit Jahns nuncupa...@googlemail.com:
 Microsoft suggests this:
 #ifdef _MSC_VER
 #if _MSC_VER == 1200
 std::ostream operator(std::ostream os, __int64 i ) // borrowed from
 http://support.microsoft.com/kb/168440
 {
     char buf[20];
     sprintf(buf,%I64d, i );
     os  buf;
     return os;
 }
 #endif
 #endif
 With either of the 2 fixes above, both CLUCENE_CORE and CLUCENE_SHARED
 compile okay.

 I will then integrate the later one.

Added this workaround to th vc6-branch.

Kind regards,

Veit Jahns

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
CLucene-developers mailing list
CLucene-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clucene-developers


Re: [CLucene-dev] Compiling v.2.3.3.4 with VC6

2011-09-19 Thread Veit Jahns
Hi Celto!

2011/9/19 cel tix44 celti...@gmail.com:
 Veit
 Thanks very much for your response.
 Attached is a list of compilation errors as is -- produced after getting
 the source code from GIT, config'ed with Cmake 2.8 (default settings, no
 boost, no zlib) and built with vc6 -- essentially, for you to estimate if
 it's worth the time  effort at all.

I think so. Actually, some of them seem to me to be errors in the
code. E.g., the void function returning a value errors. I wonder,
why these cause no errors with newer versions of Visual C++.

 If yes, I can start by fixing all simple cases (like C2248: cannot access
 private member) -- and then, if that's okay with you, resubmit what's left
 for your perusal?

It's okay.

Kind regards,

Veit

--
BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerryreg; mobile platform with sessions, labs  more.
See new tools and technologies. Register for BlackBerryreg; DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
___
CLucene-developers mailing list
CLucene-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clucene-developers


Re: [CLucene-dev] Compiling v.2.3.3.4 with VC6

2011-09-17 Thread Veit Jahns
Hi Celto!

2011/9/14 cel tix44 celti...@gmail.com:
 Team
 When compiled with VC6, v.2.3.3.4 throws some 300 errors.
 May I please ask the DEV team whether Clucene is still going to be
 compatible with VC6?

I think, it was not intended in the first place. This release includes
some parts of the Boost library 1.42. And this version does not
support VC6 [1]. But otherwise, only small parts of the Boost library
are used, so maybe this is not a big issue. And if there is a need
that this version can be compiled with VC6, we should at least try to
make it compile. What kind of errors do you get?

 If yes, I'll fix what I can, but I will need help from the DEV team where
 it's over my head, please.

If I can assist you with this, I will do so.

Kind regards,

Veit

[1] http://www.boost.org/users/history/version_1_42_0.html

--
BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
___
CLucene-developers mailing list
CLucene-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clucene-developers