Jorijn van der Graaf
46082a3117
crafter-build is moving to a single Flatpak distribution, and there is no Windows host in that picture: no build.cmd, no MSVC or mingw host build, no DLL plus launcher. Delete every host-Windows path instead of leaving it to rot unverified: the cmd.exe command runner and quoting, the LOCALAPPDATA cache, the MSVC and mingw-host LoadProject variants with their LIBCXX_DIR and CRAFTER_MINGW_DIR plumbing, the winsock port probe, the LoadLibrary libclang loader, the console-width and isatty shims, and the preprocessor guards around the Linux bodies. The x86_64-w64-mingw32 cross-compile target stays. It is target logic (output names, -femulated-tls, the libstdc++ link extras, copying a dependency DLL next to a mingw exe, wine as the runner) and did not depend on any of the removed code. The msvc target goes with the host that was the only thing able to use it. Three target-path warts fixed on the way: ExpectedOutput named a mingw static library <name>.lib while the archive step wrote lib<name>.a, so those libraries relinked on every run; the import lib is no longer copied next to a mingw exe, since the dependency's own bin dir is already on the link line; and llvm-ar now writes every archive, not only the LTO ones, so Debug and Release archives are made the same way. CRAFTER_API and Crafter.Build-Api.h existed only for the DLL boundary. Nothing downstream used them, so they are removed rather than kept as an empty macro nobody can verify. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
24 lines
1,008 B
C++
24 lines
1,008 B
C++
// SPDX-License-Identifier: LGPL-3.0-only
|
|
// SPDX-FileCopyrightText: Copyright (C) 2026 Catcrafts®
|
|
|
|
#include <cstdio>
|
|
#include <unistd.h>
|
|
|
|
import std;
|
|
import Crafter.Build;
|
|
|
|
int main(int argc, char** argv) {
|
|
// Line-buffer stdout when it is not a terminal. Must run before any stdout
|
|
// write. When stdout is a regular file or pipe the C runtime defaults to
|
|
// full (block) buffering, so the append-only progress lines ("[N/M]") and
|
|
// the trailing "Built … steps" / "listening on port …" lines would sit in
|
|
// the buffer and never reach a redirected log — fatal for tooling that
|
|
// polls the log for a readiness marker, and worst under -r where the
|
|
// process blocks in its serve loop and never returns to flush. A TTY is
|
|
// already line-buffered and its in-place redraw path flushes explicitly, so
|
|
// only adjust when redirected.
|
|
if (isatty(STDOUT_FILENO) == 0) {
|
|
std::setvbuf(stdout, nullptr, _IOLBF, 0);
|
|
}
|
|
return Crafter::Run(argc, argv);
|
|
}
|