We have about this as batch files (not perfect,
but convenient enough for Harbour development).
Everything else can be developed, all it takes
is someone interested enough to do it.
Will remain a bath but without bld_b32,bld_os2,bld_vc
If Hb_compiler=bcc32
Bld_b32
If Hb_compiler=vc
Bld_b32
Endif
The advantage is that is possible describe how compile a sample
This is exactly how it works now (and since about 9 years :)
bld.bat is the "central" file, all the rest are just files
for convenience, which does nothing more than setting
the platform and compiler type for you. Please look into
bld_b32.bat, or bld_vc.bat (any of them inside the
Harbour source tree, but start with the one in /bin).
Will bld.bat copied in c:\harbour\bin\b32 where I have path?
It won't, as this dir is an temporary place, not
a final destination. 'make_*.bat install' is copying
the binaries to final destination, which you can freely
specify, or - if you don't - this will be /lib, /bin.
I suggest only have a binary build for bin\b32\hbbld.bat istead
bin\bld_b32.bat, bin\vc\hbbld.bat instead bin\bld_vc.bat ecc.
hbbld.bat is called bld.bat. And no, nothing shall be put
inside bin\b32\ since this is reserved for temp file storage
during the non-GNU BCC build process.
Will bld.bat revritten as prg be a based for hbmk,hblin,hbcc ?
As far as I'm concerned: no.
If anything, I'd rather reduce the number of make
systems used in Harbour, than adding new ones.
hbmake is still a good candidate for a replacement, hough.
Reducing the number of make system is a very good idea
Having same syntax for different platform / c compiler
Yes, hbmake was built with that purpose, but it's broken.
Notice there are two almost independent problems here:
1) Building Harbour (and parts).
Currently: make*.bat, *.cmd, *.sh
2) Building apps using Harbour (and parts).
Currently: bld*.bat, *.cmd, *.sh + hb??? scripts for *nix.
+ hbmake for all platforms, but broken.
If those hb??? scripts could somehow be converted or
extended to give a multiplatform solution, it'd be great and
hbmake would no longer be needed.
One good step towards aiding Harbour developers on a larger
scale, is Lorenzo's suggestion for the dependency parser.
This would be a useful addition, I'd personally make it a
separate tool from the compiler though.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour