> With an earlier version 13549 compiled 100% for BCC. With the latest
> releases from Harbor began to appear that these errors. If I can fix it for
> me to continue to use BCC ?
>
>
> Franček Prijatelj wrote:
>>
>> I use mingw and MSVC8 with minigui extended (distribution by Grigory
>> Filatov)
Hello Franček Prijatelj,
With an earlier version 13549 compiled 100% for BCC. With the latest
releases from Harbor began to appear that these errors. If I can fix it for
me to continue to use BCC ?
Franček Prijatelj wrote:
>
> I use mingw and MSVC8 with minigui extended (distribution by Grigor
> Thank You.
> I see in hbdefs.h:
>
> /* Include windows.h if applicable and requested */
> #if defined( HB_OS_WIN_USED ) && defined( HB_OS_WIN )
>
> #include
> #if defined( __GNUC__ )
> #define HB_DONT_DEFINE_BASIC_TYPES
> #endif
>
> But I'am compiling daily minigui extended with mi
Hi
Thank You.
I see in hbdefs.h:
/* Include windows.h if applicable and requested */
#if defined( HB_OS_WIN_USED ) && defined( HB_OS_WIN )
#include
#if defined( __GNUC__ )
#define HB_DONT_DEFINE_BASIC_TYPES
#endif
But I'am compiling daily minigui extended with mingw and MSVC8.
> I use mingw and MSVC8 with minigui extended (distribution by Grigory
> Filatov)
> and I have no problems with any compiler.
> Because minigui uses win32 appi, You have to #include
You have to _request_ windows.h using HB_OS_WIN_USED
(formerly HB_OS_WIN32_USED).
That's all. MINIGUI code wasn't
> Hi
>
> You have to insert #include "windows.h" in every *.c file. (after #include
> "hbapi.h")
> I did it localy and it works.
No, it's wrong solution. It's one of the most
popular misconceptions about using windows API
with Harbour.
Instead, see these:
2010-01-13 15:10 UTC+0100 Viktor Sz
Hi
I use mingw and MSVC8 with minigui extended (distribution by Grigory
Filatov)
and I have no problems with any compiler.
Because minigui uses win32 appi, You have to #include
BRGS
Rossine wrote:
>
> Hello Horodyski,
>
> I use minigui extended. Currently I use Borland BCC. What is the adv
Hi
It's a consequence of . and commenting out #include "windows.h"
Franček Prijatelj wrote:
>
> Hi
>
> You have to insert #include "windows.h" in every *.c file. (after #include
> "hbapi.h")
> I did it localy and it works.
> It's a consequence of latest replacements of X types wit
Hi
You have to insert #include "windows.h" in every *.c file. (after #include
"hbapi.h")
I did it localy and it works.
It's a consequence of latest replacements of X types with HB_ in
Harbour trunk.
Anyhow I think that Grigory Filatov will have to change it.
BRGS
Rossine wrote:
>
>
Hello All,
Thanks for the tips and explanations but for now I want to continue using
the borland. Today I tried to compile with the 13627 release and the errors
continue. Using the 13549 release everything works OK.
Below I list some of the errors:
[ERRORS]
MiniGui.lib
Borland C++ 5.5.1 for
>>> I haven't said nobody uses is, but seemingly nobody who'd
>>> need it is willing to put any effort into it.
>
> not with MingW, i guess.
For sure MINGW is used by MINIGUI, which (AFAIK)
offers .dll call support, so probably everything
is out there to make it work somehow.
>>> and I rarely
>>I haven't said nobody uses is, but seemingly nobody who'd
>>need it is willing to put any effort into it.
not with MingW, i guess.
>>and I rarely see even a 'thank you',
Ohh, I must object this one. there are _LOT_ of 'thank you's for you and
others in these posts, not as many as you de
>> Nobody seems to be interested, or waits for others to fix it.
>> Someone will have to actually look into it.
>>
>> Sad. How is that possible that nobody uses it? Is there an alternative?
>> I'd love to look into it, but my knowledge in C & Harbour internals is
>> less then zero!
I haven't sai
Viktor Szakáts wrote:
>
>
> Nobody seems to be interested, or waits for others to fix it.
> Someone will have to actually look into it.
>
> Sad. How is that possible that nobody uses it? Is there an alternative?
> I'd love to look into it, but my knowledge in C & Harbour internals is
> less
> Viktor Szakáts wrote:
>>
>>
>> - handles .dlls better
>>
>
> Is DLLCALL fixed? for me it still GPFs with Mingw. I'd love to use Mingw,
> but this is a stopper for me.
Nobody seems to be interested, or waits for others to fix it.
Someone will have to actually look into it.
It's not a MINGW b
Viktor Szakáts wrote:
>
>
> - handles .dlls better
>
Is DLLCALL fixed? for me it still GPFs with Mingw. I'd love to use Mingw,
but this is a stopper for me.
Best regards
Abe
--
View this message in context:
http://n2.nabble.com/errors-with-release-13584-tp4396199p4399481.html
Sent from t
gt;> -Original Message-
>> From: Rossine [mailto:qii...@ig.com.br]
>> Sent: Friday, January 15, 2010 1:14 PM
>> To: harbour@harbour-project.org
>> Subject: RE: [Harbour] errors with release 13584
>>
>>
>> Hello Horodyski,
>>
>> I use
>-Original Message-
>From: Rossine [mailto:qii...@ig.com.br]
>Sent: Friday, January 15, 2010 1:14 PM
>To: harbour@harbour-project.org
>Subject: RE: [Harbour] errors with release 13584
>
>
>Hello Horodyski,
>
>I use minigui extended. Currently I use Borland B
Hello Horodyski,
I use minigui extended. Currently I use Borland BCC. What is the advantage
to using MingGW ?
Best Regards,
Rossine.
--
View this message in context:
http://old.nabble.com/errors-with-release-13584-tp27170267p27174837.html
Sent from the Harbour - Dev mailing list archive at N
>-Original Message-
>From: Rossine [mailto:qii...@ig.com.br]
>Sent: Friday, January 15, 2010 12:54 AM
>To: harbour@harbour-project.org
>Subject: [Harbour] errors with release 13584
>
>
>Hello,
>
>I compile minigui com this release and i see this errors:
>
>[ERRORS]
>
>MiniGui.lib
>
>Borlan
20 matches
Mail list logo
