Hi Przemek and all,
So, to give a short list of Windows .dll problems:
- 'sed' command line error.
- harbour*.dll naming in non-GNU make system.
- harbour.dll install location doesn't match in GNU ('lib') and non-
GNU ('bin') builds.
- harbour.dll content doesn't match in GNU and non-GNU (missing
hbcplr) builds.
- harbour.dll generated with BCC isn't compatible with MSVS and MinGW
ones (due to added leading underscore in BCC).
- Minor: Generation of harbour.dll using the GNU-make system under
Windows,
needs full msys shell support. Maybe it would be better to include
this
process in the GNU-make system itself (if possible at all).
- MinGW generated shared-lib .exe is not compatible with MSVS generated
harbour.dll. (missing '[EMAIL PROTECTED]' entry)
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
