elf
/
xcb-studies
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
xcb-studies/Makefile

18 lines
249 B
Makefile
Raw Normal View History

I consider Makefiles documentation, and this will help remind me that I don't want to build in the root, but in a build subdirectory. It also provides a nice and easy `make clean` method.
2022-02-18 02:31:41 +00:00
all: build/xrandr
.PHONY: all
Initial commit: XRandR connects to the server via XCB. I really need to start two cheatsheets for this: one for CMake, and one for XCB.
2022-02-17 15:01:34 +00:00
I consider Makefiles documentation, and this will help remind me that I don't want to build in the root, but in a build subdirectory. It also provides a nice and easy `make clean` method.
2022-02-18 02:31:41 +00:00
build:
mkdir -p build
Initial commit: XRandR connects to the server via XCB. I really need to start two cheatsheets for this: one for CMake, and one for XCB.
2022-02-17 15:01:34 +00:00
I consider Makefiles documentation, and this will help remind me that I don't want to build in the root, but in a build subdirectory. It also provides a nice and easy `make clean` method.
2022-02-18 02:31:41 +00:00
build/Makefile: build CMakeLists.txt
cd build && cmake ..
Initial commit: XRandR connects to the server via XCB. I really need to start two cheatsheets for this: one for CMake, and one for XCB.
2022-02-17 15:01:34 +00:00
I consider Makefiles documentation, and this will help remind me that I don't want to build in the root, but in a build subdirectory. It also provides a nice and easy `make clean` method.
2022-02-18 02:31:41 +00:00
build/xrandr: build/Makefile src/xrandr.cpp CMakeLists.txt
cd build && make
Initial commit: XRandR connects to the server via XCB. I really need to start two cheatsheets for this: one for CMake, and one for XCB.
2022-02-17 15:01:34 +00:00
clean:
I consider Makefiles documentation, and this will help remind me that I don't want to build in the root, but in a build subdirectory. It also provides a nice and easy `make clean` method.
2022-02-18 02:31:41 +00:00
rm -fr build
Innteresting. It seems that the `output` collection is much more reliable as a source of truth about which monitors and screens are actually in use. Each one comes with its own collection of `crtc`, but you can just skip the ones that return `null`, giving you a reliable list of the "active and visible" screens that the user is currently looking at. Excellent! This means that I'm one step closer to having a viable solution! I also discovered the [xcb_util](https://xcb.freedesktop.org/XcbUtil/) library of helpful utilities has a function called `xcb_aux_get_screen` for getting the root screen because everyone was weirded out by that list traversal algorithm. The source code to [xedgewarp](https://github.com/Airblader/xedgewarp) was invaluable in revealing these secrets to me. So far this little toy compiles down to only 35KB, and that includes using `std::cout` and `std::vector`! I wonder how big the Rust version will be. Yeah, yeah, I know, it cheats by having lots of itself hidden in the kernel. Next up: Actually knowing what the rotation status is.
2022-02-24 23:59:43 +00:00
run: build/xrandr
./build/xrandr