kJams Wiki - User contributions [en]

https://karaoke.kjams.com/w/api.php?action=feedcontributions&feedformat=atom&user=Guberif kJams Wiki - User contributions [en] 2026-06-09T06:35:26Z User contributions MediaWiki 1.43.0 https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4928 CFLite old 2009-01-03T20:22:04Z

<p>Guberif: changed mailto information to display name and email address</p> <hr /> <div>This page documents how to build CFLite 476.13 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> '''Huge credit''' for this project goes to '''[mailto:benjamin.coder.smith@gmail.com Ben Smith]'''. This guy knows what he's doing and is well worth hiring. Here is the [http://www.rentacoder.com/RentACoder/misc/BidRequests/ShowBidRequest.asp?lngBidRequestId=939947 original project page].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * First, install the built binary by following [[Code/CFLite|The "Easy" Way instructions]].<br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13].<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * Download [http://kjams.com/cflite/downloads/patch_and_flsl.zip patch_and_flsl.zip] (contains the patcher and the flsl.c file)<br /> * Install [[CFLite/Cygwin|Cygwin]]. Follow the link for detailed instructions.<br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CFLite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere simple. It will unzip into a folder called "CF-476.13".<br /> ** Open the "CF-476.13" directory. From now on i'll just call this "the CFLite folder".<br /> ** Delete the following files: The patch does not yet cover these source files and their contained features. The build process for CFLite is... unique, you'll want to move or remove these files. (A suitable Makefile would be superior)<br /> CFConcreteStreams.c<br /> CFMachPort.c<br /> CFMessagePort.c<br /> CFPlugIn_Instance.c<br /> CFRunLoop.c<br /> CFRunLoopPriv.h<br /> CFSocket.c<br /> CFSocketStream.c<br /> CFStream.c<br /> CFStringDefaultEncoding.h<br /> CFUserNotification.c<br /> CFVersion.c<br /> CFWindowsMessageQueue.c<br /> CFWindowsMessageQueue.h<br /> ** You may also delete these files, as they are already installed (from step 1):<br /> CFCharacterSetBitmaps.bitmap<br /> CFUniCharPropertyDatabase.data<br /> CFUnicodeData-B.mapping<br /> CFUnicodeData-L.mapping<br /> ** Unzip '''patch_and_flsl.zip''' and place it's 2 files into your CFLite folder. This will place your patcher and the flsl.c file both in that directory. Note that flsl is a locked file (at leat on my mac) so unlock it before applying the patch.<br /> ** Unzip '''Include.zip''' into your CFLite folder (it will be in it's own folder)<br /> ** Unzip the '''ICU4C''' package into the Include folder that was just created. It should extract into a folder called '''icu'''.<br /> <br /> Your include folder should look like this when you're finished. (Ignore the fact that the path does not contain the word "CF-476.13", yours should)<br><br /> http://kjams.com/cflite/screenshots/cfbuild_include_folder_screenshot.png<br /> <br /> * at your Cygwin command prompt, navigate IN to your CFLite folder (so you're seeing it's contents)<br /> ** Note: Cygwin will execute regular dos commands like dir, copy, del, or you can use their unix equivalents ls, cp, rm. Change directories with the cd command.<br /> ** Note: Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. For example; /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> * Apply the patch. The patch is against CFLite '''476.13'', patching will fail with any other version.<br /> ** Use this patch command from inside the CFLite directory. Note that is a "Number One" after the '''-p''', it is not a "Letter Ell".<br /> patch -p1 < cf_windows.patch<br /> * Note: open CFUtilities and search for <br /> fprintf(CFGetLogFile(), NULL, "%04d...<br /> and change it to (just remove the "NULL, "):<br /> fprintf(CFGetLogFile(), "%04d...<br /> * Now make the binary<br /> make 2>error_log.txt<br /> ** There are a lot of warnings.<br /> ** Your built .dll and .lib files will be installed into your \WINDOWS\CoreFoundation\ directory after being built.<br /> ** Your modified CF headers will be copied into \WINDOWS\CoreFoundation\CoreFoundation\ automatically as well<br /> <br /> * Using CFLite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> ** Visual Studio 2005<br /> *** You followed the original instructions for "the easy way" right?<br /> ** CodeWarrior<br /> *** add the dll to your project<br /> *** add the 2 include paths<br /> *** you can't use the functions "CFAbsoluteTimeGetGregorianDate" and "CFAbsoluteTimeGetDifferenceAsGregorianUnits" because they return structs. Instead, use "CFAbsoluteTimeGetGregorianDate_MW" and "CFAbsoluteTimeGetDifferenceAsGregorianUnits_MW" respectively. See CFTest (below) for an example.<br /> <br /> * Download the [http://kjams.com/cflite/downloads/CFTest.zip CFTest] source files. This is the test harness sample project and includes some extremely high win factor utilities<br /> ** open it up and go to the "win_vs" folder for Visual Studio project, or "win_cw" for the CodeWarrior project<br /> ** the "console.txt" is the example output that it '''should''' look like in your console or log file</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4672 CFLite old 2008-08-13T09:40:15Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13].<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file. [http://kjams.com/cflite/downloads/flsl.c Here] is a local copy.<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * You will need the contents of include/mach/ and include/i386/, and the files include/malloc/malloc.h, include/sys/cdefs.h, include/AssertMacros.h, include/AvailabilityMacros.h, and include/TargetConditionals.h from include.zip<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]]. Follow the link for detailed instructions.<br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere simple.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** The patch does not yet cover the following source files and their contained features. The build process for CF-Lite is... unique, you'll want to move or remove these files. A suitable Makefile would be superior.<br /> *** CFConcreteStreams.c<br /> *** CFMachPort.c<br /> *** CFMessagePort.c<br /> *** CFPlugIn_Instance.c<br /> *** CFRunLoop.c<br /> *** CFRunLoopPriv.h<br /> *** CFSocket.c<br /> *** CFSocketStream.c<br /> *** CFStream.c<br /> *** CFStringDefaultEncoding.h<br /> *** CFUserNotification.c<br /> *** CFVersion.c<br /> *** CFWindowsMessageQueue.c<br /> *** CFWindowsMessageQueue.h<br /> ** Create a folder in your windows directory named CoreFoundation. Under it, make a new folder named CoreFoundation.resources. Under that one, create one called CharacterSets. You should now have the path \WINDOWS\CoreFoundation\CoreFoundation.resources\CharacterSets.<br /> ** Move the files CFCharacterSetBitmaps.bitmap, CFUniCharPropertyDatabase.data, CFUnicodeData-B.mapping, CFUnicodeData-L.mapping into the new CharacterSets folder.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Create a folder named malloc. Copy include.zip's include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy include.zip's include/sys/cdefs.h into it.<br /> ** Copy include.zip's include/AvailabilityMacros.h, include/AssertMacros.h, and include/TargetConditionals.h files and the include/mach and include/i386 folders into your include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> <br /> <br /> Your include folder should look like this when you're finished.<br>http://kjams.com/cflite/screenshots/cfbuild_include_folder_screenshot.png<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin will execute regular dos commands like dir, copy, del, or you can use their unix equivalents ls, cp, rm. Change directories with the cd command.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. For example; /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply [http://kjams.com/cflite/downloads/cf_windows.patch the patch]. The patch is against CFLite-476.13, patching will fail with CFLite-476.10.<br /> ** Use the command 'patch -p1 < cf_windows.patch' from inside the CF-Lite directory.<br /> <br /> <br /> * Run make. Just type make and press enter.<br /> ** There are a lot of warnings.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> ** Your .dll and .lib files will be in your current directory. The directory include/CoreFoundation/ will contain the Core Foundation headers that you use for other programs. <br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions because Visual Studio didn't load the object code for that particular module.<br /> *** CoreFoundation relies on the stdint.h and stdbool.h files, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard. You'll need to put them on your include path. I placed mine in my compiler's include folder because they help support C99 and don't interfere with my compiler workings. Since they are freely redistributable, [http://kjams.com/cflite/downloads/stdint.h stdint.h] and [http://kjams.com/cflite/downloads/stdbool.h stdbool.h] can be had locally as well.<br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> <br /> * Source code changes for CFTest.exe<br /> ** CFTest.exe looks for the "test.xml" Chiquitita.xml file in its parent directory.<br /> <br /> * CFUtils.cpp lines 112 and 115 in the function Read_PList should use CFSTR() for the text in the call to CCFLog or CFTest.exe crashes when the xml file can't be read or if it doesn't parse correctly.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4671 CFLite old 2008-08-13T07:24:56Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13].<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file. [http://kjams.com/cflite/downloads/flsl.c Here] is a local copy.<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * You will need the contents of include/mach/ and include/i386/, and the files include/malloc/malloc.h, include/sys/cdefs.h, include/AssertMacros.h, include/AvailabilityMacros.h, and include/TargetConditionals.h from include.zip<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]]. Follow the link for detailed instructions.<br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere simple.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** The patch does not yet cover the following source files and their contained features. The build process for CF-Lite is... unique, you'll want to move or remove these files. A suitable Makefile would be superior.<br /> *** CFConcreteStreams.c<br /> *** CFMachPort.c<br /> *** CFMessagePort.c<br /> *** CFPlugIn_Instance.c<br /> *** CFRunLoop.c<br /> *** CFRunLoopPriv.h<br /> *** CFSocket.c<br /> *** CFSocketStream.c<br /> *** CFStream.c<br /> *** CFStringDefaultEncoding.h<br /> *** CFUserNotification.c<br /> *** CFVersion.c<br /> *** CFWindowsMessageQueue.c<br /> *** CFWindowsMessageQueue.h<br /> ** Create a folder in your windows directory named CoreFoundation. Under it, make a new folder named CoreFoundation.resources. Under that one, create one called CharacterSets. You should now have the path \WINDOWS\CoreFoundation\CoreFoundation.resources\CharacterSets.<br /> ** Move the files CFCharacterSetBitmaps.bitmap, CFUniCharPropertyDatabase.data, CFUnicodeData-B.mapping, CFUnicodeData-L.mapping into the new CharacterSets folder.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Create a folder named malloc. Copy include.zip's include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy include.zip's include/sys/cdefs.h into it.<br /> ** Copy include.zip's include/AvailabilityMacros.h, include/AssertMacros.h, and include/TargetConditionals.h files and the include/mach and include/i386 folders into your include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> <br /> <br /> Your include folder should look like this when you're finished.<br>http://kjams.com/cflite/screenshots/cfbuild_include_folder_screenshot.png<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin will execute regular dos commands like dir, copy, del, or you can use their unix equivalents ls, cp, rm. Change directories with the cd command.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. For example; /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply [http://kjams.com/cflite/downloads/cf_windows.patch the patch]. The patch is against CFLite-476.13, patching will fail with CFLite-476.10.<br /> ** Use the command 'patch -p1 < cf_windows.patch' from inside the CF-Lite directory.<br /> <br /> <br /> * Run make. Just type make and press enter.<br /> ** There are a lot of warnings.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> ** Your .dll and .lib files will be in your current directory. The directory include/CoreFoundation/ will contain the Core Foundation headers that you use for other programs. <br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions because Visual Studio didn't load the object code for that particular module.<br /> *** CoreFoundation relies on the stdint.h and stdbool.h files, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard. You'll need to put them on your include path. I placed mine in my compiler's include folder because they help support C99 and don't interfere with my compiler workings. Since they are freely redistributable, [http://kjams.com/cflite/downloads/stdint.h stdint.h] and [http://kjams.com/cflite/downloads/stdbool.h stdbool.h] can be had locally as well.<br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** CFTest.exe looks for the "test.xml" Chiquitita.xml file in its parent directory.<br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite/Cygwin&diff=4670 CFLite/Cygwin 2008-08-13T06:52:51Z

<p>Guberif: </p> <hr /> <div># Run the [http://www.cygwin.com/setup.exe Cygwin Setup] installer<br>http://kjams.com/cflite/screenshots/picture%206.png<br /> # Click "Run"<br>http://kjams.com/cflite/screenshots/picture%207.png<br /> # Click "Run"<br>http://kjams.com/cflite/screenshots/picture%208.png<br /> # Click "Next"<br>http://kjams.com/cflite/screenshots/picture%209.png<br /> # Click "Next"<br>http://kjams.com/cflite/screenshots/picture%2010.png<br /> # Click "Next"<br>http://kjams.com/cflite/screenshots/picture%2011.png<br /> # Click "Next"<br>http://kjams.com/cflite/screenshots/picture%2012.png<br /> # Click "Next"<br>http://kjams.com/cflite/screenshots/picture%2013.png<br /> # pick any mirror (i like to pick http ones rather than FTP ones), then click Next<br>http://kjams.com/cflite/screenshots/cygwin_stop_here.png<br /> # I find it helpful to stretch the window out.<br>http://kjams.com/cflite/screenshots/cygwin_expanded.png<br /> # Expand the Devel branch and select these packages by clicking the text labelled Skip(pretty unintuitive, imo). The packages needed for CF-Lite are:<br /> #* diffutils<br /> #* gcc-core <br /> #* gcc-objc <br /> #* gdb, if you want to debug the dll.<br /> #* make<br /> #* patchutils<br><br>http://kjams.com/cflite/screenshots/cygwin_download.png<br /> # Click Next, cygwin will download the necessary packages from the internet and install them.<br>http://kjams.com/cflite/screenshots/cygwin_finish.png<br /> # Click Finish.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4669 CFLite old 2008-08-12T10:32:00Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13].<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * You will need the contents of include/mach/ and include/i386/, and the files include/malloc/malloc.h, include/sys/cdefs.h, include/AssertMacros.h, include/AvailabilityMacros.h, and include/TargetConditionals.h from include.zip<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]] - select (click the text labelled Skip, it will change to a package version) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** Devel/patchutils<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere simple.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** The patch does not yet cover the following source files and their contained features. The build process for CF-Lite is... unique, you'll want to move or remove these files. A suitable Makefile would be superior.<br /> *** CFConcreteStreams.c<br /> *** CFMachPort.c<br /> *** CFMessagePort.c<br /> *** CFPlugIn_Instance.c<br /> *** CFRunLoop.c<br /> *** CFRunLoopPriv.h<br /> *** CFSocket.c<br /> *** CFSocketStream.c<br /> *** CFStream.c<br /> *** CFStringDefaultEncoding.h<br /> *** CFUserNotification.c<br /> *** CFVersion.c<br /> *** CFWindowsMessageQueue.c<br /> *** CFWindowsMessageQueue.h<br /> ** Create a folder in your windows directory named CoreFoundation. Under it, make a new folder named CoreFoundation.resources. Under that one, create one called CharacterSets. You should now have the path \WINDOWS\CoreFoundation\CoreFoundation.resources\CharacterSets.<br /> ** Move the files CFCharacterSetBitmaps.bitmap, CFUniCharPropertyDatabase.data, CFUnicodeData-B.mapping, CFUnicodeData-L.mapping into the new CharacterSets folder.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Create a folder named malloc. Copy include.zip's include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy include.zip's include/sys/cdefs.h into it.<br /> ** Copy include.zip's include/AvailabilityMacros.h, include/AssertMacros.h, and include/TargetConditionals.h files and the include/mach and include/i386 folders into your include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> <br /> <br /> Your include folder should look like this when you're finished.<br /> INCLUDE_SCREENSHOT_HERE<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. For example; /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply the patch. The patch is a patch against CFLite-476.13. Where to host patch?<br /> ** Use the command 'patch -p1 < cf_windows.patch'<br /> <br /> <br /> * Run make. Just type make and press enter.<br /> ** There are a lot of warnings.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> ** Your .dll and .lib files will be in your current directory. The directory include/CoreFoundation/ will contain the Core Foundation headers that you use for other programs. <br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions because Visual Studio didn't load the object code for that particular module.<br /> *** CoreFoundation relies on the stdint.h and stdbool.h files, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard. You'll need to put them on your include path. I placed mine in my compiler's include folder because they help support C99 and don't interfere with my compiler workings.<br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4668 CFLite old 2008-08-12T10:24:41Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13].<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * You will need the contents of include/mach/ and include/i386/, and the files include/malloc/malloc.h, include/sys/cdefs.h, include/AssertMacros.h, include/AvailabilityMacros.h, and include/TargetConditionals.h from include.zip<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]] - select (click the text labelled Skip, it will change to a package version) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** Devel/patchutils<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere simple.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** The patch does not yet cover the following source files and their contained features. The build process for CF-Lite is... unique, you'll want to move or remove these files. A suitable Makefile would be superior.<br /> *** CFConcreteStreams.c<br /> *** CFMachPort.c<br /> *** CFMessagePort.c<br /> *** CFPlugIn_Instance.c<br /> *** CFRunLoop.c<br /> *** CFRunLoopPriv.h<br /> *** CFSocket.c<br /> *** CFSocketStream.c<br /> *** CFStream.c<br /> *** CFStringDefaultEncoding.h<br /> *** CFUserNotification.c<br /> *** CFVersion.c<br /> *** CFWindowsMessageQueue.c<br /> *** CFWindowsMessageQueue.h<br /> ** Create a folder in your windows directory named CoreFoundation. Under it, make a new folder named CoreFoundation.resources. Under that one, create one called CharacterSets. You should now have the path \WINDOWS\CoreFoundation\CoreFoundation.resources\CharacterSets.<br /> ** Move the files CFCharacterSetBitmaps.bitmap, CFUniCharPropertyDatabase.data, CFUnicodeData-B.mapping, CFUnicodeData-L.mapping into the new CharacterSets folder.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Create a folder named malloc. Copy include.zip's include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy include.zip's include/sys/cdefs.h into it.<br /> ** Copy include.zip's include/AvailabilityMacros.h, include/AssertMacros.h, and include/TargetConditionals.h files and the include/mach and include/i386 folders into your include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> <br /> <br /> Your include folder should look like this when you're finished.<br /> INCLUDE_SCREENSHOT_HERE<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. For example; /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply the patch. The patch is a patch against CFLite-476.13. Where to host patch?<br /> ** use the command 'patch -p1 < cf_windows.patch'<br /> <br /> <br /> * Run make. Just type make and press enter.<br /> ** There are a lot of warnings.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> ** Your .dll and .lib files will be in your current directory. The directory include/CoreFoundation/ will contain the Core Foundation headers that you use for other programs. <br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions because Visual Studio didn't load the object code for that particular module.<br /> *** CoreFoundation relies on the stdint.h and stdbool.h files, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard. You'll need to put them on your include path. I placed mine in my compiler's include folder because they help support C99 and don't interfere with my compiler workings.<br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4667 CFLite old 2008-08-12T10:23:21Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13].<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * You will need the contents of include/mach/ and include/i386/, and the files include/malloc/malloc.h, include/sys/cdefs.h, include/AssertMacros.h, include/AvailabilityMacros.h, and include/TargetConditionals.h from include.zip<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]] - select (click the text labelled Skip, it will change to a package version) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** Devel/patchutils<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere simple.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** The patch does not yet cover the following source files and their contained features. The build process for CF-Lite is... unique, you'll want to move or remove these files. A suitable Makefile would be superior.<br /> *** CFConcreteStreams.c<br /> *** CFMachPort.c<br /> *** CFMessagePort.c<br /> *** CFPlugIn_Instance.c<br /> *** CFRunLoop.c<br /> *** CFRunLoopPriv.h<br /> *** CFSocket.c<br /> *** CFSocketStream.c<br /> *** CFStream.c<br /> *** CFStringDefaultEncoding.h<br /> *** CFUserNotification.c<br /> *** CFVersion.c<br /> *** CFWindowsMessageQueue.c<br /> *** CFWindowsMessageQueue.h<br /> ** Create a folder in your windows directory named CoreFoundation. Under it, make a new folder named CoreFoundation.resources. Under that one, create one called CharacterSets. You should now have the path \WINDOWS\CoreFoundation\CoreFoundation.resources\CharacterSets.<br /> ** Move the files CFCharacterSetBitmaps.bitmap, CFUniCharPropertyDatabase.data, CFUnicodeData-B.mapping, CFUnicodeData-L.mapping into the new CharacterSets folder.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Copy the files stdint.h, and stdbool.h into this include folder.<br /> ** Create a folder named malloc. Copy XCode's /usr/include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy XCode's /usr/include/sys/cdefs.h into it.<br /> ** Copy include.zip's include/AvailabilityMacros.h, include/AssertMacros.h, and include/TargetConditionals.h files and the include/mach and include/i386 folders into your include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> <br /> <br /> Your include folder should look like this when you're finished.<br /> INCLUDE_SCREENSHOT_HERE<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. For example; /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply the patch. The patch is a patch against CFLite-476.13. Where to host patch?<br /> ** use the command 'patch -p1 < cf_windows.patch'<br /> <br /> <br /> * Run make. Just type make and press enter.<br /> ** There are a lot of warnings.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> ** Your .dll and .lib files will be in your current directory. The directory include/CoreFoundation/ will contain the Core Foundation headers that you use for other programs. <br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions because Visual Studio didn't load the object code for that particular module.<br /> *** CoreFoundation relies on the stdint.h and stdbool.h files, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard. You'll need to put them on your include path. I placed mine in my compiler's include folder because they help support C99 and don't interfere with my compiler workings.<br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4666 CFLite old 2008-08-12T10:22:50Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * You will need the contents of include/mach/ and include/i386/, and the files include/malloc/malloc.h, include/sys/cdefs.h, include/AssertMacros.h, include/AvailabilityMacros.h, and include/TargetConditionals.h from include.zip<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]] - select (click the text labelled Skip, it will change to a package version) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** Devel/patchutils<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere simple.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** The patch does not yet cover the following source files and their contained features. The build process for CF-Lite is... unique, you'll want to move or remove these files. A suitable Makefile would be superior.<br /> *** CFConcreteStreams.c<br /> *** CFMachPort.c<br /> *** CFMessagePort.c<br /> *** CFPlugIn_Instance.c<br /> *** CFRunLoop.c<br /> *** CFRunLoopPriv.h<br /> *** CFSocket.c<br /> *** CFSocketStream.c<br /> *** CFStream.c<br /> *** CFStringDefaultEncoding.h<br /> *** CFUserNotification.c<br /> *** CFVersion.c<br /> *** CFWindowsMessageQueue.c<br /> *** CFWindowsMessageQueue.h<br /> ** Create a folder in your windows directory named CoreFoundation. Under it, make a new folder named CoreFoundation.resources. Under that one, create one called CharacterSets. You should now have the path \WINDOWS\CoreFoundation\CoreFoundation.resources\CharacterSets.<br /> ** Move the files CFCharacterSetBitmaps.bitmap, CFUniCharPropertyDatabase.data, CFUnicodeData-B.mapping, CFUnicodeData-L.mapping into the new CharacterSets folder.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Copy the files stdint.h, and stdbool.h into this include folder.<br /> ** Create a folder named malloc. Copy XCode's /usr/include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy XCode's /usr/include/sys/cdefs.h into it.<br /> ** Copy include.zip's include/AvailabilityMacros.h, include/AssertMacros.h, and include/TargetConditionals.h files and the include/mach and include/i386 folders into your include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> <br /> <br /> Your include folder should look like this when you're finished.<br /> INCLUDE_SCREENSHOT_HERE<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. For example; /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply the patch. The patch is a patch against CFLite-476.13. Where to host patch?<br /> ** use the command 'patch -p1 < cf_windows.patch'<br /> <br /> <br /> * Run make. Just type make and press enter.<br /> ** There are a lot of warnings.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> ** Your .dll and .lib files will be in your current directory. The directory include/CoreFoundation/ will contain the Core Foundation headers that you use for other programs. <br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions because Visual Studio didn't load the object code for that particular module.<br /> *** CoreFoundation relies on the stdint.h and stdbool.h files, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard. You'll need to put them on your include path. I placed mine in my compiler's include folder because they help support C99 and don't interfere with my compiler workings.<br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4665 CFLite old 2008-08-12T10:20:16Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * You will need the contents of include/mach/ and include/i386/, and the files include/malloc/malloc.h, include/sys/cdefs.h, include/AssertMacros.h, include/AvailabilityMacros.h, and include/TargetConditionals.h from include.zip<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]] - select (click the text labelled Skip, it will change to a package version) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** Devel/patchutils<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere simple.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** The patch does not yet cover the following source files and their contained features. The build process for CF-Lite is... unique, you'll want to move or remove these files. A suitable Makefile would be superior.<br /> *** CFConcreteStreams.c<br /> *** CFMachPort.c<br /> *** CFMessagePort.c<br /> *** CFPlugIn_Instance.c<br /> *** CFRunLoop.c<br /> *** CFRunLoopPriv.h<br /> *** CFSocket.c<br /> *** CFSocketStream.c<br /> *** CFStream.c<br /> *** CFStringDefaultEncoding.h<br /> *** CFUserNotification.c<br /> *** CFVersion.c<br /> *** CFWindowsMessageQueue.c<br /> *** CFWindowsMessageQueue.h<br /> ** Create a folder in your windows directory named CoreFoundation. Under it, make a new folder named CoreFoundation.resources. Under that one, create one called CharacterSets. You should now have the path \WINDOWS\CoreFoundation\CoreFoundation.resources\CharacterSets.<br /> ** Move the files CFCharacterSetBitmaps.bitmap, CFUniCharPropertyDatabase.data, CFUnicodeData-B.mapping, CFUnicodeData-L.mapping into the new CharacterSets folder.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Copy the files stdint.h, and stdbool.h into this include folder.<br /> ** Create a folder named malloc. Copy XCode's /usr/include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy XCode's /usr/include/sys/cdefs.h into it.<br /> ** Copy include.zip's include/AvailabilityMacros.h, include/AssertMacros.h, and include/TargetConditionals.h files and the include/mach and include/i386 folders into your include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> <br /> <br /> Your include folder should look like this when you're finished.<br /> INCLUDE_SCREENSHOT_HERE<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. For example; /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply the patch. The patch is a patch against CFLite-476.13. Where to host patch?<br /> ** use the command patch -p1 < cf_windows.patch<br /> <br /> <br /> * Run make. Just type make and press enter.<br /> ** There are a lot of warnings.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> ** Your .dll and .lib files will be in your current directory. The directory include/CoreFoundation/ will contain the Core Foundation headers that you use for other programs. <br /> <br /> * Using CF-Lite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions because Visual Studio didn't load the object code for that particular module.<br /> *** CoreFoundation relies on the stdint.h and stdbool.h files, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard. You'll need to put them on your include path. I placed mine in my compiler's include folder because they help support C99 and don't interfere with my compiler workings.<br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4664 CFLite old 2008-08-12T07:16:17Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * If you're using Microsoft Visual Studio, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard.<br /> * You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> ** When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere easy.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** The patch does not yet cover these source files and their contained features. The build process for CF-Lite is... unique, you'll want to remove these files. A suitable Makefile would be superior.<br /> *** CFConcreteStreams.c<br /> *** CFMachPort.c<br /> *** CFMessagePort.c<br /> *** CFPlugIn_Instance.c<br /> *** CFRunLoop.c<br /> *** CFRunLoopPriv.h<br /> *** CFSocket.c<br /> *** CFSocketStream.c<br /> *** CFStream.c<br /> *** CFStringDefaultEncoding.h<br /> *** CFUserNotification.c<br /> *** CFVersion.c<br /> *** CFWindowsMessageQueue.c<br /> *** CFWindowsMessageQueue.h<br /> ** Create a folder in your windows directory named CoreFoundation. Under it, make a new folder named CoreFoundation.resources. Under that one, create one called CharacterSets. You should now have the path \WINDOWS\CoreFoundation\CoreFoundation.resources\CharacterSets.<br /> ** Move the files CFCharacterSetBitmaps.bitmap, CFUniCharPropertyDatabase.data, CFUnicodeData-B.mapping, CFUnicodeData-L.mapping into the new CharacterSets folder.<br /> <br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Copy the files stdint.h, stdbool.h, AvailabilityMacros.h, AssertMacros.h, and TargetConditionals.h into this include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> ** Create a folder named malloc. Copy XCode's /usr/include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy XCode's /usr/include/sys/cdefs.h into it.<br /> ** Copy XCode's /usr/include/mach and /usr/include/i386 folders into your include folder.<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. For example; /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply the patch. The patch is a patch against CFLite-476.13. Where to host patch?<br /> ** XXXTODO patch instructions.<br /> <br /> <br /> * Run make. Just type make.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions because Visual Studio didn't load the object code for that particular module.<br /> <br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4663 CFLite old 2008-08-12T07:15:43Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * If you're using Microsoft Visual Studio, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard.<br /> * You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> ** When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere easy.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** The patch does not yet cover these source files and their contained features. The build process for CF-Lite is... unique, you'll want to remove these files. A suitable Makefile would be superior.<br /> *** CFConcreteStreams.c<br /> *** CFMachPort.c<br /> *** CFMessagePort.c<br /> *** CFPlugIn_Instance.c<br /> *** CFRunLoop.c<br /> *** CFRunLoopPriv.h<br /> *** CFSocket.c<br /> *** CFSocketStream.c<br /> *** CFStream.c<br /> *** CFStringDefaultEncoding.h<br /> *** CFUserNotification.c<br /> *** CFVersion.c<br /> *** CFWindowsMessageQueue.c<br /> *** CFWindowsMessageQueue.h<br /> <br /> ** Create a folder in your windows directory named CoreFoundation. Under it, make a new folder named CoreFoundation.resources. Under that one, create one called CharacterSets. You should now have the path \WINDOWS\CoreFoundation\CoreFoundation.resources\CharacterSets.<br /> ** Move the files CFCharacterSetBitmaps.bitmap, CFUniCharPropertyDatabase.data, CFUnicodeData-B.mapping, CFUnicodeData-L.mapping into the new CharacterSets folder.<br /> <br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Copy the files stdint.h, stdbool.h, AvailabilityMacros.h, AssertMacros.h, and TargetConditionals.h into this include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> ** Create a folder named malloc. Copy XCode's /usr/include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy XCode's /usr/include/sys/cdefs.h into it.<br /> ** Copy XCode's /usr/include/mach and /usr/include/i386 folders into your include folder.<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. For example; /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply the patch. The patch is a patch against CFLite-476.13. Where to host patch?<br /> ** XXXTODO patch instructions.<br /> <br /> <br /> * Run make. Just type make.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions because Visual Studio didn't load the object code for that particular module.<br /> <br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4662 CFLite old 2008-08-12T05:59:58Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * If you're using Microsoft Visual Studio, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard.<br /> * You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> ** When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere easy.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** Remove the files: XXXTODO. The patch does not yet cover these source files and their contained features.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Copy the files stdint.h, stdbool.h, AvailabilityMacros.h, AssertMacros.h, and TargetConditionals.h into this include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> ** Create a folder named malloc. Copy XCode's /usr/include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy XCode's /usr/include/sys/cdefs.h into it.<br /> ** Copy XCode's /usr/include/mach and /usr/include/i386 folders into your include folder.<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. For example; /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply the patch. The patch is a patch against CFLite-476.13. Where to host patch?<br /> ** XXXTODO patch instructions.<br /> <br /> <br /> * Run make. Just type make.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions because Visual Studio didn't load the object code for that particular module.<br /> <br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4661 CFLite old 2008-08-12T05:59:00Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * If you're using Microsoft Visual Studio, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard.<br /> * You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> ** When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere easy.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** Remove the files: XXXTODO. The patch does not yet cover these source files and their contained features.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Copy the files stdint.h, stdbool.h, AvailabilityMacros.h, AssertMacros.h, and TargetConditionals.h into this include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> ** Create a folder named malloc. Copy XCode's /usr/include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy XCode's /usr/include/sys/cdefs.h into it.<br /> ** Copy XCode's /usr/include/mach and /usr/include/i386 folders into your include folder.<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. For example; /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply the patch. The patch is a patch against CFLite-476.13. Where to host patch?<br /> ** XXXTODO patch instructions.<br /> <br /> * Run make. Just type make.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions because Visual Studio didn't load the object code for that particular module.<br /> <br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4660 CFLite old 2008-08-12T05:56:32Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * If you're using Microsoft Visual Studio, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard.<br /> * You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> ** When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere easy.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** Remove the files: xyzzy . The patch does not yet cover these source files and their contained features.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Copy the files stdint.h, stdbool.h, AvailabilityMacros.h, AssertMacros.h, and TargetConditionals.h into this include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> ** Create a folder named malloc. Copy XCode's /usr/include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy XCode's /usr/include/sys/cdefs.h into it.<br /> ** Copy XCode's /usr/include/mach and /usr/include/i386 folders into your include folder.<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. For example; /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply the patch. The patch is a patch against CFLite-476.13. Where to host patch?<br /> <br /> <br /> * Run make. Just type make.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions because Visual Studio didn't load the object code for that particular module.<br /> <br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4659 CFLite old 2008-08-12T05:55:28Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * If you're using Microsoft Visual Studio, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard.<br /> * You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> ** When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere easy.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** Remove the files: xyzzy . The patch does not yet cover these source files and their contained features.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Copy the files stdint.h, stdbool.h, AvailabilityMacros.h, AssertMacros.h, and TargetConditionals.h into this include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> ** Create a folder named malloc. Copy XCode's /usr/include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy XCode's /usr/include/sys/cdefs.h into it.<br /> ** Copy XCode's /usr/include/mach and /usr/include/i386 folders into your include folder.<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. In other words, /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply the patch. The patch is a patch against CFLite-476.13. Where to host patch?<br /> <br /> <br /> * Run make. Just type make.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> <br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> <br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions because Visual Studio didn't load the object code for that particular module.<br /> <br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4658 CFLite old 2008-08-12T05:52:35Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * If you're using Microsoft Visual Studio, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard.<br /> * You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> ** When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere easy.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** Remove the files: xyzzy . The patch does not yet cover these source files and their contained features.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Copy the files stdint.h, stdbool.h, AvailabilityMacros.h, AssertMacros.h, and TargetConditionals.h into this include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> ** Create a folder named malloc. Copy XCode's /usr/include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy XCode's /usr/include/sys/cdefs.h into it.<br /> ** Copy XCode's /usr/include/mach and /usr/include/i386 folders into your include folder.<br /> <br /> <br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. In other words, /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply the patch. The patch is a patch against version 476-13. Where to host patch?<br /> <br /> <br /> * Run make. Just type make.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> <br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> <br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions.<br /> <br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4657 CFLite old 2008-08-12T05:52:14Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * If you're using Microsoft Visual Studio, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard.<br /> * You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> <br /> <br /> * Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> ** When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere easy.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** Remove the files: xyzzy . The patch does not yet cover these source files and their contained features.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Copy the files stdint.h, stdbool.h, AvailabilityMacros.h, AssertMacros.h, and TargetConditionals.h into this include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> ** Create a folder named malloc. Copy XCode's /usr/include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy XCode's /usr/include/sys/cdefs.h into it.<br /> ** Copy XCode's /usr/include/mach and /usr/include/i386 folders into your include folder.<br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. In other words, /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> <br /> <br /> * Apply the patch. The patch is a patch against version 476-13. Where to host patch?<br /> <br /> <br /> * Run make. Just type make.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> <br /> <br /> * Using CF-Lite in your own programs:<br /> <br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> <br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions.<br /> <br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4656 CFLite old 2008-08-12T05:50:40Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> * Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> ** When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * If you're using Microsoft Visual Studio, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard.<br /> * You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> <br /> <br /> * Arrange the source files. This layout is the format that the patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere easy.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** Remove the files: xyzzy . The patch does not yet cover these source files and their contained features.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Copy the files stdint.h, stdbool.h, AvailabilityMacros.h, AssertMacros.h, and TargetConditionals.h into this include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> ** Create a folder named malloc. Copy XCode's /usr/include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy XCode's /usr/include/sys/cdefs.h into it.<br /> ** Copy XCode's /usr/include/mach and /usr/include/i386 folders into your include folder.<br /> * Navigate to the folder where you extracted CF-Lite on your Cygwin command prompt.<br /> ** Cygwin maps disk drive letters to a mount point in the folder /cygdrive/. In other words, /cygdrive/c/ is equivalent to C:\, and /cygdrive/m/ would be M:\ at a DOS prompt or under My Computer.<br /> * Apply the patch. The patch is a patch against version 476-13. Where to host patch?<br /> * Run make. Just type make.<br /> ** If you need to capture stderr during the build process, use make 2>error_log.txt instead.<br /> ** <br /> <br /> * Using CF-Lite in your own programs:<br /> ** If you're using GCC<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** Works just like using a DLL in other GCC apps.<br /> *** Make sure you use the -mno-cygwin flag to prevent gcc from linking with the cygwin dll and C runtime. Link with -lmsvcrt instead.<br /> <br /> ** Visual Studio 2005<br /> *** You will need to define the preprocessor directive __WIN32__ in your build.<br /> *** In release target builds, you need to disable Visual Studio's library loading trimming. To do this, open your project properties, expand Configuration Properties, expand Linker, select Optimizations, then set the field labelled references to ''''Keep Unreferenced Data (/OPT:NOREF)''''. If you don't do this, you can have crashes at fairly innocent seeming functions.<br /> <br /> <br /> <br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4655 CFLite old 2008-08-12T05:20:47Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> * Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> ** When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * If you're using Microsoft Visual Studio, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard.<br /> * You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> <br /> * Arrange the source files. This layout is the format that the windows patch understands.<br /> ** Extract CF-Lite to a place of your choosing. You'll need to get to the directory easily from cygwin, so make it somewhere easy.<br /> ** Open the directory where you extracted CF-Lite.<br /> ** Remove the files: xyzzy . The patch does not yet cover these source files and their contained features.<br /> ** Copy flsl.c into your CFLite folder.<br /> ** Create a folder named include, in the CF-Lite folder.<br /> ** Open the include folder that you just made.<br /> ** Copy the files stdint.h, stdbool.h, AvailabilityMacros.h, AssertMacros.h, and TargetConditionals.h into this include folder.<br /> ** Extract the ICU4C package in the include folder. It should extract into an icu folder.<br /> ** Create a folder named malloc. Copy XCode's /usr/include/malloc/malloc.h into this folder.<br /> ** Create a folder named sys. Copy XCode's /usr/include/sys/cdefs.h into it.<br /> ** Copy XCode's /usr/include/mach and /usr/include/i386 folders into your include folder.<br /> * Apply the patch<br /> * Run make<br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4654 CFLite old 2008-08-12T04:32:11Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> * Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> ** When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * If you're using Microsoft Visual Studio, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard.<br /> * You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> <br /> <br /> * Apply the patch<br /> * Run make<br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br /> ** You can ignore the XCode project<br /> ** create a new project in your windows dev environment and add the two .cpp files.<br><br /> ** the "console.txt" is the example output that it '''should''' look like in your console<br /> ** you may need to tweak the relative path for "test.xml" to load properly. <br /> <br /> Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4653 CFLite old 2008-08-12T04:30:32Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> * Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug the dll, also install Devel/gdb.<br /> ** When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> <br /> * Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> * Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> * Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> * Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> * If you're using Microsoft Visual Studio, you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] They don't come with the compiler but are part of the C99 standard.<br /> * You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> <br /> <br /> * Apply the patch<br /> * Run make<br /> * Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br>* You can ignore the XCode project<br>* create a new project in your windows dev environment and add the two .cpp files.<br>* the "console.txt" is the example output that it '''should''' look like in your console<br>* you may need to tweak the relative path for "test.xml" to load properly. Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4652 CFLite old 2008-08-12T04:22:47Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> # Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> #* Devel/gcc-core <br /> #* Devel/gcc-objc <br /> #* Devel/make<br /> #* If you want to debug the dll, also install Devel/gdb.<br /> #* When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> # Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> # Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> # Get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> # Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> # you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] if you're using Microsoft Visual Studio, it doesn't come with the compiler but is part of the C99 standard.<br /> # Muck with leopard headers<br /> ##You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> # Apply the patch<br /> # run make<br /> # Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br>* You can ignore the XCode project<br>* create a new project in your windows dev environment and add the two .cpp files.<br>* the "console.txt" is the example output that it '''should''' look like in your console<br>* you may need to tweak the relative path for "test.xml" to load properly. Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4651 CFLite old 2008-08-12T04:20:39Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> # Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> #* Devel/gcc-core <br /> #* Devel/gcc-objc <br /> #* Devel/make<br /> #* If you want to debug, also install Devel/gdb.<br /> #* When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> # Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> # Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> # get FreeBSD's [http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/libkern/flsl.c?rev=1.4;content-type=text%2Fplain flsl.c] source file<br /> # Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> # you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] if you're using Microsoft Visual Studio, it doesn't come with the compiler but is part of the C99 standard. I suggest placing these files in your Visual Studio C include folder(C:\Program Files\Microsoft Visual Studio 8\VC\include by default for VS2005), but you can add these on a separate include path if you want to keep your compiler header folder pristine. More details about this file are on [http://en.wikipedia.org/wiki/Stdint.h Wikipedia]. Maybe it would be better to just add this to the include.zip with AvailabilityMacros et al?<br /> # Muck with leopard headers<br /> ##You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> # Apply the patch<br /> # run make<br /> # Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br>* You can ignore the XCode project<br>* create a new project in your windows dev environment and add the two .cpp files.<br>* the "console.txt" is the example output that it '''should''' look like in your console<br>* you may need to tweak the relative path for "test.xml" to load properly. Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4650 CFLite old 2008-08-12T04:16:47Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> # Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> #* Devel/gcc-core <br /> #* Devel/gcc-objc <br /> #* Devel/make<br /> #* If you want to debug, also install Devel/gdb.<br /> #* When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> # Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> # Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> # get FreeBSD's flsl.c source file<br /> # Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> # you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] if you're using Microsoft Visual Studio, it doesn't come with the compiler but is part of the C99 standard. I suggest placing these files in your Visual Studio C include folder(C:\Program Files\Microsoft Visual Studio 8\VC\include by default for VS2005), but you can add these on a separate include path if you want to keep your compiler header folder pristine. More details about this file are on [http://en.wikipedia.org/wiki/Stdint.h Wikipedia]. Maybe it would be better to just add this to the include.zip with AvailabilityMacros et al?<br /> # Muck with leopard headers<br /> ##You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> # Apply the patch<br /> # run make<br /> # Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br>* You can ignore the XCode project<br>* create a new project in your windows dev environment and add the two .cpp files.<br>* the "console.txt" is the example output that it '''should''' look like in your console<br>* you may need to tweak the relative path for "test.xml" to load properly. Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4649 CFLite old 2008-08-12T04:14:21Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> # Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> #* Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug, also install Devel/gdb.<br /> # When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> # Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> # Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> # get FreeBSD's flsl.c source file<br /> # Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> # you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] if you're using Microsoft Visual Studio, it doesn't come with the compiler but is part of the C99 standard. I suggest placing these files in your Visual Studio C include folder(C:\Program Files\Microsoft Visual Studio 8\VC\include by default for VS2005), but you can add these on a separate include path if you want to keep your compiler header folder pristine. More details about this file are on [http://en.wikipedia.org/wiki/Stdint.h Wikipedia]. Maybe it would be better to just add this to the include.zip with AvailabilityMacros et al?<br /> # Muck with leopard headers<br /> ##You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> # Apply the patch<br /> # run make<br /> # Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br>* You can ignore the XCode project<br>* create a new project in your windows dev environment and add the two .cpp files.<br>* the "console.txt" is the example output that it '''should''' look like in your console<br>* you may need to tweak the relative path for "test.xml" to load properly. Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4648 CFLite old 2008-08-12T04:13:17Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> # Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ** Devel/gcc-core <br /> ** Devel/gcc-objc <br /> ** Devel/make<br /> ** If you want to debug, also install Devel/gdb.<br /> # When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> # Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> # Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> # get FreeBSD's flsl.c source file<br /> # Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> # you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] if you're using Microsoft Visual Studio, it doesn't come with the compiler but is part of the C99 standard. I suggest placing these files in your Visual Studio C include folder(C:\Program Files\Microsoft Visual Studio 8\VC\include by default for VS2005), but you can add these on a separate include path if you want to keep your compiler header folder pristine. More details about this file are on [http://en.wikipedia.org/wiki/Stdint.h Wikipedia]. Maybe it would be better to just add this to the include.zip with AvailabilityMacros et al?<br /> # Muck with leopard headers<br /> ##You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> # Apply the patch<br /> # run make<br /> # Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br>* You can ignore the XCode project<br>* create a new project in your windows dev environment and add the two .cpp files.<br>* the "console.txt" is the example output that it '''should''' look like in your console<br>* you may need to tweak the relative path for "test.xml" to load properly. Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4647 CFLite old 2008-08-12T04:12:53Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> # Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> * Devel/gcc-core <br /> * Devel/gcc-objc <br /> * Devel/make<br /> * If you want to debug, also install Devel/gdb.<br /> # When you first run cygwin, it may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> # Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> # Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> # get FreeBSD's flsl.c source file<br /> # Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> # you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] if you're using Microsoft Visual Studio, it doesn't come with the compiler but is part of the C99 standard. I suggest placing these files in your Visual Studio C include folder(C:\Program Files\Microsoft Visual Studio 8\VC\include by default for VS2005), but you can add these on a separate include path if you want to keep your compiler header folder pristine. More details about this file are on [http://en.wikipedia.org/wiki/Stdint.h Wikipedia]. Maybe it would be better to just add this to the include.zip with AvailabilityMacros et al?<br /> # Muck with leopard headers<br /> ##You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> # Apply the patch<br /> # run make<br /> # Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br>* You can ignore the XCode project<br>* create a new project in your windows dev environment and add the two .cpp files.<br>* the "console.txt" is the example output that it '''should''' look like in your console<br>* you may need to tweak the relative path for "test.xml" to load properly. Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4646 CFLite old 2008-08-12T04:02:52Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> # Install [[CFLite/Cygwin|Cygwin]] - select (add them by clicking the text labelled Skip) these packages during the install:<br /> ## Devel/gcc-core <br /> ## Devel/gcc-objc <br /> ## Devel/make<br /> ## If you want to debug, also install Devel/gdb.<br /> # After the install completes, cygwin may notify you that it needs you to build /etc/passwd and /etc/group. Do this. Your cygwin setup should be ready.<br /> <br /> # Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> # Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> # get FreeBSD's flsl.c source file<br /> # Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> # you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] if you're using Microsoft Visual Studio, it doesn't come with the compiler but is part of the C99 standard. I suggest placing these files in your Visual Studio C include folder(C:\Program Files\Microsoft Visual Studio 8\VC\include by default for VS2005), but you can add these on a separate include path if you want to keep your compiler header folder pristine. More details about this file are on [http://en.wikipedia.org/wiki/Stdint.h Wikipedia]. Maybe it would be better to just add this to the include.zip with AvailabilityMacros et al?<br /> # Muck with leopard headers<br /> ##You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> # Apply the patch<br /> # run make<br /> # Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br>* You can ignore the XCode project<br>* create a new project in your windows dev environment and add the two .cpp files.<br>* the "console.txt" is the example output that it '''should''' look like in your console<br>* you may need to tweak the relative path for "test.xml" to load properly. Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4645 CFLite old 2008-08-10T12:02:56Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> # Install [[CFLite/Cygwin|Cygwin]] - select these packages during the install:<br /> Devel/gcc-core Devel/gcc-objc Devel/make (add them by clicking the text labelled Skip)<br /> My install didn't complete the first time, if this happens, run setup.exe again and run through the defaults<br /> My install told me to build /etc/passwd and /etc/group and gave instructions, do this if notified.kjgft<br /> # Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> # Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> #get FreeBSD's flsl.c source file<br /> # install it where??<br /> # Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> # install it where??<br /> # you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] if you're using Microsoft Visual Studio, it doesn't come with the compiler but is part of the C99 standard. I suggest placing these files in your Visual Studio C include folder(C:\Program Files\Microsoft Visual Studio 8\VC\include by default for VS2005), but you can add these on a separate include path if you want to keep your compiler header folder pristine. More details about this file are on [http://en.wikipedia.org/wiki/Stdint.h Wikipedia]. Maybe it would be better to just add this to the include.zip with AvailabilityMacros et al?<br /> # Muck with leopard headers<br /> You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> # Apply the patch<br /> # run make<br /> # Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br>* You can ignore the XCode project<br>* create a new project in your windows dev environment and add the two .cpp files.<br>* the "console.txt" is the example output that it '''should''' look like in your console<br>* you may need to tweak the relative path for "test.xml" to load properly. Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4644 CFLite old 2008-08-10T07:32:56Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> # Install [[CFLite/Cygwin|Cygwin]] - select these packages during the install:<br /> Devel/gcc-core Devel/gcc-objc Devel/make (add them by clicking the text labelled Skip)<br /> My install didn't complete the first time, if this happens, run setup.exe again and run through the defaults<br /> My install told me to build /etc/passwd and /etc/group and gave instructions, do this if notified.kjgft<br /> # Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> # Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> # install it where??<br /> # Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> # install it where??<br /> # you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] if you're using Microsoft Visual Studio, it doesn't come with the compiler but is part of the C99 standard. I suggest placing these files in your Visual Studio C include folder(C:\Program Files\Microsoft Visual Studio 8\VC\include by default for VS2005), but you can add these on a separate include path if you want to keep your compiler header folder pristine. More details about this file are on [http://en.wikipedia.org/wiki/Stdint.h Wikipedia]. Maybe it would be better to just add this to the include.zip with AvailabilityMacros et al?<br /> # Muck with leopard headers<br /> You will need the contents of mach/*, i386/*, malloc/malloc.h, and sys/cdefs.h from xcode 3.0<br /> # Apply the patch<br /> # run make<br /> # Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br>* You can ignore the XCode project<br>* create a new project in your windows dev environment and add the two .cpp files.<br>* the "console.txt" is the example output that it '''should''' look like in your console<br>* you may need to tweak the relative path for "test.xml" to load properly. Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4643 CFLite old 2008-08-10T06:20:20Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> # Install [[CFLite/Cygwin|Cygwin]] - select these packages during the install:<br /> Devel/gcc-core Devel/gcc-objc Devel/make (add them by clicking the text labelled Skip)<br /> My install didn't complete the first time, if this happens, run setup.exe again and run through the defaults<br /> My install told me to build /etc/passwd and /etc/group and gave instructions, do this if notified.kjgft<br /> # Download [http://download.icu-project.org/files/icu4c/4.0/icu4c-4_0-Win32-msvc8.zip ICU4C] <br /> # Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> # install it where??<br /> # Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> # install it where??<br /> # you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] if you're using Microsoft Visual Studio, it doesn't come with the compiler but is part of the C99 standard. I suggest placing these files in your Visual Studio C include folder(C:\Program Files\Microsoft Visual Studio 8\VC\include by default for VS2005), but you can add these on a separate include path if you want to keep your compiler header folder pristine. More details about this file are on [http://en.wikipedia.org/wiki/Stdint.h Wikipedia]. Maybe it would be better to just add this to the include.zip with AvailabilityMacros et al?<br /> # Muck with leopard headers<br /> # Apply the patch<br /> # run make<br /> # Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br>* You can ignore the XCode project<br>* create a new project in your windows dev environment and add the two .cpp files.<br>* the "console.txt" is the example output that it '''should''' look like in your console<br>* you may need to tweak the relative path for "test.xml" to load properly. Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4635 CFLite old 2008-07-27T05:22:50Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> # Install [[CFLite/Cygwin|Cygwin]]<br /> # Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> # install it where??<br /> # Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> # install it where??<br /> # you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] and [http://www.koders.com/c/fidDF4818DD265741F8A74455FC281F0C1CBA35EB47.aspx stdbool.h] if you're using Microsoft Visual Studio, it doesn't come with the compiler but is part of the C99 standard. I suggest placing these files in your Visual Studio C include folder(C:\Program Files\Microsoft Visual Studio 8\VC\include by default for VS2005), but you can add these on a separate include path if you want to keep your compiler header folder pristine. More details about this file are on [http://en.wikipedia.org/wiki/Stdint.h Wikipedia]. Maybe it would be better to just add this to the include.zip with AvailabilityMacros et al?<br /> # Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br>* You can ignore the XCode project<br>* create a new project in your windows dev environment and add the two .cpp files.<br>* the "console.txt" is the example output that it '''should''' look like in your console<br>* you may need to tweak the relative path for "test.xml" to load properly. Please document any necessary changes to the source code.</div>

Guberif https://karaoke.kjams.com/w/index.php?title=Stdbool.h&diff=4634 Stdbool.h 2008-07-27T05:15:15Z

<p>Guberif: </p> <hr /> <div></div>

Guberif https://karaoke.kjams.com/w/index.php?title=Stdbool.h&diff=4633 Stdbool.h 2008-07-27T05:08:45Z

<p>Guberif: </p> <hr /> <div>/*<br /> * Copyright (c) 2000 Jeroen Ruigrok van der Werven <asmodai@FreeBSD.org><br /> * All rights reserved.<br /> *<br /> * Redistribution and use in source and binary forms, with or without<br /> * modification, are permitted provided that the following conditions<br /> * are met:<br /> * 1. Redistributions of source code must retain the above copyright<br /> * notice, this list of conditions and the following disclaimer.<br /> * 2. Redistributions in binary form must reproduce the above copyright<br /> * notice, this list of conditions and the following disclaimer in the<br /> * documentation and/or other materials provided with the distribution.<br /> *<br /> * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND<br /> * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE<br /> * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE<br /> * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE<br /> * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL<br /> * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS<br /> * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)<br /> * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT<br /> * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY<br /> * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF<br /> * SUCH DAMAGE.<br /> *<br /> * $FreeBSD: src/include/stdbool.h,v 1.6 2002/08/16 07:33:14 alfred Exp $<br /> */<br /> <br /> #ifndef _STDBOOL_H_<br /> #define _STDBOOL_H_ <br /> <br /> #define __bool_true_false_are_defined 1<br /> <br /> #ifndef __cplusplus<br /> <br /> #define false 0<br /> #define true 1<br /> <br /> #define bool _Bool<br /> #if __STDC_VERSION__ < 199901L && __GNUC__ < 3<br /> typedef int _Bool;<br /> #endif<br /> <br /> #endif /* !__cplusplus */<br /> <br /> #endif /* !_STDBOOL_H_ */</div>

Guberif https://karaoke.kjams.com/w/index.php?title=CFLite_old&diff=4632 CFLite old 2008-07-27T04:35:51Z

<p>Guberif: </p> <hr /> <div>This page documents how to build CFLite 476.10 such that you can then link to it in your Windows projects, and then blissfully use CFStrings, CFDictionaries, and all the other CFGoodness that CFLite will bring you. For a "quick and dirty" way to just start *using* CFLite on windows (without having to compile it), [[Code/CFLite|click here]].<br /> <br /> On Windows XP or Windows Vista:<br><br /> # Install [[CFLite/Cygwin|Cygwin]]<br /> # Download [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.13.tar.gz CFLite 476.13]. '''Ooops!''' Not available? Try: [http://www.opensource.apple.com/darwinsource/tarballs/apsl/CF-476.10.tar.gz CFLite 476.10]<br /> # install it where??<br /> # Download [http://kjams.com/cflite/downloads/include.zip include.zip] (contains /usr/include/*, which includes AvailabilityMacros, AssertMacros and TargetConditionals from 10.5)<br /> # install it where??<br /> # you'll need [http://msinttypes.googlecode.com/svn/trunk/stdint.h stdint.h] if you're using Microsoft Visual Studio, it doesn't come with the compiler but is part of the C99 standard. I suggest placing this file in your Visual Studio C include folder(C:\Program Files\Microsoft Visual Studio 8\VC\include by default for VS2005), but you can add it on a separate include path if you want to keep your compiler header folder pristine. More details about this file are on [http://en.wikipedia.org/wiki/Stdint.h Wikipedia]. Maybe it would be better to just add this to the include.zip with AvailabilityMacros et al?<br /> # Download [[CFLite/CFTest|CFTest]] source files. This is the test harness sample project.<br>* You can ignore the XCode project<br>* create a new project in your windows dev environment and add the two .cpp files.<br>* the "console.txt" is the example output that it '''should''' look like in your console<br>* you may need to tweak the relative path for "test.xml" to load properly. Please document any necessary changes to the source code.</div>

Guberif