fix: add curl to vitasdk toolchain to resolve curl/curl.h not found build failure#1
Merged
toaster-code merged 3 commits intomasterfrom Apr 1, 2026
Merged
Conversation
The build was failing with `fatal error: curl/curl.h: No such file or directory` because imagefetcher.cpp includes curlhttp.hpp which requires <curl/curl.h>, but curl was not downloaded into the PSVita cross-compilation sysroot. - Add `curl` to additional_libs in ci/conan-vitasdk/conanfile.py so that curl.tar.xz is downloaded from vitasdk/packages and installed into the vitasdk arm-vita-eabi sysroot alongside libvita2d, libpng, libjpeg-turbo, taihen - Bump package_version to ".1" (full version: 2.527.1) to invalidate cached builds and force the new package to be used - Update ci/conan/profiles/vita to reference vitasdk-toolchain/2.527.1 Agent-Logs-Url: https://github.com/toaster-code/pkgj/sessions/e7c36799-ae97-47d7-aaac-e2a12d62d4b1 Co-authored-by: toaster-code <148431+toaster-code@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Remove undesired files from repository history
fix: add curl to vitasdk toolchain to resolve curl/curl.h not found build failure
Apr 1, 2026
Adds .github/workflows/release.yml that triggers on v* tags and: - build-vita job: cross-compiles pkgj.vpk using Conan + vitasdk toolchain - build-host job: builds pkgj_cli and pkgj_sim using cmake + SDL2/curl - release job: creates a GitHub Release with all 3 artifacts named with the tag Also removes .github from .gitignore so the workflow files are tracked. Agent-Logs-Url: https://github.com/toaster-code/pkgj/sessions/c9bbaf1e-2ce6-4d7f-b777-82af07f4b455 Co-authored-by: toaster-code <148431+toaster-code@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
.githubfrom.gitignoreso workflow files can be tracked.github/workflows/release.ymlwith 3 jobs:build-vita: buildspkgj.vpkvia Conan + vitasdk toolchain on ubuntu-22.04build-host: buildspkgj_cliandpkgj_simvia cmake with system SDL2/curl on ubuntu-22.04release: creates a GitHub Release with all 3 artifacts named with the version tagactions/download-artifact@v4.1.3to avoid path traversal CVEpermissions: contents: readand job-levelpermissions: contents: writeon release jobOriginal prompt
I had to remove some undesired files from repository history (that i've added by mistake), and now i have this with github:
"This branch is 557 commits ahead of and 534 commits behind blastrock/pkgj:master." in github.
I think there is a mistake or something related to my fix, as the IA told me this:
⚠️ Avisos importantes
"
Reescrever histórico muda hashes de commit.
Tags antigas são regravadas (forçar tag push).
Faz backup antes (git bundle ou clone espelho).
Depois de filter-repo, qualquer clone antigo precisa ser re-clonado ou reset->hard.
"
O que aconteceu? é possivel ajustar?
[Chronological Review: The conversation began with the user requesting explanations and analyses of specific code segments in the file /root/pkgj/src/pkgi.cpp. The user asked about macros, namespaces, and specific code syntax, indicating a desire to understand the code's functionality and structure. The conversation evolved into discussions about threading, error handling, and the implementation of a logging system. The user expressed concerns about potential race conditions and the need for controlled thread management. The user also requested documentation for changes made in the code, adjustments to the logging system, and the use of curl for HTTP requests. The conversation culminated in the user asking about removing files from commit history and addressing issues with GitHub regarding commit discrepancies.][Intent Mapping: The user explicitly requested explanations of code segments, analysis of the entire file, and critiques of the code. They sought to understand threading management and error handling, specifically regarding HTTP requests. The user also wanted to document changes in the codebase and address issues with GitHub commit history.]
[Technical Inventory: The conversation involved discussions about C++ syntax, threading, mutexes, HTTP requests using curl, and Git operations. The user mentioned using SDL for texture management and expressed concerns about race conditions in threading. The user also referenced the need for a logging system that displays logs in reverse order.]
[Code Archaeology: The user referenced specific code snippets, including macros for loading JPEG files and managing textures, as well as functions related to configuration management. The user also discussed the implementation of a thread management system for downloading images.]
[Progress Assessment: The user has made progress in understanding the code and has identified areas for improvement, such as thread management and error handling. They have also documented changes and are working on resolving GitHub commit history issues.]
[Context Validation: All critical information for continuation is captured, including user requests for code explanations, threading management, and Git operations.]
[Recent Commands Analysis: The user requested to create a tag for the current version, remove undesired files from repository history, and address discrepancies in commit history with GitHub. The user expressed concerns about the implications of rewriting commit history and sought clarification on how to adjust the situation.]
1. Conversation Overview: - Primary Objectives: The user requested explanations of code segments, analysis of the entire file, and critiques of the code. They also sought to understand threading management and error handling, specifically regarding HTTP requests. - Session Context: The conversation began with code explanations and evolved into discussions about threading, error handling, and Git operations. - User Intent Evolution: The user's needs shifted from understanding specific code segments to addressing broader issues related to threading management and GitHub commit history.- Technical Foundation:
- C++: The user is working with C++ code, specifically in the file /root/pkgj/src/pkgi.cpp.
- SDL: Used for texture management in the code.
- Git: The user is managing version control and addressing commit history issues.
- Codebase Status:
- /root/pkgj/src/pkgi.cpp:
- Purpose: Contains the main code for the project.
- Current State: The user is analyzing and modifying the code for threading and HTTP request handling.
- Key Code Segments: Macros for loading JPEG files, thread management functions, and configuration management functions.
- Problem Resolution:
- Issues Encountered: The user faced potential race conditions in threading and discrepancies in GitHub commit history.
- Solutions Implemented: The user is working on a controlled thread management system and has made changes to the codebase.
- Debugging Context: The user is addressing HTTP request errors and ensuring proper thread management.
- Progress Tracking:
- Completed Tasks: The user has made progress in understanding the code and has documented changes.
- Partially Complete Work: The user is still working on resolving GitHub commit history issues and implementing thread management.
- Validated Outcomes:...
Created from VS Code.