Hi David,

>> I did notice it and thanks for these tests, but I'd suggest
>> to patch (or send patches for) existing .hbc files, after you
>> tested them with hbmk2 successfully using OS/2 specific 3rd
>> party lib names. It's rather inefficient if I edit them without
>> testing and we iterate it endlessly. Plus for me it's impossible
>> to decide which one of the possible true OS/2 lib name setups
>> should be put into SVN .hbc files. Ideally the default here
>> should be what _most_ OS/2 users would expect.
> 
>> You should add:
>> {os2}libs=...
> 
>> Plus you should exclude existing libs= lines with
>> {!os2} if they are not currently protected.
> 
> Messages were for specific cases, not only libs list
> 
> a) hbcurl
>  * Fail to build with OpenWatcom
>  * undefined symbols in os2gcc
>  Alternatives:
>  - Fix source code
>  - or, perhaps hbcurl does not work in OpenWatcom

Easily possible. The errors you sent are 
all reported in system headers and libcurl 
headers. We can't fix those in Harbour.

Ideally this problem should be reported to 
libcurl developers.

Unfortunately there is no way to disable 
dependency detection for platform/compiler 
combinations (os2/watcom) in Harbour, so OS/2 
users will have to make sure not to set 
HB_WITH_CURL when building for watcom.

> b) hbcairo
>  Missing function in one sample
>  Alternatives:
>  - Fix source code
>  - or, perhaps sample fail in any platform

It seems that OS/2 cairo version has no 
'CAIRO_HAS_IMAGE_SURFACE' support, and this 
makes test app break. The correct fix here is to 
provide Harbour level function regardless of 
cairo version, but return permanent error in 
this case. This is the method used in all other 
Harbour lib bindings.

I hope Mindaugas can fix it.

> c) Contrib libs readme*
>  Libs list required for each contrib based on my tests
>  Alternatives:
>  - Modify *.h* files by myself
>  - Describe list, done in readme* file

Lib dependencies are never documented in INSTALL, 
instead, they are configured in appropriate .hbc files.
In INSTALL, we can document _package_ dependencies 
and packages web links, but never actual lib filenames.

> d) hbqt
>  List of source files which have errors on OS/2 and detailed flow of tests
>  Alternatives:
>  - Fix source code
>  - Perhaps this code does not work on OS/2 - Qt

I can't comment on those. Only that the bool conversion 
problem could probably be easily fixed (unless it's an 
OS/2 compiler bug), for someone good in C++.

> 
>  But Pritpal is highly focused in hbide now   :-)
> 
>  Most errors are of kind:
>  'A' is not a member of 'B'
>  class 'C' has no member named 'D'
>  'E' was not declared in this scope
>  expected primary-expression before ')' token
>  invalid use of incomplete type 'F'
>  incomplete type 'G' used in nested name specifier
>  forward declaration of 'H'
>  expected type-specifier before 'I'
> 
>  I do not know if:
>  - Are valid errors which must be fixed on Harbour
>  - Other compiler switchs required
>  - They are errors related to OS/2-Qt code and not Harbour
> 
>>> My mail file for Harbour messages reached 105 Mb file size and no one
>>> editor in OS/2 can open it ( EPM, E, TEDIT, JEdit )  :-)
> 
>> (if it's a text file you can use 'grep')
> 
> But grep does not show context around each found

According to its own help, it does:
---
Context control:
  -B, --before-context=NUM  print NUM lines of leading context
  -A, --after-context=NUM   print NUM lines of trailing context
  -C, --context=NUM         print NUM lines of output context
  -NUM                      same as --context=NUM
      --color[=WHEN],
      --colour[=WHEN]       use markers to highlight the matching strings;
                            WHEN is `always', `never', or `auto'
---

Brgds,
Viktor

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to