3 ms·
> I’m excluding Cygwin and its major fork, MSYS2, despite not inheriting any of these flaws. They change so much that they’re effectively whole new platforms, n
by kazinator 5y ago
> I’m excluding Cygwin and its major fork, MSYS2, despite not inheriting any of these flaws. They change so much that they’re effectively whole new platforms, not truly “native” to Windows.
Ah, but Cygwin doesn't actually change so much that we can't scale some of it back, to have sane C and C++ development on Windows.
https://www.kylheku.com/cygnal/ https://www.kylheku.com/cygnal/
Build a Cygwin program, then do a switcheroo on the cygwin1.dll to deploy as a Windows program.
I developed Cygnal to have an easy and sane way of porting the TXR language to Windows.
You can control the Windows console with <termios.h> and ANSI/VT100 escapes. Literally not a line of code has to change from Linux!
In Cygnal, I scaled back various POSIXy things in Cygwin. For instance:
- normal paths with drive letter names work.
- the chdir() function understands the DOS/Windows concept of a logged drive: that chdir("D:") will change to the current directory remembered for the D drive.
- drive relative paths like "d:doc.txt" work (using the working directory associated with the D drive).
- PATH is semicolon separated, not colon.
- The HOME variable isn't /home/username, but is rewritten from the value of USERPROFILE.
(I had problems with native Windows Vim launched from a Cygwin program, and then looking
for a nonexistent /home due to the frobbed variable, so I was sure to address this issue).
- popen and system do not look for /bin/sh. They use cmd.exe!
- when exec detects that "/bin/sh" "-c" "<arg>" is being spawned, it rewrites this to cmd.exe. The benefit is that interpreter programs which expose command invocation functions which they implement from scratch by forking and execing /bin/sh -c command are thereby retargetted to windows.
- the /cygdrive directory is gone
- /dev is available as dev:/ so you can access devices.
- 6581 5y ago> https://www.kylheku.com/cygnal/ https://www.kylheku.com/cygnal/ Your SSL certificate is invalid and your server uses TLS 1.0 which is insecure and disabled by default in recent browsers.
- kazinator 5y ago> your server uses TLS 1.0 That is correct. Basically, the OS upgrades kept breaking my highly customized setup, resulting in downtime and wasted time, so eventually I dropped out of the program. I need to rebuild a new server and migrate everything over. With two small kids now and full-time job, if I have any block of free time (basically late at night or early morning), I prioritize putting it into working on code. It's not just a web server setup and custom things around it, but Postgress databases, e-mail setup and other stuff. Every item could have some issue chewing up hours. > which is insecure Secure/insecure isn't a simple Boolean. It's less secure than newer versions of the protocol, but it's not "insecure" like, say, a plain password sent over telnet. > Your SSL certificate is invalid I don't believe that is the case. Firstly, I've never had an problem connecting to the site using https from any browser. Secondly, most online SSL checking tools do not report a problem other than remarking on it being self-signed. For instance geocerts.com says "The hostname (www.kylheku.com) matches the certificate and the certificate is valid." I found one which doesn't understand wildcard names: it reports that www.kylheku.com doesn't match *.kylheku.com. That's a bug in the checker. One other flags some unspecified issue with the Alternative Names property (which I didn't even specify when generating the cert).