Code/CFLite/CFNetwork: Difference between revisions
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
#download <googa>../../../cflite/downloads/CoreFoundation.zip|CoreFoundation|/downloads/CoreFoundationInstaller</googa> and put it in your development tree | #download <googa>../../../cflite/downloads/CoreFoundation.zip|CoreFoundation|/downloads/CoreFoundationInstaller</googa> and put it in your development tree | ||
# using Qt (tested on 5.9.1) | # using Qt (tested on 5.9.1) | ||
## open CF/opencflite-476.17.2/Qt/CFLite/CFLite.pro | ## on Windows: open CF/opencflite-476.17.2/Qt/CFLite/CFLite.pro | ||
## | ## open CFTest/project/qt/CFTest/CFTest_win.pro | ||
## your "Session" should look like this:<br>{{SERVER}}/cflite/screenshots/qt_session.png | ## your "Session" should look like this: (Not including CFLite on Mac)<br>{{SERVER}}/cflite/screenshots/qt_session.png | ||
## set CFTest_win to the active project, use the 64bit one, | ## set CFTest_win/mac to the active project, use the 64bit one | ||
## on Windows, set it to depend on and sync with CFLite, like this:<br>{{SERVER}}/cflite/screenshots/qt_session_dependencies.png | |||
## below screen shots show 64bit debug as an example, you can optionally set up 32bit debug, and also release of both 32 and 64 | ## below screen shots show 64bit debug as an example, you can optionally set up 32bit debug, and also release of both 32 and 64 | ||
## how CFLite build settings should look: (ignore run settings)<br>{{SERVER}}/cflite/screenshots/qt_build_cflite.png | ## Windows: how CFLite build settings should look: (ignore run settings)<br>{{SERVER}}/cflite/screenshots/qt_build_cflite.png | ||
## how CFTest build settings should look:<br>{{SERVER}}/cflite/screenshots/qt_build_cftest.png | ## how CFTest build settings should look:<br>{{SERVER}}/cflite/screenshots/qt_build_cftest.png | ||
## how CFTest run settings should look:<br>{{SERVER}}/cflite/screenshots/qt_run_cftest.png | ## how CFTest run settings should look:<br>{{SERVER}}/cflite/screenshots/qt_run_cftest.png | ||
Revision as of 15:41, 9 August 2017
I hereby release everything here under the terms of the "FreeBSD License".
If you use QuickTime on Windows, or Parallels Desktop for debugging Windows
Be very sure you check this stuff out, it's important.
How to get started
- if you're on Windows:
- Install Bonjour Print Services. (you do not need to run the printer wizard nor set up a printer, this is just a service that CFTest makes use of)
- install Python 2.7 do NOT install python 3. Python is used for post-build steps / deployment
- download CoreFoundation and put it in your development tree
- using Qt (tested on 5.9.1)
- on Windows: open CF/opencflite-476.17.2/Qt/CFLite/CFLite.pro
- open CFTest/project/qt/CFTest/CFTest_win.pro
- your "Session" should look like this: (Not including CFLite on Mac)
- set CFTest_win/mac to the active project, use the 64bit one
- on Windows, set it to depend on and sync with CFLite, like this:
- below screen shots show 64bit debug as an example, you can optionally set up 32bit debug, and also release of both 32 and 64
- Windows: how CFLite build settings should look: (ignore run settings)
- how CFTest build settings should look:
- how CFTest run settings should look:
- if you're using Visual Studio
- Open the file "CFNetwork/CFTest/win_vs/CFTest.sln".
- go to "Solution Explorer"
- select "CFTest", right click it and pick "Properties"
- in the "Configuration:" menu, pick "All Configurations"
- go to "configuration properties->debugging"
- set "Command" to "$(SolutionDir)build\$(TargetName).app\Contents\Windows\$(TargetFileName)".
- in VS2010 and later, actually you may need to just specify the full path (in step 4 above), as "$(TargetName)" does not seem to expand correctly for debug vs. release