Building xHarbour with BCC32 7.70 and BCC32C 7.30

[Reynaldo Henrique]

I would like to informe you that a can build xHarbour with BCC32 7.70
and BCC32C 7.30 sucessfully!


Thanks you,


Reynaldo Henrique

[Enrico Maria Giordano]

I would like to informe you that a can build xHarbour with  BCC32 7.70
and BCC32C 7.30 sucessfully!

Great! Can I see your batch?

[Reynaldo Henrique]

Post by Enrico Maria Giordano

I would like to informe you that a can build xHarbour with  BCC32 7.70
and BCC32C 7.30 sucessfully!

Great! Can I see your batch?

I am using only the make_bc all and setting the c:\borland\bin in the
PATH and the c:\bcc102\bin in the PATH


Reynaldo Henrique

[Reynaldo Henrique]

I am using only the make_bc all and setting the c:\borland\bin in the

Post by Reynaldo Henrique
PATH and the c:\bcc102\bin in the PATH

My bcc32.exe folder is c:\borland\bcc770\bin.
And my bcc32c.exe folder is c:\bcc102\bin

Reynaldo Henrique

[Enrico Maria Giordano]

Post by Reynaldo Henrique

Post by Enrico Maria Giordano
Great! Can I see your batch?

I am using only the make_bc all and setting the c:\borland\bin in the
PATH and the c:\bcc102\bin in the PATH

Can I see the exact batch you are using?

[Reynaldo Henrique]

Post by Enrico Maria Giordano

Post by Reynaldo Henrique

Post by Enrico Maria Giordano
Great! Can I see your batch?

I am using only the make_bc all and setting the c:\borland\bin in the
PATH and the c:\bcc102\bin in the PATH

Can I see the exact batch you are using?

I am using the original batch file MAKE_BC.BAT, without any changes.



Reynaldo Henrique

[Enrico Maria Giordano]

Post by Reynaldo Henrique

Post by Enrico Maria Giordano
Can I see the exact batch you are using?

I am using the original batch file MAKE_BC.BAT, without any changes.

So, you are just open a console and write

make_bc

?

[Ron Pinkas]

Post by Enrico Maria Giordano

Post by Reynaldo Henrique

Post by Enrico Maria Giordano
Can I see the exact batch you are using?

I am using the original batch file MAKE_BC.BAT, without any changes.

So, you are just open a console and write
make_bc
?

Yes Enrico, that's what every user should expect and whatt I always did.
The work I did now was exactly tto ensure that this continue to be case
with all new compilers.

[Enrico Maria Giordano]

Post by Ron Pinkas

Post by Enrico Maria Giordano
So, you are just open a console and write
make_bc
?

Yes Enrico, that's what every user should expect and whatt I always did.
The work I did now was exactly tto ensure that this continue to be case
with all new compilers.

If I do so, I get:

For your convenience xHarbour's bin directory was added to your PATH.
For your convenience xHarbour's bin directory was added to your PATH.
For your convenience xHarbour's bin directory was added to your PATH.
Searching for Borland C++...
"ERROR: Borland C++ not found!"

------------------------------
Make Utility for Borland C/C++
------------------------------

Borland C/C++ not found.
Please install and try again.

[Reynaldo Henrique]

Post by Enrico Maria Giordano
For your convenience xHarbour's bin directory was added to your PATH.
For your convenience xHarbour's bin directory was added to your PATH.
For your convenience xHarbour's bin directory was added to your PATH.
Searching for Borland C++...
"ERROR: Borland C++ not found!"
 ------------------------------
 Make Utility for Borland C/C++
 ------------------------------
 Borland C/C++ not found.
 Please install and try again.

I add c:\borland\bcc770\bin to windows PATH and so I compile xHarboour
and so I compile xharbour with bcc32
alternatively I add c:\bcc102\bin to windows PATH and so I compile
xHarbour with bcc32c
Each time I add a new compiler I open a command prompt again.


Reynaldo Henrique

[Enrico Maria Giordano]

Post by Reynaldo Henrique
I add c:\borland\bcc770\bin to windows PATH and so I compile xHarboour
and so I compile xharbour with bcc32
alternatively I add c:\bcc102\bin to windows PATH and so I compile
xHarbour with bcc32c
Each time I add a new compiler I open a command prompt again.

With this commands:

SET PATH=%PATH%;e:\bcc32\bcc\bin
make_bc all

I get this on the log:

ILINK32 -ap -Tpe -x -Gn -C -Llib\b32 -LECHO disattivato. c0x32.obj
obj\b32\hblib.obj ,bin\b32\hblib.exe,, ws2_32.lib cw32mt.lib
import32.lib
Turbo Incremental Link 6.97 Copyright (c) 1997-2022 Embarcadero
Technologies, Inc.
Fatal: Unable to open file 'DISATTIVATO.'

[Reynaldo Henrique]

