From: Simon Ronald <simon@ro...> - 2004-06-16 06:29:48
I'm trying to migrate our application written with owl to MS VCC+
Microsoft Net Development Environment 2003.
I installed the 604 ownext libraries and patched them with owl604p19.exe
I was wondering :
a) I ran the program msc7owl.bat and it generated a couple of dll files
:- I was wondering does anyone know how to build static link .lib files
instead of dlls?
b) Also when i build the dll files, by running the msc7owl.bat file, it
didn't seem to make and link in the global.cpp and main.cpp files :-
these are needed by owl when I compile my main program as they define
gModule and the call to the OwlMain function that also sets up the
gModule global :- am I doing something wrong in the creation of the
DLL? Is there some flag or extra action I need to take to include
these two .cpp into the final build?
c) when building the DLLs I noticed that it didn't copy the import libs
into the bin directory :- I had to fish the import lib out of the $dll.w
temporary directory _owl.lib and rename it and copy them to the bin
directory. I trust this is correct procedure?
d) if anyone has driven the static lib route before, if you might kindly
email me the owl static built libs for vc7, multi threaded, debug & non
debug versions, that would be much appreciated
e) has anyone had experience in mingling MFC with OWL :- what is the
best way to do it :- what are the gotchas :- does the OWL have to go
into a DLL for this or can it be statically linked :- anyone have a
simple sample program with the two intermixed?
help much appreciated!
Creative Windoware Pty Ltd
1st Floor, 128 Hindley Street, Adelaide, SA, Australia, 5000
GPO Box 944, Adelaide SA 5001
Mobile: 0415 467 357 (Australia)
Ph: +61 8 8415 5121 (International)
Fax: (877) 731 4410 (USA Toll Free)