search for: shmmap

Displaying 3 results from an estimated 3 matches for "shmmap".

Did you mean: shmmax
2001 Oct 08
1
win32sdk shared memory issue
...the Ogg Vorbis libraries built from the win32sdk in winlame. Since the rc2 DLL's are not functioning, I compiled them by myself. The apparent reason is that some data arrays like _residue_P were not shared among DLLs. I looked at the code, and found that IMHO dirty hack in vorbis/win32/src/shmmap*.h that maps the data arrays. Why not placing the data arrays in shared segments? http://support.microsoft.com/support/kb/articles/Q100/6/34.ASP is a good description how to achieve that. Just some #pragma's that could go into #if defined(_MSC_VER) sections. bye Michael -- michael.fink@a...
2001 Sep 10
1
new DLL additions in core libs
Chris, re the DLL additions: In a word, *no*. That much Win32 specific code does not belong in a lib that's pure math and totally platform agnostic. It may be appropriate, assuming it's necessary, to add this in the win32 specific SDKs, but it has no business in the core libvorbis. Please move it out to a more appropriate place as soon as you possibly can. Secondly: I'd like to
2001 Oct 17
2
win32sdk shared memory issue -- proposed change of code
...on file, or explicitly via _cdeclspec(dllexport) -- unlike procedures (functions), it is mandatory for a DLL client to access that variable via _cdeclspec(dllimport). It is unnecessary to allocate dynamic memory and then copy pointers to that allocated memory, as is done with the vorbis/win32/src/shmmap.h and vorbis/win32/src/shmmap_c.h stuff. In otherwords, we've come full circle -- it looks like the linking paradigm in Windows is closer to what would be expected when developing under UNIX, after all... ...well -- almost, as mentioned, the "_cdeclspec(dllimport)" attribute is re...