Re: Compiling LS modules with DEV-C++
"Brian Wolven" <[email protected]> Mon, 17 Nov 2003 20:29:54 -0500
| Newsgroups | gmane.comp.windows.shell-shocked.devel |
|---|---|
| Message-ID | <000701c3ad73$7895bfb0$0300a8c0@DD85GV11> |
A. Klingenstein wrote: > Brian Wolven wrote: >> which generates errors like this: >> >> [Linker error] undefined reference to `[email protected]' > > -lwinmm in Project Options (alt-p), Parameters, Linker should do the > trick. The function is in libwinmm.a Many thanks. It'd take me forever to figure that out on my own. >> void BangWinMove(HWND hCaller, LPCSTR pszArgs) >> >> this line generates errors: >> >> else if (strstr(strlwr(pszArgs),"centered")) >> >> unless it is changed to this: >> >> else if (strstr(strlwr((char *)pszArgs),"centered")) >> >> Is there a set of string functions/typedefs that should be used now >> for safety, consistency, and to conform to the current LS core code? >> Some of thi s source code is kind of old... > > strsafe.h is what the core itself uses. It compiles/works with mingw > just fine, but you can only get it from the platform sdk. just drop > the strsafe.h in your Dev-C++ include file directory and #include it. > You > won't be able to use normal C functions like strcpy, strcat, etc > anymore. strsafe.h provides (different) alternatives. The main > advantage > of them is that buffer overruns are (almost) impossible. Cool - I think I'll download the psdk at work though. Fatter pipe there. >> Ahhh - one last thing - anyone know how to minimize the size of the >> DLL's created by dev-c++? Even with full optimization and no >> debugging they are running 113 kBytes. > > Not really :( > There are a few things you can do, but they will always be bigger than > MSVC generated ones, unfortunately. Using a newer mingw version > usually > helps a bit. removing debugging symbols (use "strip.exe" on the DLL) I stumbled across that in the dev-c++ bin directory - that cut things down to 63 KB or so. That'll do. > PS: no, vi doesn't work inside Dev-C++. But Dev-C++ creates standard > Makefiles: projectname.mak > You can always use vim + make to do compiling if you wish. That sounds like a winner - thanks again. I've managed to successfully graft one new bang command onto winctrl so far. =) __________________________________________________ Subscription options and archive: http://www.freelists.org/list/shell-coding