2a292c3984
Make it possible to build curl for Windows CE using the CeGCC toolchain.
With both CMake and autotools, including tests and examples, also in CI.
The build configuration is the default one with Schannel enabled. No
3rd-party dependencies have been tested.
Also revive old code to make Schannel build with Windows CE, including
certificate verification.
Builds have been throughougly tested. But, I've made no functional tests
for this PR. Some parts (esp. file operations, like truncate and seek)
are stubbed out and likely broken as a result. Test servers build, but
they do not work on Windows CE. This patch substitutes `fstat()` calls
with `stat()`, which operate on filenames, not file handles. This may or
may not work and/or may not be secure.
About CeGCC: I used the latest available macOS binary build v0.59.1
r1397 from 2009, in native `mingw32ce` build mode. CeGCC is in effect
MinGW + GCC 4.4.0 + old/classic-mingw Windows headers. It targets
Windows CE v3.0 according to its `_WIN32_WCE` value. It means this PR
restores portions of old/classic-mingw support. It makes the Windows CE
codepath compatible with GCC 4.4.0. It also adds workaround for CMake,
which cannot identify and configure this toolchain out of the box.
Notes:
- CMake doesn't recognize CeGCC/mingw32ce, necessitating tricks as seen
with Amiga and MS-DOS.
- CMake doesn't set `MINGW` for mingw32ce. Set it and `MINGW32CE`
manually as a helper variable, in addition to `WINCE` which CMake sets
based on `CMAKE_SYSTEM_NAME`.
- CMake fails to create an implib for `libcurl.dll`, due to not
recognizing the platform as a Windowsy one. This patch adds the
necessary workaround to make it work.
- headers shipping with CeGCC miss some things curl needs for Schannel
support. Fixed by restoring and renovating code previously deleted
old-mingw code.
- it's sometime non-trivial to figure out if a fallout is WinCE,
mingw32ce, old-mingw, or GCC version-specific.
- WinCE is always Unicode. With exceptions: no `wmain`,
`GetProcAddress()`.
- `_fileno()` is said to convert from `FILE *` to `void *` which is
a Win32 file `HANDLE`. (This patch doesn't use this, but with further
effort it probably could be.)
https://stackoverflow.com/questions/3989545/how-do-i-get-the-file-handle-from-the-fopen-file-structure
- WinCE has no signals, current directory, stdio/CRT file handles, no
`_get_osfhandle()`, no `errno`, no `errno.h`. Some of this stuff is
standard C89, yet missing from this platform. Microsoft expects
Windows CE apps to use Win32 file API and `FILE *` exclusively.
- revived CeGCC here (not tested for this PR):
https://building.enlyze.com/posts/a-new-windows-ce-x86-compiler-in-2024/
On `UNDER_CE` vs. `_WIN32_WCE`: (This patch settled on `UNDER_CE`)
- A custom VS2008 WinCE toolchain does not set any of these.
The compiler binaries don't contain these strings, and has no compiler
option for targeting WinCE, hinting that a vanilla toolchain isn't
setting any of them either.
- `UNDER_CE` is automatically defined by the CeGCC compiler.
https://cegcc.sourceforge.net/docs/details.html
- `UNDER_CE` is similar to `_WIN32`, except it's not set automatically
by all compilers. It's not supposed to have any value, like a version.
(Though e.g. OpenSSL sets it to a version)
- `_WIN32_WCE` is the CE counterpart of the non-CE `_WIN32_WINNT` macro.
That does return the targeted Windows CE version.
- `_WIN32_WCE` is not defined by compilers, and relies on a header
setting it to a default, or the build to set it to the desired target
version. This is also how `_WIN32_WINNT` works.
- `_WIN32_WCE` default is set by `windef.h` in CeGCC.
- `_WIN32_WCE` isn't set to a default by MSVC Windows CE headers (the
ones I checked at least).
- CMake sets `_WIN32_WCE=<ver>`, `UNDER_CE`, `WINCE` for MSVC WinCE.
- `_WIN32_WCE` seems more popular in other projects, including CeGCC
itself. `zlib` is a notable exception amongst curl dependencies,
which uses `UNDER_CE`.
- Since `_WIN32_WCE` needs "certain" headers to have it defined, it's
undefined depending on headers included beforehand.
- `curl/curl.h` re-uses `_WIN32_WCE`'s as a self-guard, relying on
its not-(necessarily)-defined-by-default property:
|
||
|---|---|---|
| .. | ||
| .checksrc | ||
| .gitignore | ||
| 10-at-a-time.c | ||
| adddocsref.pl | ||
| address-scope.c | ||
| altsvc.c | ||
| anyauthput.c | ||
| block_ip.c | ||
| cacertinmem.c | ||
| certinfo.c | ||
| chkspeed.c | ||
| CMakeLists.txt | ||
| connect-to.c | ||
| cookie_interface.c | ||
| crawler.c | ||
| debug.c | ||
| default-scheme.c | ||
| ephiperfifo.c | ||
| evhiperfifo.c | ||
| externalsocket.c | ||
| fileupload.c | ||
| ftp-wildcard.c | ||
| ftpget.c | ||
| ftpgetinfo.c | ||
| ftpgetresp.c | ||
| ftpsget.c | ||
| ftpupload.c | ||
| ftpuploadfrommem.c | ||
| ftpuploadresume.c | ||
| getinfo.c | ||
| getinmemory.c | ||
| getredirect.c | ||
| getreferrer.c | ||
| ghiper.c | ||
| headerapi.c | ||
| hiperfifo.c | ||
| href_extractor.c | ||
| hsts-preload.c | ||
| htmltidy.c | ||
| htmltitle.cpp | ||
| http2-download.c | ||
| http2-pushinmemory.c | ||
| http2-serverpush.c | ||
| http2-upload.c | ||
| http3-present.c | ||
| http3.c | ||
| http-options.c | ||
| http-post.c | ||
| httpcustomheader.c | ||
| httpput-postfields.c | ||
| httpput.c | ||
| https.c | ||
| imap-append.c | ||
| imap-authzid.c | ||
| imap-copy.c | ||
| imap-create.c | ||
| imap-delete.c | ||
| imap-examine.c | ||
| imap-fetch.c | ||
| imap-list.c | ||
| imap-lsub.c | ||
| imap-multi.c | ||
| imap-noop.c | ||
| imap-search.c | ||
| imap-ssl.c | ||
| imap-store.c | ||
| imap-tls.c | ||
| interface.c | ||
| ipv6.c | ||
| keepalive.c | ||
| localport.c | ||
| Makefile.am | ||
| Makefile.example | ||
| Makefile.inc | ||
| maxconnects.c | ||
| multi-app.c | ||
| multi-debugcallback.c | ||
| multi-double.c | ||
| multi-event.c | ||
| multi-formadd.c | ||
| multi-legacy.c | ||
| multi-post.c | ||
| multi-single.c | ||
| multi-uv.c | ||
| multithread.c | ||
| netrc.c | ||
| parseurl.c | ||
| persistent.c | ||
| pop3-authzid.c | ||
| pop3-dele.c | ||
| pop3-list.c | ||
| pop3-multi.c | ||
| pop3-noop.c | ||
| pop3-retr.c | ||
| pop3-ssl.c | ||
| pop3-stat.c | ||
| pop3-tls.c | ||
| pop3-top.c | ||
| pop3-uidl.c | ||
| post-callback.c | ||
| postinmemory.c | ||
| postit2-formadd.c | ||
| postit2.c | ||
| progressfunc.c | ||
| protofeats.c | ||
| range.c | ||
| README.md | ||
| resolve.c | ||
| rtsp-options.c | ||
| sendrecv.c | ||
| sepheaders.c | ||
| sessioninfo.c | ||
| sftpget.c | ||
| sftpuploadresume.c | ||
| shared-connection-cache.c | ||
| simple.c | ||
| simplepost.c | ||
| simplessl.c | ||
| smooth-gtk-thread.c | ||
| smtp-authzid.c | ||
| smtp-expn.c | ||
| smtp-mail.c | ||
| smtp-mime.c | ||
| smtp-multi.c | ||
| smtp-ssl.c | ||
| smtp-tls.c | ||
| smtp-vrfy.c | ||
| sslbackend.c | ||
| synctime.c | ||
| threaded-ssl.c | ||
| unixsocket.c | ||
| url2file.c | ||
| urlapi.c | ||
| usercertinmem.c | ||
| version-check.pl | ||
| websocket-cb.c | ||
| websocket.c | ||
| xmlstream.c | ||
libcurl examples
This directory is for libcurl programming examples. They are meant to show some simple steps on how you can build your own application to take full advantage of libcurl.
If you end up with other small but still useful example sources, please mail them for submission in future packages and on the website.
Building
The Makefile.example is an example Makefile that could be used to build
these examples. Just edit the file according to your system and requirements
first.
Most examples should build fine using a command line like this:
`curl-config --cc --cflags --libs` -o example-my example.c
Some compilers do not like having the arguments in this order but instead want you do reorganize them like:
`curl-config --cc` -o example-my example.c `curl-config --cflags --libs`
Please do not use the curl.se site as a test target for your libcurl
applications/experiments. Even if some of the examples use that site as a URL
at some places, it does not mean that the URLs work or that we expect you to
actually torture our website with your tests. Thanks.
Examples
Each example source code file is designed to be and work stand-alone and rather self-explanatory. The examples may at times lack the level of error checks you need in a real world, but that is then only for the sake of readability: to make the code smaller and easier to follow.