Windows Terminal is a useful and welcome
open source
addition to any developer working on Windows.
It has no prerequisites and works well with multiple WSL distros.
Python can extract .zst Zstd files using the
zstandard
package.
Zstd is widely supported and available across operating systems.
Make a Python function
extract_zstd
to extract all files and directories inside the .zst file.
Matlab
websave
or
ftp
might not work in cases where a plain “curl” or “wget” command works.
A symptom of this issue is HTML is downloaded instead of the intended binary file.
Websites such as
Dropbox
recognize the HTTP User Agent of curl and Wget and mutate the web server response to be automation-friendly.
Since Matlab is much less commonly used than Python, curl, Wget, etc. this user agent-dependent behavior results.
We recommend understanding why Matlab websave doesn’t work, or use the low-level Matlab
HTTP Interface.
To use curl from Matlab, recognize this may require unique setup for each system, despite that curl is included (preinstalled) in modern operating systems including Windows.
The extra quotes around “url” allow for arbitrary characters to be used in the URL that can confuse shells like zsh.
The “-L” option to curl allows redirects.
Linux systems with multiple curl versions installed may need to set an environment variable to prioritize.
Set the filename as appropriate for computer (ensure the file exists).
CMake
configure_file
can serve to generate source code files including Fortran.
For templates beyond a few lines of code, it may be useful to read the template from a file.
This requires setting CMake directory property
CMAKE_CONFIGURE_DEPENDS
to have CMake regenerate the file if the template file changes as in the example below.
file(READmy_template.in.f90template_code)configure_file(example.in.f90example.f90@ONLY)set_property(DIRECTORYPROPERTYCMAKE_CONFIGURE_DEPENDSmy_template.in.f90)#example use
add_executable(main ${CMAKE_CURRENT_BINARY_DIR}/example.f90)
iftop
is a handy utility on macOS, Linux and other Unices for a live Terminal graph of network data flow to particular addresses.
On computers with many network interfaces, including virtual interfaces such as on macOS, it is handy to set a default interface in a config file.
iftop uses the file ~/.iftoprc.
For example, on macOS you may be interested in interface “en1”.
To help determine the desired interface, use ifconfig or ip a to find the interface with the public IP address.
Then create ~/.iftoprc containing like:
interface: en1
where “en1” is your desired interface determined as per above.
RHEL uses
firewalld
to provide network firewall.
firewalld has the concept of
runtime vs. permanent rules,
which help avoid getting the firewall into an unusable state.
Permanent rules become live at next restart/reboot, while runtime rules disappear at restart/reboot.
Suppose one wishes to put the SSH server on a non-default port 12345 to mitigate auth log clutter.
First configure the SSH server in /etc/ssh/sshd_config, then restart SSH and verify the SSH configuration is working by adding the port to firewalld (here, 12345):
firewall-cmd --add-port=12345/tcp
If this works, make the firewalld rule permanent:
firewall-cmd --permanent --add-port=12345/tcp
SELinux will also need an updated policy to allow the SSH port change, like:
To have the most reliable path operations in CMake, it’s typically best to resolve paths to the full expanded path.
Note: there are a few CMake functions that desire relative paths, but those are clearly spelled out in the docs.
expanduser.cmake
for CMake expands the ~ tilde character to the user home directory on all operating systems, including Windows.
As a CMake project grows, increasing complexity can make it hard to discern what tests are to be run and their properties.
Perhaps the project logic is unexpectedly omitting necessary tests.
The CI system or human can verify the list of tests by:
ctest -N
For machine parsing and human-readable verbose details including fixtures and labels, output
JSON:
ctest --show-only=json-v1
To ensure an accurate test list, the project must first be configured and built as usual:
In many cases, using the Unix-type slash file separator / will work even on Windows.
Trying to manually specify backslash Windows file separator \ can cause problems in CMake and many other languages.
Thus in CMake and other languages like Python, we always use / as path separator, and only transform to backslash for the rare cases it’s needed.
That switches backslash \ file separators to Unix slash / file separators.
This becomes relevant if manually adjusting Include paths by appending to lib_INCLUDE_DIRS or similar.
If backslashes sneak through, unexpected build-time errors can result, and even configure-time errors with “check_source_compiles()” and similar.
As the docs note, put
quotes"${mypath}" around the variable expansion to ensure CMake doesn’t mangle the path.
Transform to
native file separator
is generally more rarely used.
CMake can transform paths to native file separator, with the caveat that this can cause unpredictable Windows-specific backslash problems, as with any program.