Embarcadero Releases Free C++ Compiler for Windows

[AntoninoP]

I'm trying to compile xHarbour with the new compiler. First problem, I get:

Code: Select all

e:\fw\bcc101\include\windows\sdk\windows.h:42:9: warning: unknown pragma ignored [-Wunknown-pragmas]
#pragma region Application Family or OneCore Family

Any ideas?

EMG

Code: Select all

#pragma region

is only a microsoft feature, i suggest to surround it in a ifdef like say here: http://stackoverflow.com/a/23561973/854279

[Enrico Maria Giordano]

Code: Select all

#pragma region

is only a microsoft feature, i suggest to surround it in a ifdef like say here: http://stackoverflow.com/a/23561973/854279

It's not in my code. And it is not the only problem. I don't want to alter compiler code.

EMG

[toninhofwi]

Hi Enrico.

Try edit next files and please, change bcc55 to your bcc path:

bcc32c.cfg:
-I"c:\harbour\bcc55\include";"c:\harbour\bcc55\include\windows\crtl";"c:\harbour\bcc55\include\windows\rtl";"c:\harbour\bcc55\include\windows\sdk";"c:\harbour\bcc55\include\dinkumware64"
-L"c:\harbour\bcc55\lib\win32c\release";"c:\harbour\bcc55\lib\win32c\release\psdk"

ilink32.cfg
-L"c:\harbour\bcc55\lib\win32c\release";"c:\harbour\bcc55\lib\win32c\release\psdk"

best regards'.

PS: this is only an idea, not tested yet...

[Enrico Maria Giordano]

The paths are already fine. The problem is the include files of the new compiler or some compiler switch to use for disable the warning.

EMG

[toninhofwi]

IMHO is time to think to move from bcc to mingw.

I compiled harbour with mingW using msys2 and all is fine including all samples from fwh.

The only problem that I see is with resources, we need replace "\" by "/"

Regards.

[Enrico Maria Giordano]

IMHO is time to think to move from bcc to mingw.

Why? I need I real reason or I'm not interested. MinGW is from Linux, a world that I don't like very much.

EMG

[toninhofwi]

IMHO is time to think to move from bcc to mingw.

Why? I need I real reason or I'm not interested. MinGW is from Linux, a world that I don't like very much.

EMG

I understand you, but the classic BCC was killed and this new BCC is a clang based compiler (http://clang.llvm.org/)

Regards.

[Enrico Maria Giordano]

I understand you, but the classic BCC was killed and this new BCC is a clang based compiler (http://clang.llvm.org/)

So? What's the point?

EMG

[toninhofwi]

MinGW is from Linux, a world that I don't like very much.

Enrico this new bcc is clang based, if you don't like Linux, maybe you don't like clang too.

Andi post on harbour devel sometimes ago that BCC clang edition is very slow and now I read this:

http://community.embarcadero.com/answer ... -very-slow

[Antonio Linares]

We may consider to keep using BCC 7.0 if 7.2 is slower

[Enrico Maria Giordano]

Enrico this new bcc is clang based, if you don't like Linux, maybe you don't like clang too.

I like BCC because is small and simple to use. There is no so much differences between normal and clang version in size and use. So I'd happily use clang version if only I could solve the problem that I reported above.

Andi post on harbour devel sometimes ago that BCC clang edition is very slow and now I read this:

http://community.embarcadero.com/answer ... -very-slow

I already made some test with pure C and It seemed faster in compiling and producing a smaller EXE. I don't know if this is true with [x]Harbour/FWH EXEs too. That's the reason why I'm trying to compile xHarbour with clang version, without success so far.

EMG

[Enrico Maria Giordano]

We may consider to keep using BCC 7.0 if 7.2 is slower

We can use "normal" (non clang) version of BCC 7.2 that is working just fine. You can download it from Mel Smith website (http://www.whosaway.com).

EMG

[Enrico Maria Giordano]

I'm trying to compile xHarbour with the new compiler. First problem, I get:

Code: Select all

e:\fw\bcc101\include\windows\sdk\windows.h:42:9: warning: unknown pragma ignored [-Wunknown-pragmas]
#pragma region Application Family or OneCore Family

Any ideas?

EMG

Up.

Please note that any single include file of the include\windows directory have

#pragma region

inside it. Surely there has to be a way to disable that warning. But how?

EMG

[Antonio Linares]

-Wno-unknown-pragmas ?

[Enrico Maria Giordano]

Code: Select all

E2075 Incorrect command line option: -Wno-unknown-pragmas

EMG