www.FiveTechSoft.com
https://forums.fivetechsupport.com/
Please don't upload xHarbour builds to non-official websites. Always provide the official link:karinha wrote:Mister Rao:
Downloads:
BCC77:
https://mega.nz/file/gIskAIjL#vB-TuQAnx ... oIeJSEVIVk
XHBBCC77:
https://mega.nz/file/MIcQ0ZyQ#crdlVE-I0 ... Gtw3jj4lys
Mira los *.CFGs
Gracias, thanks.
Regards, saludos.
I agree. In the meantime, I'm experimenting. Please note that I always used FWH with any versions of BCC without problems. I found a problem in your compile batch and I'm trying to understand it.nageswaragunupudi wrote:Mr. João
Thanks.
For now, I prefer to use bcc & xHarbour versions used by FWH for building FWH libraries.
I wait till Mr. Antonio takes a decision to use the new versions.
Enrico, these are my backup copies; It's my file cloud. I took it from where you indicated and modified it to work perfectly.Enrico Maria Giordano wrote:Please don't upload xHarbour builds to non-official websites. Always provide the official link:karinha wrote:Mister Rao:
Downloads:
BCC77:
https://mega.nz/file/gIskAIjL#vB-TuQAnx ... oIeJSEVIVk
XHBBCC77:
https://mega.nz/file/MIcQ0ZyQ#crdlVE-I0 ... Gtw3jj4lys
Mira los *.CFGs
Gracias, thanks.
Regards, saludos.
http://xharbour.org/index.asp?page=down ... naries_win
No hay problema, Maestro Nages. El Maestro Antonio definitivamente lo usará. A menos que prefiera quedarse congelado en el tiempo. Lo correcto es siempre modernizarse. ¿o no?nageswaragunupudi wrote:Mr. João
Thanks.
For now, I prefer to use bcc & xHarbour versions used by FWH for building FWH libraries.
I wait till Mr. Antonio takes a decision to use the new versions.
What are your modifications? Can you share them? Anyway, the current xHarbour builds don't need any modifications. They work fine as they are now.karinha wrote:Enrico, these are my backup copies; It's my file cloud. I took it from where you indicated and modified it to work perfectly.
I found the problem! Please, try this change in the compile batch (buildx.bat):Enrico Maria Giordano wrote:I agree. In the meantime, I'm experimenting. Please note that I always used FWH with any versions of BCC without problems. I found a problem in your compile batch and I'm trying to understand it.
Code: Select all | Expand
echo -L%bcdir%\lib;%bcdir%\lib\psdk + > b32.bc
echo c0w32.obj + >> b32.bcEnrico, I've always done it this way. I prefer it this way, because I know it works perfectly.Enrico Maria Giordano wrote:Joao, I reviewed your ilink32.cfg. It is not good because you have to modify it every time you want to move BCC to another folder. That's why I prefet to put the lib paths in the compile batch so it manages them automatically.
Code: Select all | Expand
L 1 C 1 Ins Indent c:\bcc77\bin\ilink32.cfg
-Gn
-Lc:\bcc77\lib;c:\bcc77\lib\psdk
-aa
-x
Enrico:Enrico Maria Giordano wrote:Try to move BCC in a different directory. You will have to change the paths in the compile batch AND in the CFG file. Otherwise, if you put -L switch in the compile batch you have to change the paths only there and you can forget the CFG.
Code: Select all | Expand
Pasta de c:\
03/04/2023 15:21 <DIR> BCC55
21/08/2023 12:10 <DIR> BCC551
16/06/2023 17:19 <DIR> BCC551_OLD
16/06/2023 17:20 <DIR> BCC582
26/05/2012 11:44 <DIR> BCC582_old
31/12/2006 23:06 <DIR> BCC68
31/12/2006 23:09 <DIR> bcc69
20/05/2017 10:56 <DIR> bcc7
27/04/2023 09:45 <DIR> bcc72
15/09/2023 16:57 <DIR> BCC74
16/11/2023 09:41 <DIR> BCC76
22/11/2023 12:13 <DIR> BCC77