Post by Enrico Maria Giordano
SET PATH=%PATH%;e:\bcc32\bcc\bin
make_bc all
    ILINK32  -ap -Tpe -x -Gn -C -Llib\b32 -LECHO disattivato.
c0x32.obj obj\b32\hblib.obj  ,bin\b32\hblib.exe,,   ws2_32.lib
cw32mt.lib import32.lib
Turbo Incremental Link 6.97 Copyright (c) 1997-2022 Embarcadero
Technologies, Inc.
Fatal: Unable to open file 'DISATTIVATO.'

I edit the windows environment PATH each time I use a new compiler


Reynaldo Henrique

[Enrico Maria Giordano]

With this command:

SET PATH=%PATH%;e:\temp\bcc77\bin
make_bc all

I get this on the console:

For your convenience xHarbour's bin directory was added to your PATH.
For your convenience xHarbour's bin directory was added to your PATH.
For your convenience xHarbour's bin directory was added to your PATH.
Searching for Borland C++...
Creating System Files (ST) ...
In file included from utils\misc\hblib.c:61:
e:\fw\temp\bcc77\bin\..\include\windows\sdk\windows.h:42:9: warning:
unknown pragma ignored [-Wunknown-pragmas]
#pragma region Application Family or OneCore Family
^
In file included from utils\misc\hblib.c:61:
In file included from
e:\fw\temp\bcc77\bin\..\include\windows\sdk\windows.h:204:
In file included from
e:\fw\temp\bcc77\bin\..\include\windows\sdk\windef.h:25:
In file included from
e:\fw\temp\bcc77\bin\..\include\windows\sdk\minwindef.h:15:
In file included from
e:\fw\temp\bcc77\bin\..\include\windows\sdk\specstrings.h:62:

and tons of similar warnings.

[Reynaldo Henrique]

Post by Enrico Maria Giordano
SET PATH=%PATH%;e:\temp\bcc77\bin
make_bc all
For your convenience xHarbour's bin directory was added to your PATH.
For your convenience xHarbour's bin directory was added to your PATH.
For your convenience xHarbour's bin directory was added to your PATH.
Searching for Borland C++...
Creating System Files (ST) ...
unknown pragma ignored [-Wunknown-pragmas]
#pragma region Application Family or OneCore Family
        ^
In file included from
In file included from
In file included from
In file included from
and tons of similar warnings.
Here I don't have the messages that you have.

Reynaldo Henrique

[Enrico Maria Giordano]

Post by Enrico Maria Giordano
Here I don't have the messages that you have.

Can I see your bcc32.cfg and bcc32c.cfg?

[Reynaldo Henrique]

Enrico,

Post by Enrico Maria Giordano
Can I see your bcc32.cfg and bcc32c.cfg?

Of course,

my bcc32.cfg:

-I"c:\borland\bcc770\include";"c:\borland\bcc770\include\dinkumware";"c:\borland\bcc770\include\windows\crtl";"c:\borland\bcc770\include\windows\rtl";"c:\borland\bcc770\include\windows\vcl";"c:\borland\bcc770\include\windows\sdk"

-I"c:\borland\bcc770\include\windows";"c:\borland\bcc770\include\windows\vcl";"c:\borland\bcc770\include\windows\rtl";"c:\borland\bcc770\include\windows\sdk";"c:\borland\bcc770\include\dinkumware";"c:\borland\bcc770\include\windows\crtl"

-L"c:\borland\bcc770\lib\win32\release";"c:\borland\bcc770\lib\win32\release\psdk"


My bcc32c.cfg:

-isystem @\..\include\dinkumware64
-isystem @\..\include\windows\crtl
-isystem @\..\include\windows\sdk
-L@\..\lib\win32c\debug
-L@\..\lib\win32c\release
-L@\..\lib\win32c\release\psdk
-Xdriver -Qunused-arguments

Reynaldo Henrique

[Enrico Maria Giordano]

Post by Reynaldo Henrique
-I"c:\borland\bcc770\include";"c:\borland\bcc770\include\dinkumware";"c:\borland\bcc770\include\windows\crtl";"c:\borland\bcc770\include\windows\rtl";"c:\borland\bcc770\include\windows\vcl";"c:\borland\bcc770\include\windows\sdk"
-I"c:\borland\bcc770\include\windows";"c:\borland\bcc770\include\windows\vcl";"c:\borland\bcc770\include\windows\rtl";"c:\borland\bcc770\include\windows\sdk";"c:\borland\bcc770\include\dinkumware";"c:\borland\bcc770\include\windows\crtl"
-L"c:\borland\bcc770\lib\win32\release";"c:\borland\bcc770\lib\win32\release\psdk"

Tried: no change.
This is for BCC64.
@ is not supported for -L command, as far as I know.

Post by Reynaldo Henrique
-Xdriver -Qunused-arguments

These are wrong compiler switches. It seems you are not using this
bcc32c.cfg at all.