UE Studio & xHarbour Builder

[TimStone]

I have UE Studio (current version ) but manually run xHarbour Builder. With Multi Edit I could do my builds from within the Editor. So far all the setup comments I have seen here are for doing compile/build with Borland.

Does anyone have guidelines for configuring UE Studio to work with xHarbour Builder, including keyword highlighting ? Also, I have still found it doesn't do a real good job of reformatting .prg files. That was a strength of Multi-Edit with Evolve.

Any input specific to this compiler/linker would be appreciated.

[Antonio Linares]

Tim,

Please review FWH\uestudio\FWH.zip provided files inside it.

For the syntax highlight, please review this topic:
viewtopic.php?f=17&t=12908

[Richard Chidiak]

Tim

I would highly recommend to use Borland compiler with Uestudio

This is a very reliable solution, i have abandoned xhb builder since quite a time now and i am using uestudio with borland , no problem at all

Antonio provides xharbour builds that i use that are tested and we have full support

Just my 2cents

Richard

[Massimo Linossi]

Hi Richard.
I want to make the same change that you already made.
Have you found any difference crossing from Xharbour builder to Borland ?
And now many functions, or commands, did you change ?
Thanks a lot.
Massimo.

[Richard Chidiak]

Massimo

It is quite straight forward,

If you are using third party libaries (tsbutton, tsbrowse, vrd...etc) you need to build them for borland, you can do this with uestudio, all projects are available

you just have to build the uestudio project (add all the prg files and rc files) and then you're done and make sure uestudio config file finds your third party library but you do this only once....

If you need help building project , let me know, i can send you a sample of a project file

Hth

Richard

[frose]

Tim,

I switched from MultiEdit with Evolve to UEStudio for 2 years or so and I don't miss MultiEdit anymore. For reindenting and for function cross-reference list, I'm using 'click' developed by Phil Barnett, you can find it here: http://www.the-oasis.net/.

For building projects I'm also working with the xHarbour builder, asking me why, found only two reasons:

1 - By habit
2 - The 'Visual xHarbour Debugger' VxD

And of course only the second one is substantially.

So, if 'FWDbg' can substitute VxD, there is nothing more to say against the combination 'Borland compiler with Uestudio'.

Perhaps I find the time to test 'FWDbg' and the building project capabilities of UEStudio in the next weeks, knowing I have the great assistance of this forum (Antonio, Richard, Otto, ...)

HTH

[TimStone]

Thanks for the comments.

I am curious why the Borland compiler is considered the better option. Have you found actual program performance differences ? If so, what are they ?

I have used xHarbour Builder because of 1) Microsoft compatibility, and 2) It helps to support the continuing development efforts.

[frose]

Tim wrote:

I am curious why the Borland compiler is considered the better option. Have you found actual program performance differences ? If so, what are they ?

I don't expect performance differences, but as already said, I have no further experience with the Borland or other compiler.

As retrieved in this forum (e. g. viewtopic.php?f=3&t=16384) you have already tried to switch to UEStudio and BCC last summer. Are there some experiences you can share here?

Tim wrote:

I have used xHarbour Builder because of 1) Microsoft compatibility, and 2) It helps to support the continuing development efforts.

Your reasons sounds a little bit nebulous. So I assume you havn't - same as I - further substantially reasons (except debugging) to stay with xHarbour Builder?

[Antonio Linares]

Tim, Frank,

IMO these are pros and cons for each compiler:

Borland:
Pros: Used since the very beginning of the Harbour and xHarbour projects. Traditionally quite friendly. Free.
Cons: It is not available for 64 bits, neither Windows Mobile, neither Linux and OSX.

Microsoft C:
Pros: Available for 64 bits and Windows Mobile. Difficult to isolate it as it is distributed as part of Visual Studio. Included for free in demo versions of Visual Studio.
Cons: It is not available for Linux, neither OSX.

gcc (GNU C compiler):
Pros: Available for ALL operating systems: Windows, 64, Windows Mobile, Linux and OSX. Free. Learn it once and use it everywhere.

PellesC (included and renamed in xHB comercial):
Pros: Free. Highly compatible with Microsoft C.
Cons: It is not available for Windows Mobile, neither Linux, neither OSX. It does not support C++ code.

My vote: gcc seems the best way to go, but actually most FWH users keep using Borland C

[IBTC]

My vote: gcc seems the best way to go

I agree.

Do you also offer libs for gcc in future now?

[Antonio Linares]

Ruediger,

We already have FWH built using (MinGW: Minimalist GNU for Windows) gcc and we provide a samples\buildg.bat to build the apps.

We have not included those LIBs in FWH setup (we will do it from next version on). If you want them, please send me an email, thanks

[IBTC]

We have not included those LIBs in FWH setup (we will do it from next version on). If you want them, please send me an email, thanks

Thanks! Done.

[Enrico Maria Giordano]

gcc (GNU C compiler):
Pros: Available for ALL operating systems: Windows, 64, Windows Mobile, Linux and OSX. Free. Learn it once and use it everywhere.

Cons: It is no friendly at all. Just to compile an "hello world" sample can be a nightmare. The real problem is that it's too Unix/Linux centered.

EMG

[Antonio Linares]

Dear Enrico,

See how easy is to build a "Hello world"

test.c

Code: Select all | Expand

#include <stdio.h>

int main( char * argv, int argc )
{
   printf( "Hello world!\n" );
   return 0;
}
 

to build it:

Code: Select all | Expand

gcc test.c -otest
 

thats it It will compile and link the executable "test"

IMO we are too much used to Borland C

[PAUL SIMM]

Could someone please post a sample project file for UE Studio and xHarbour.