From: Will Senn <will.senn@gmail.com>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Setting up an X Development Environment for Mac OS
Date: Tue, 24 Jan 2023 19:46:54 -0600 [thread overview]
Message-ID: <3e272d72-b77a-d347-b5c3-7ed19482e5af@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]
All,
If you think unix ends without x, just move along, nothing to see here.
Otherwise, I thought I would share the subject of my latest post and a
link with those of you interested in such things.
Recently, I've been tooling around trying to wrap my head around x
windows and wanted to give programming it a shot at the xlib level... on
my mac, if possible. So, I bought a copy of Adrian Nye's Xlib
Programming Manual for Version 11 R4/R5, aka Volume One of The
Definitive Guides to the X Window System, published, get this... 30+
years ago, in 1992 :) and started reading like a madman. As usual, this
was an example of great technical writing from the prior millenium,
something rarely found today.
Anyway, I hunted up the source code examples as published, unpacked
them, did a few environmental things to my mac, and built my first xlib
application from that source. A few tweaks to my XQuartz configuration
and I was running the application in twm on my mac, with a root window.
To read about it and see it in all of its glory, check it out here:
https://decuser.github.io/operating-systems/mojave/x-windows/2023/01/24/x-windows-dev-on-mac.html
The same sort of setup works with Linux, FreeBSD, or my latest
environment DragonFly BSD. It's not the environment that I find
interesting, but rather the X Window System itself, but this is my way
of entering into that world. If you are interested in running X Windows,
not as an integrated system on your mac (where x apps run in aqua
windows), but with a 'regular' window manager, and you haven't figured
out how, this is one way.
On the provocateur front - is X part of unix? I mean this in oh so many
nuanced ways, so read into it as you will. I would contend, torpedoes be
damned, that it is :).
Will
[-- Attachment #2: Type: text/html, Size: 2418 bytes --]
next reply other threads:[~2023-01-25 1:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 1:46 Will Senn [this message]
2023-01-25 7:45 ` [TUHS] " segaloco via TUHS
2023-01-25 8:00 ` Lars Brinkhoff
2023-01-25 16:41 ` Rich Salz
2023-01-25 19:53 ` Theodore Ts'o
2023-01-25 20:04 ` Dan Cross
2023-01-25 20:23 ` Larry McVoy
2023-01-25 20:27 ` Chet Ramey
2023-01-27 4:49 ` Theodore Ts'o
2023-01-27 18:05 ` Henry Mensch
2023-01-27 18:24 ` Charles H Sauer (he/him)
2023-01-26 13:17 ` Marc Donner
2023-02-08 22:12 ` [TUHS] project athena (was Re: Setting up an X Development Environment for Mac OS) Jonathan Gray
2023-02-09 2:51 ` [TUHS] " Theodore Ts'o
2023-02-11 0:13 ` Henry Mensch
2023-02-11 0:53 ` Larry McVoy
2023-02-11 3:51 ` Jonathan Gray
2023-02-11 14:48 ` Larry McVoy
2023-02-12 2:26 ` Jonathan Gray
2023-02-12 21:35 ` Henry Mensch
2023-02-11 0:23 ` Henry Mensch
2023-01-25 20:38 [TUHS] Re: Setting up an X Development Environment for Mac OS Noel Chiappa
2023-01-25 21:25 ` Clem Cole
2023-01-26 6:30 ` Lars Brinkhoff
2023-01-26 10:56 ` Ralph Corderoy
2023-01-26 15:28 ` [TUHS] " josh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e272d72-b77a-d347-b5c3-7ed19482e5af@gmail.com \
--to=will.senn@gmail.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).