For reference, here is my posted solution which "plugs into"
current HMG distro:
[ NOTE: the batch file is only needed to keep current "feel"
of the distro, the .hbc could be places in any standard place
instead and let it be automatically or manually picked. ]
--- BATCH\hbmk2.bat
@set PATH=%~dp0..\MINGW\bin
@"%~dp0..\HARBOUR\bin\hbmk2.exe" "%~dp0hmg.hbc" %*
---
--- BATCH\hmg.hbc
#
# $Id$
#
# Usage:
# > hbmk2 test.prg C:\hmg\HARBOUR\bin\hmg.hbc
{win}incpaths=..\include
{win}libpaths=..\lib
# The "tricky" bits
{win}sources=${hb_curdir}*.rc
{win}sources=..\resources\minigui.rc
{win}gt=gtgui
# core
{win}libs=minigui
# core #2
{win}libs=gui
{win}libs=dll
# contribs
{win}libs=crypt edit editex graph ini report
# Harbour contribs
{win}libs=hbmzip
{win}libs=hbwin
# system
{win}libs=vfw32
---
Brgds,
Viktor
On 2009 Oct 12, at 16:28, Roberto Lopez wrote:
Przemyslaw Czerpak wrote:
> My personal experience is that the most often the sources of user
problems
are wrongly synced with Harbour core code build scripts in
different add
on libraries.
<...>
I respect you and your work a lot (the same as Viktor).
Is not my intention to disturb you and the list with this.
The only thing that I have to say is that I have a different POV
about that.
Regarding problems with HMBK2 there is various, maybe I post a
detailed report when I finish the tests.
Regards,
Roberto.
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
