Maybe this works in the MinGW shell environment,
but I tried it only once so far (in non-Harbour context),
so I'm highly unfamiliar with it.
Just click on MSys icon and then make:
cd <harbour_dir>
./make_gnu.sh
Okay it's now running. Pretty smoothly actually.
[ Only make_gnu.sh clean took quite a while to finish,
caused by some 'find' command on my whole harbour dir.
I wonder what is the purpose of this. ]
Overall, I think I'm leaving this topic for now, and we
will revisit it in a next revision. It's not a critical
issue after all.
Anyhow it will be good to check if MinGW is MSVC compatible.
If not then I do not see any reason to force MinGW and GNUC
users to use MSVC for creating official harbour.dll.
Please remember that GCC based binaries are most portable
between systems (in fact they can be created on all supported
by us systems) with support for cross builds and MSVC is compiler
which can be used only for very limited number of platforms.
If sth should be considered as official windows shared library
format then IMHO it should be compatible with MinGW harbour.dll.
Surely, it would be better. I believe all compilers should
be able to produce a compatible .dll.
Okay, I've now built Harbour using make_gnu.sh, I don't know
how a shared lib looks like, but there are surely not any
harbour*.dll created. hb-mkslib.sh needs parameters, but
I don't know what exactly?
How should I continue now?
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
