Anyone compiled Borland OWL (Object Windows Library) with winelib ?

[Grzegorz Prokopski]

Hi !

I am unable to find this information in wine-devel archives, so I
decided to ask here.

Q1: Have You heard about anyone who compiled Borland OWL (Object
Windows Library) based project with winelib ? Yeah - I know it is
an old library and Borland C++ 5.02 is the last version released
a few years ago and without future updates.

Anyway I have a project which IS written in OWL and need to check
how hard will it be to make it working under Linux without
rewriting it all.

I belive I have the sources for complete OWL of course.

Q2: With You expirience what would You say to that statment:
If my OWL-based program works under Wine it should be convertable
to winelib.
How true is that statment ?

Q3: I have read docs about using winelib and seen that there is
MS Visual C++ mentioned many times. Does MS VC++ have some kind
of support in winemake or in winelib itself ? Does OWL case differ
much from MS VC++ ?

Thank You for Your answers.

Grzegorz Prokopski

[eric pouech]

> Q1: Have You heard about anyone who compiled Borland OWL (Object
> Windows Library) based project with winelib ?

not to my knowledge
> Anyway I have a project which IS written in OWL and need to check
> how hard will it be to make it working under Linux without
> rewriting it all.

well, it might be possible. some folks have been successful with MFC
however, it has to be checked which BCC++ specific extensions were
used by OWL
> I belive I have the sources for complete OWL of course.

this would be necessary... since OWL is a C++ lib, the DLL linking
is done on decorated names, and since GCC and BCC don't use the same
you need to recompile OWL
> Q2: With You expirience what would You say to that statment:
> If my OWL-based program works under Wine it should be convertable
> to winelib.
> How true is that statment ?

well, it has to be further checked. I'd say likely (as it's possible
with MFC)
> Q3: I have read docs about using winelib and seen that there is
> MS Visual C++ mentioned many times. Does MS VC++ have some kind
> of support in winemake or in winelib itself ?

what winemaker does provide is a quick way to convert an existing
code base for building into winelib. however, it doesn't provide (yet)
the project/dependencies/specific rules you can build in any powerful
IDE
> Does OWL case differ much from MS VC++ ?

they are different beasts. OWL is a C++ lib, MS VC++ is
compiler/IDE/MFC...
coffee machine (oops this has been disabled lately for C# compliance)

A+

Borland OWL & winelib ?

[Grzegorz Prokopski]

eric pouech wrote:
> > Q1: Have You heard about anyone who compiled Borland OWL (Object
> > Windows Library) based project with winelib ?
>
> not to my knowledge

I am trying ATM.
> > Anyway I have a project which IS written in OWL and need to check
> > how hard will it be to make it working under Linux without
> > rewriting it all.
>
> well, it might be possible. some folks have been successful with MFC
> however, it has to be checked which BCC++ specific extensions were
> used by OWL

Yeah, I've read the docs. Gonna check it by experiment.
> > Q2: With You expirience what would You say to that statment:
> > If my OWL-based program works under Wine it should be convertable
> > to winelib.
> > How true is that statment ?
>
> well, it has to be further checked. I'd say likely (as it's possible
> with MFC)

May there be any other problems than with source-compiler ones ?
It is quite old lib and I wouldn't expect it to use any "new" windows
api features. Much less than current MFC - I am sure.
> > Does OWL case differ much from MS VC++ ?
>
> they are different beasts. OWL is a C++ lib, MS VC++ is
> compiler/IDE/MFC...
> coffee machine (oops this has been disabled lately for C# compliance)

I was thinkig about OWL vs. MFC difference. Don't know why my fingers
wrote MS VC++ ;-) Nevermind then.

Going back to the OWL sources & wine ;-) (And getting some beer as it
is late evening in Poland now ;-)

Thanks
    			Grzegorz Prokopski

Borland OWL & winelib ?

[eric pouech]

> > well, it has to be further checked. I'd say likely (as it's possible
> > with MFC)
>
> May there be any other problems than with source-compiler ones ?
> It is quite old lib and I wouldn't expect it to use any "new" windows
> api features. Much less than current MFC - I am sure.

my main concern isn't against API support (some native OWL should run in
wine). it's more compilation issues that we may face (like use of
pragma,
specific preprocessor extents..., some 32/16 bit discrepencies).
Compiling MFC under wine is not a piece of cake (and furthermore,
details
have never been released because of copyright issues)
> Going back to the OWL sources & wine ;-) (And getting some beer as it
> is late evening in Poland now ;-)

don't code and drink ;-)

A+