On Tue, 04 May 2010, Szak�ts Viktor wrote:
Hi,
> I still cannot see why f.e. you cannot update to
> the latest version, if it is important for you.
Let's say that there are some problems with current
xHarbour code and there is a chance that they will
be exploited by such update.
> Anyway, you
> I agre for support the latest available version of all tools
> For me is not a problem i can create a dummylib
Yes, it's also a good solution. Maybe the best.
> a generic way for remove autodetected library will be used also for use last
> hbmk2 with very oldest harbour
Could be, though IMO i
>> I personally prefer to support the latest available
>> version of all tools, if I have to choose between
>> them. We're talking about a free and open source
>> product, so there should be no technical to use old
>> version.
>>
>
> No, it is not correct in all circumstances.
> I stopped xHa
Viktor Szakáts wrote:
>
> I personally prefer to support the latest available
> version of all tools, if I have to choose between
> them. We're talking about a free and open source
> product, so there should be no technical to use old
> version.
>
No, it is not correct in all circumstances
I agre for support the latest available version of all tools
For me is not a problem i can create a dummylib
a generic way for remove autodetected library will be used also for use last
hbmk2 with very oldest harbour
2010/5/4 Viktor Szakáts
> I cannot decide on behalf of potential hbmk2 -xhb
I cannot decide on behalf of potential hbmk2 -xhb
users what is the best decision here.
I personally prefer to support the latest available
version of all tools, if I have to choose between
them. We're talking about a free and open source
product, so there should be no technical to use old
ve
i am using xharbour 1.0.0
is not possible remove this library from command line?
2010/5/4 Viktor Szakáts
> Use latest xhb CVS, which has this library.
>
> Viktor
>
> --
Massimo Belgrano
___
Harbour mailing list (attachment size limit: 40KB)
Harbour@har
Use latest xhb CVS, which has this library.
Viktor
On 2010 May 4, at 18:15, Massimo Belgrano wrote:
> Fatal: Unable to open file 'DBFNSX.LIB'
>
> with this hbp without DBFNSX.LIB
> -m
> -p
> -w0
> -oarcahd.exe
> -trace
> -DEURO
> -D__GTWVW__
> -GUI
> -b
> -oG:\clip52\LAVORI\MASSIMO\ARCA\ARCAHHD
Fatal: Unable to open file 'DBFNSX.LIB'
with this hbp without DBFNSX.LIB
-m
-p
-w0
-oarcahd.exe
-trace
-DEURO
-D__GTWVW__
-GUI
-b
-oG:\clip52\LAVORI\MASSIMO\ARCA\ARCAHHD
-workdir=G:/clip52/LAVORI/MASSIMO/ARCA/${hb_plat}/${hb_comp}
-q
-trace
-info
-ldebug
-lace32
-lrdd.lib
-lrddads
-lbmdbfcdx
-ldbf
Try with '-xhb' (instead of '-xhp')
Viktor
On 2010 May 4, at 17:26, Massimo Belgrano wrote:
> thanks for tips, sorry but i have an xharbour setting not updated like
> harbour one
>
> now Compilation will start but have also a problem that will be due to my
> conversion from hbmake to hbmk2 us
>> hbmk2's goal is to build executables from xhb sources
>> using xhb compiler and regular C compiler tools.
>> Configuration should be done just as for Harbour.
>> hbmk2's goal is not to emulate the full build and
>> make infrastructure of xhb.
>>
>> BTW, my advice repeated now about 3 hundred
thanks for tips, sorry but i have an xharbour setting not updated like
harbour one
now Compilation will start but have also a problem that will be due to my
conversion from hbmake to hbmk2 using
G:\CLIP52\LAVORI\MASSIMO\ARCA>
hbmk2.exe g:\clip52\lavori\massimo\arca\arcahd.hbp -xhp -rebuild
-
Viktor Szakáts wrote:
>
>> set HB_INSTALL_PREFIX=c:\xharbour\
>> hbmk2.exe myhbp.hbp -xhp
>> hbmk2: Processing environment options: -mt -compiler=bcc32
>> hbmk2: Error: Compiler value unknown: bcc32
>
> 'bcc32' has been changed to 'bcc' at least a year ago
> in Harbour.
>
> hbmk2's goal is to
On 2010 May 4, at 15:29, Massimo Belgrano wrote:
> set HB_INSTALL_PREFIX=c:\xharbour\
> hbmk2.exe myhbp.hbp -xhp
> hbmk2: Processing environment options: -mt -compiler=bcc32
> hbmk2: Error: Compiler value unknown: bcc32
'bcc32' has been changed to 'bcc' at least a year ago
in Harbour.
hbmk2's
set HB_INSTALL_PREFIX=c:\xharbour\
hbmk2.exe myhbp.hbp -xhp
hbmk2: Processing environment options: -mt -compiler=bcc32
hbmk2: Error: Compiler value unknown: bcc32
2010/5/4 Viktor Szakáts
>
> There is a quite large code portion dealing with
> this issue, I suggest to explore the source code
> of
> How hbmk2 detect the harbour tree and c compiler / linker tree?
There is a quite large code portion dealing with
this issue, I suggest to explore the source code
of hbmk2.
> -xhp will be also a line in hbp?
No. It's command line only.
Viktor
___
How hbmk2 detect the harbour tree and c compiler / linker tree?
-xhp will be also a line in hbp?
2010/5/4 Viktor Szakáts
>
> It should be enough to add '-xhb' option to hbmk2 cmdline
> to switch to xhb mode.
>
> Viktor
>
> --
Massimo Belgrano
___
Harbo
> Have you a timeline for
> hbide version compatible with xharbour
It should be enough to add '-xhb' option to hbmk2 cmdline
to switch to xhb mode.
Viktor
___
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists
This can be a good news
I received many request about it so i plan update my blog with your version
http://harbourlanguage.blogspot.com/
2010/5/4 Pritpal Bedi
>
>
> Massimo Belgrano wrote:
> >
> > Have you a timeline for
> > hbide version compatible with xharbour
> > hbide widard for easy proje
Massimo Belgrano wrote:
>
> Have you a timeline for
> hbide version compatible with xharbour
> hbide widard for easy project creating
>
Probably yes.
By the end of next week.
-
enjoy hbIDEing...
Pritpal Bedi
http://hbide.vouch.info/
--
View this message in context:
http:/
Have you a timeline for
hbide version compatible with xharbour
hbide widard for easy project creating
> > Can i past errorlog copying from clipboard or file?
> >
>
> It can be implemented. With next commit.
>
>
--
Massimo Belgrano
___
Harbour mailing l
Massimo Belgrano wrote:
>
> right click on editor tab
> Error base/1076 argument error. >=
> called from xbptabwidget:execslot()
> called from (b)xbptabwidget_create
> called from qt_eventloop_processevents()
> called from qeventloop:processevents()
> called from appevent()
> called from hbide_c
22 matches
Mail list logo
