ciderpress/nufxlib/nufxlib.def

; NufxLib library exported symbols
;
; This is redundant with the __declspec(dllexport) declarations enabled
; with the NUFXLIB_EXPORTS symbol.  If we're just building a DLL, there's
; no need for this file.  However, the objects we're building are used for
; both the static library and the dynamic library, and we don't want to
; have exports in the static library.  If we do, the linker will create
; .lib and .exp files for every executable we link against it.  This is
; mostly harmless, but a tad messy.  I don't expect the interface to change,
; so there's not much of a maintenance burden here.
;
EXPORTS
    NuAbort
    NuAddFile
    NuAddRecord
    NuAddThread
    NuClose
    NuContents
    NuCreateDataSinkForBuffer
    NuCreateDataSinkForFP
    NuCreateDataSinkForFile
    NuCreateDataSourceForBuffer
    NuCreateDataSourceForFP
    NuCreateDataSourceForFile
    NuDataSinkGetOutCount
    NuDataSourceSetRawCrc
    NuDebugDumpArchive
    NuDelete
    NuDeleteRecord
    NuDeleteThread
    NuExtract
    NuExtractRecord
    NuExtractThread
    NuFlush
    NuFreeDataSink
    NuFreeDataSource
    NuGetAttr
    NuGetExtraData
    NuGetMasterHeader
    NuGetRecord
    NuGetRecordIdxByName
    NuGetRecordIdxByPosition
    NuGetValue
    NuGetVersion
    NuIsPresizedThreadID
    NuOpenRO
    NuOpenRW
    NuRecordCopyAttr
    NuRecordCopyThreads
    NuRecordGetNumThreads
    NuRename
    NuSetErrorHandler
    NuSetErrorMessageHandler
    NuSetExtraData
    NuSetGlobalErrorMessageHandler
    NuSetOutputPathnameFilter
    NuSetProgressUpdater
    NuSetRecordAttr
    NuSetSelectionFilter
    NuSetValue
    NuStrError
    NuStreamOpenRO
    NuTest
    NuTestFeature
    NuTestRecord
    NuThreadGetByIdx
    NuUpdatePresizedThread
Large set of changes to restore CiderPress build. CiderPress and MDC now compile, and execute far enough to open their respective "about" boxes, but I doubt they'll do much more than that. * Switch from MBCS to UNICODE APIs Microsoft switched to UTF-16 (by way of UCS-2) a long time ago, and the support for MBCS seems to be getting phased out. So it's time to switch to wide strings. This is a bit awkward for CiderPress because it works with disk and file archives with 8-bit filenames, and I want NufxLib and DiskImgLib to continue to work on Linux (which has largely taken the UTF-8 approach to Unicode). The libraries will continue to work with 8-bit filenames, with CiderPress/MDC doing the conversion at the appropriate point. There were a couple of places where strings from a structure handed back by one of the libraries were used directly in the UI, or vice-versa, which is a problem because we have nowhere to store the result of the conversion. These currently have fixed place-holder "xyzzy" strings. All UI strings are now wide. Various format strings now use "%ls" and "%hs" to explicitly specify wide and narrow. This doesn't play well with gcc, so only the Windows-specific parts use those. * Various updates to vcxproj files The project-file conversion had some cruft that is now largely gone. The build now has a common output directory for the EXEs and libraries, avoiding the old post-build copy steps. * Added zlib 1.2.8 and nufxlib 2.2.2 source snapshots The old "prebuilts" directory is now gone. The libraries are now built as part of building the apps. I added a minimal set of files for zlib, and a full set for nufxlib. The Linux-specific nufxlib goodies are included for the benefit of the Linux utilities, which are currently broken (don't build). * Replace symbols used for include guards Symbols with a leading "__" are reserved. 2014-11-10 23:32:55 +00:00			`; NufxLib library exported symbols`
			`;`
			`; This is redundant with the __declspec(dllexport) declarations enabled`
			`; with the NUFXLIB_EXPORTS symbol. If we're just building a DLL, there's`
			`; no need for this file. However, the objects we're building are used for`
			`; both the static library and the dynamic library, and we don't want to`
			`; have exports in the static library. If we do, the linker will create`
			`; .lib and .exp files for every executable we link against it. This is`
			`; mostly harmless, but a tad messy. I don't expect the interface to change,`
			`; so there's not much of a maintenance burden here.`
			`;`
			`EXPORTS`
			`NuAbort`
			`NuAddFile`
			`NuAddRecord`
			`NuAddThread`
			`NuClose`
			`NuContents`
			`NuCreateDataSinkForBuffer`
			`NuCreateDataSinkForFP`
			`NuCreateDataSinkForFile`
			`NuCreateDataSourceForBuffer`
			`NuCreateDataSourceForFP`
			`NuCreateDataSourceForFile`
			`NuDataSinkGetOutCount`
			`NuDataSourceSetRawCrc`
			`NuDebugDumpArchive`
			`NuDelete`
			`NuDeleteRecord`
			`NuDeleteThread`
			`NuExtract`
			`NuExtractRecord`
			`NuExtractThread`
			`NuFlush`
			`NuFreeDataSink`
			`NuFreeDataSource`
			`NuGetAttr`
			`NuGetExtraData`
			`NuGetMasterHeader`
			`NuGetRecord`
			`NuGetRecordIdxByName`
			`NuGetRecordIdxByPosition`
			`NuGetValue`
			`NuGetVersion`
			`NuIsPresizedThreadID`
			`NuOpenRO`
			`NuOpenRW`
			`NuRecordCopyAttr`
			`NuRecordCopyThreads`
			`NuRecordGetNumThreads`
			`NuRename`
			`NuSetErrorHandler`
			`NuSetErrorMessageHandler`
			`NuSetExtraData`
			`NuSetGlobalErrorMessageHandler`
			`NuSetOutputPathnameFilter`
			`NuSetProgressUpdater`
			`NuSetRecordAttr`
			`NuSetSelectionFilter`
			`NuSetValue`
			`NuStrError`
			`NuStreamOpenRO`
			`NuTest`
			`NuTestFeature`
			`NuTestRecord`
			`NuThreadGetByIdx`
			`NuUpdatePresizedThread`