Many thanks, I will test it in a sec.
What I'd like to do is disable FM STAT for all default builds.
So users would rather need HB_FM_STATISTICS, if they need
it permanently enabled for some (to me wierd looking) reason.
Do you see a problem with that?
Brgds,
Viktor
On 2008.11.12., at 23:16, P
>Hi Viktor and Toninho
>Please check the location of c0d32.obj and if it's known for BCC
>compiler so it can locate during linking. AFAIR ilink in BCC needs
>valid paths set in ilink32.cfg. It was -L option or sth like that.
>You can also use bcc32.exe as wrapper to ilink32.exe and if I'm
>not wro
Hi Przemek,
Very good point. It may explain Toninho's problem
well. Since he was not using the central config files
(which is BTW an install time requirement for all
Borland C compilers), and he was only copying in
bcc32.cfg, ilink32 was clueless about lib dirs.
Thanks a lot. This also means thi
Hi Przemek,
If you try to enable memory statistic in shared
binaries using harbour.dll then it will not work
in such way. In MS-Windows DLL is not shared library
like in other systems but complete executable which
only public some entries. It means that any internal
bindings cannot be overloaded
2008-11-12 23:28 UTC+0100 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
* harbour/source/rtl/hbgtcore.c
! removed code I committed by mistake.
best regards
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/
2008-11-12 23:16 UTC+0100 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
* harbour/source/vm/fm.c
+ added support for enabling/disabling memory statistic when
application starts. To enable memory statistic it's enough
to set HB_FM_STAT environment variable to non empty value.
T
On Wed, 12 Nov 2008, Szak�ts Viktor wrote:
Hi Viktor,
>> Dont' you afraid that we will end with winvista, winxp,
>> win9x, win64 and other subdirectories?
> No. WinCE is a different beast than the rest of
> the flavors, as you must know the best. We also have
> the special macro HB_WINCE internal
On Wed, 12 Nov 2008, Szak�ts Viktor wrote:
Hi Viktor and Toninho
>>> BTW, do you have a 'c0d32.obj' in your Borland lib dir?
>> Yes, I have.
> Very strange. No more ideas here. Anyone?
Please check the location of c0d32.obj and if it's known for BCC
compiler so it can locate during linking. AFAI
On Wed, 12 Nov 2008, Szak�ts Viktor wrote:
Hi Viktor,
> The idea is to build Harbour with mem stats off
> by default and to create hbfm.lib and MT version
> hbfmmt.lib as an alternative FM lib with mem
> stats turned on.
> I can't get it to work though.
If you try to enable memory statistic in s
2008-11-12 20:03 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
* doc/linux1st.txt
* Updated for Ubuntu 8.10.
--
Brgds,
Viktor
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
Hi folks,
I've been struggling with making non-GNU make
system to create hbfm.lib and hbfmmt.lib, just
like these exist in GNU make.
The idea is to build Harbour with mem stats off
by default and to create hbfm.lib and MT version
hbfmmt.lib as an alternative FM lib with mem
stats turned on.
Thi
Hi Przemek,
> Here is a bug in your code which creates the difference. It should be:
> ordCreate(, "T1", cKey, {|| &cKey} )
> otherwise you create index where key value is fixed "CODE" string in
> the given codeblock. CL53 DBFCDX/COMIX ignores codeblock but CL52 DBFCDX/
> SIX3 and DBFNTX doesn't
Hi Toninho,
Hi Viktor,
I did above changes, but I still need use HB_BUILD_DLL=no.
BTW, do you have a 'c0d32.obj' in your Borland lib dir?
Yes, I have.
Very strange. No more ideas here. Anyone?
Brgds,
Viktor
___
Harbour mailing list
Harbour@harbo
2008-11-12 19:11 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
* make_b32.bat
* make_b32.mak
* make_vc.bat
* make_vc.mak
* make_gcc.mak
* contrib/mtpl_b32.mak
* contrib/mtpl_gcc.mak
* contrib/mtpl_vc.mak
+ Added 'set HB_BUILD_OPTIM=no' option to disable
all C compiler op
On Wed, 12 Nov 2008, Pritpal Bedi wrote:
Hi Pritpal,
> I wonder why I took a long route whereas the shortest and
> neatest was awailable.
Please try to read carefully the text below. If you will not
understand sth then please ask about it. I'll try to help but
I need that you will want to create
On Mon, 10 Nov 2008, Szak�ts Viktor wrote:
Hi Viktor,
> I'd like to ask opinions whether to introduce wince
> as a distinct architecture in the GNU-make system.
> This would replace current w32/mingwce, w32/msvcce,
> w32/poccce builds with wince/mingw, wince/msvc,
> wince/pocc.
Dont' you afraid
2008-11-12 18:20 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
* source/common/hbverdsp.c
* Don't show '(C mode)', only C++.
--
Brgds,
Viktor
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/ha
Imo you can update gtwvg (also with provisory name file) as you want,
also with not working code
After this I hope that somebody can help you more easy
Or I miss something?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pritpal Bedi
Sent: Wednesday, Novem
>This shouldn't make a difference, at least in 5.5, but I've
>never tried that. I'd rather suggest to use C_USR to setup
>special Harbour flags '-5 -6'. '-WC' '-w-inl-' are surely
>unnecessary, and even '-a8' AFAIK. Then, the bcc32.cfg
>stored in your Borland C bin dir would only need -I and
>-L li
Hi Przemek,
I'd like to ask opinions whether to introduce wince
as a distinct architecture in the GNU-make system.
This would replace current w32/mingwce, w32/msvcce,
w32/poccce builds with wince/mingw, wince/msvc,
wince/pocc.
Dont' you afraid that we will end with winvista, winxp,
win9x, win6
Hello Przemek
I cannot think of myself so dumb :-((
I wonder why I took a long route whereas the shortest and
neatest was awailable.
Przemyslaw Czerpak-2 wrote:
>
> HB_FUNC( HB_GTINFO )
> {
>if( ISPOINTER( 1 ) && ISNUM( 2 ) )
>{
> PHB_GT pGT = hb_gt_ItemBase( hb_param( 1, HB_IT_
Massimo
>Do you plan implement a complete version in few month?
I will try as much I could.
But for sure someone should join me in this effort.
First let me expose the basic class structure and some
functional dmo code.
Once this is in place, I think we can go miles ahead.
Regards
Pritpal Be
I Highly appreciate the idea of partial but working xbase++ compatible
class structure in GTWVG
I can understand choice of rigidity for reliability
Do you plan implement a complete version in few month?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Prit
On Wed, 12 Nov 2008, Saulius Zrelskis wrote:
Hi Saulius,
> Sample below behaves different in Clipper and Harbour.
> Clipper:
> OrdKey: CODE
> KEYSIZE: 20
> 1 CODE: check over ORDKEYVAL: check over
> 2 CODE: check up ORDKEYVAL: check up
> 3
2008-11-12 14:44 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
* make_vc.mak
+ TOFIX added for the case when HB_CC_NAME is overridden
by user and MT/DLL targets are being created.
* common.mak
* source/common/hbver.c
% Minor opts.
--
Brgds,
Viktor
___
Hello Przemek,
Sample below behaves different in Clipper and Harbour.
Clipper:
OrdKey: CODE
KEYSIZE: 20
1 CODE: check over ORDKEYVAL: check over
2 CODE: check up ORDKEYVAL: check up
3 CODE: check outORDKEYVAL: check out
Harbou
On Wed, 12 Nov 2008, Maurilio Longo wrote:
Hi Maurilio,
> I think the problem is not in the code but in the flags used to build harbour,
> I've changed owatcom.cf this way
It's highly possible.
> I've removed nearly all compilation flags, I don't know what they mean, but
> anyway, I've always t
On Tue, 11 Nov 2008, Pritpal Bedi wrote:
Hi Pritpal,
> May be I could not present my case properly.
> I understand your implementation of new GT and also
> how it is behaving. My request is based on the new OBJECT
> modal I am building on lines with Xbase++ where I needed
> such functionality.
On Wed, 12 Nov 2008, Phil Barnett wrote:
Hi Phil,
> The difference is likely to be more pronounced when there are hundreds of
> variables that are public, vs hundreds of locals scattered throughout the
> software.
Neither in Clipper nor in [x]Harbour the speed of memvar variables
does not depe
Checked with an older version OS/2 MCP (Media Convenience Pack) which
have his own environment, so eCS paths, sets, files, libraries, dlls ...
are excluded
Same failures as in eCS 1.2MR
Using hbrun_mt.exe from eCS in OS/2 MCP
[E:\harbour811\harbour\tests]e:\harbour811\ow\b
2008-11-12 13:57 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
* source/common/hbverdsp.c
! Fixed displaying tracing status. (INFO and DEBUG level
counts as 'on'.)
--
Brgds,
Viktor
___
Harbour mailing list
Harbour@harbour-project.org
http:/
>I think the problem is not in the code but in the flags used to build
>harbour, I've changed owatcom.cf this way
>#CPPFLAGS = -j -w3 -d2 -5s -5r -fp5 -oxehtz -zq -zt0 -mf -bt=NT
>#DAVID: CPPFLAGS = -w2 -d1 -zq -bt=OS2
>CPPFLAGS = -w2 -d1 -zq -bt=OS2 -bm
>#architecture flags
>#CPPFLAGS += -5 -fp
Hi Jose,
Yesterday I updated trunk and could not see specific make for wince-
Pelles.
Which one can I use?
HB_ARCHITECTURE=w32
HB_COMPILER=poccce
You'll need GNU make and to run make_gnu.bat.
Brgds,
Viktor
___
Harbour mailing list
Harbour@harbour
2008-11-12 12:13 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
* make_b32.mak
* make_vc.mak
* common.mak
* utils/hbdoc/Makefile
* utils/hbmake/Makefile
* utils/hbtest/Makefile
* utils/hbrun/Makefile
% Setup to build shipped Harbour executables with -gc0.
; TODO: Please update
Hi Toninho,
[ I've just tested the default build using
BCC 5.8.2, and it finishes without error, just
as 5.5.1. ]
Maybe is related to my environment. I don´t have my bcc folders in
path. To compile Harbour, I copy bcc32.cfg to harbour folder and call
make_b32.bat
---bcc32.cfg---
-IE:\harbour\b
I'd suggest to try to solve this problem using
existing facilities. Pouring new variations into
the core seems not the best idea when we have
already quite some open problems around this area.
Brgds,
Viktor
On 2008.11.12., at 7:40, Pritpal Bedi wrote:
Przemek
May be I could not present my ca
Viktor,
JLC>> I would know if it is possible to build libs for wince using
JLC>PellesC.
JLC>>
JLC>> Is it possible ?
JLC>
JLC>Yes, it's possible.
Great!!
JLC>
JLC>Since yesterday it's even possible to build
JLC>Harbour for WinCE using Pelles C 5.0.
JLC>
Yesterday I updated trunk and could no
Hi Przemek,
> It should be fixed now.
That is true :)
Thank you.
Best regards,
Saulius
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
Przemyslaw, David,
I think the problem is not in the code but in the flags used to build harbour,
I've changed owatcom.cf this way
#CPPFLAGS = -j -w3 -d2 -5s -5r -fp5 -oxehtz -zq -zt0 -mf -bt=NT
#DAVID: CPPFLAGS = -w2 -d1 -zq -bt=OS2
CPPFLAGS = -w2 -d1 -zq -bt=OS2 -bm
#architecture flags
#CPPFLA
>As a workaround try disabling .dlls using:
>set HB_BUILD_DLL=no
Hi Viktor thanks. It works.
>[ I've just tested the default build using
>BCC 5.8.2, and it finishes without error, just
>as 5.5.1. ]
Maybe is related to my environment. I don´t have my bcc folders in
path. To compile Harbour, I copy
On Tuesday 11 November 2008 05:01:15 am Przemyslaw Czerpak wrote:
> Have you checked it?
> You'll be very surprised if you will make some tests.
> In tests/speedtst.prg tests 1-15 checks the speed of
> local, static, public, privates and fields.
> Do you see noticeable speed difference between firs
Hi Toninho,
This seems like an older problem exploited
by enabling .dll building by default.
As for the proper solution, it's difficult
to tell it without having this compiler
freely available.
As a workaround try disabling .dlls using:
set HB_BUILD_DLL=no
[ I've just tested the default build
42 matches
Mail list logo
