Windows 32-bit DLLs with Harbour Code - Any More Progress
Posted: Wed Jun 18, 2008 4:25 pm
Hello,
FWH8.05/BCC5.5 is now my development environment.
I have read the posts on creating a self contained DLL in Harbour that can be called from other programming platforms.
It seems that the one called level 1 (maindll.c Windows self-contained DLL entry point) would be the easiest to implement ... but may be limited to one parameter being passed.
Has any one successfully implemented a DLL function call from another programming language to a function defined in Harbour within the Windows environment. If so, would you be kind enough to share your approach.
I am new to Harbour (I've got a FiveWin++ background) and so would like a little "kick in the right direction".
My application that I would like to port over is written in FW++/Alaska XBase++/c/c++. I use c/c++ to increase performance when calculating crc's, string manipulations and querying hardware for status.
Any guidance would be appreciated.
Thank you
Angelo C
FWH8.05/BCC5.5 is now my development environment.
I have read the posts on creating a self contained DLL in Harbour that can be called from other programming platforms.
It seems that the one called level 1 (maindll.c Windows self-contained DLL entry point) would be the easiest to implement ... but may be limited to one parameter being passed.
Has any one successfully implemented a DLL function call from another programming language to a function defined in Harbour within the Windows environment. If so, would you be kind enough to share your approach.
I am new to Harbour (I've got a FiveWin++ background) and so would like a little "kick in the right direction".
My application that I would like to port over is written in FW++/Alaska XBase++/c/c++. I use c/c++ to increase performance when calculating crc's, string manipulations and querying hardware for status.
Any guidance would be appreciated.
Thank you
Angelo C