March 9Mar 9 Native Script Auto CompilerOne Command to Build & Download Your ScriptDownload: Click Herelast updated: 04-13-2026 (v1.2.2)Update Logv1.2.2- Generate minimal workspace Cargo.toml with only the script being built and dependencies folder - Prevents build failures when workspace Cargo.toml references projects that no longer existv1.2.1- Fixed error detection: Added catch-all error pattern to catch cargo workspace errors like "error: failed to load manifest" - Previously only matched specific error patterns, causing silent failures for cargo-level errorsv1.2.0- Build log verification — After rebuild completes, automatically downloads and scans the build log for compilation errors - Prominent error display — Shows a big red BUILD FAILED block with all error lines when compilation fails - Clean failure handling — No more confusing success messages after failure; exits cleanly without noisy traceback - Automatic cleanup — Log files are always deleted after inspection, even on failures - File locking — Prevents multiple terminals from running builds simultaneously (cross-platform: Windows msvcrt, Unix fcntl) - Queue-aware waiting — If another build is running, displays a clear message and polls every 3 seconds until the lock is released - Automatic lock release — Uses atexit to ensure locks are cleaned up on normal exit, crashes, or Ctrl+C - Option 0 — Interactive menu now shows 0. Build ALL scripts at the top - CLI support — python osbot_auto_build.py all builds all scripts sequentially - Sequential processing — Each script goes through the full cycle (package → upload → rebuild → verify → download) before the next starts - Login once — Authenticates once and reuses the session for all scripts - Per-script sections — Clear headers like Building script 1/3: script_name when building multiple - Correct DLL download — Fixed bug where the most recently modified script was downloaded instead of the one actually built (e.g., selecting thieving but getting magic) - Added version constant VERSION = "1.2.0" displayed in the configuration header as OSB Builder Automation v1.2.0v1.1.0- Added file lock mechanism to prevent concurrent instances - Added "Build All" option (0) to run all scripts sequentially - Fixed an issue with credentials on Windowsv1.0.0- Initial release--- WHAT IT DOES ---Run one command and it will:- Package your script + dependencies + Cargo.toml into a ZIP- Upload it, trigger a rebuild, and wait for it to finish- Download the compiled DLL into compiler/downloads/- Clean up the temp ZIP when done--- SETUP ---1. Extract the compiler/ folder into your project root (same level as Cargo.toml): my_project/ ├── Cargo.toml ├── script_dependencies/ ├── my_script/ └── compiler/2. Install Python 3 if you don't have it:Python Installation Steps - Windows: https://www.python.org/downloads/ (check "Add to PATH") - macOS: brew install python3 - Linux: sudo apt install python3 python3-venv3. Open a terminal in the compiler/ folder and run:Terminal Commands python3 -m venv .venv # macOS / Linux .venv/bin/pip install requests colorama python-dotenv # Windows .venv\Scripts\pip install requests colorama python-dotenv4. Copy .env.example to .env and fill in your credentials:.env Credentials USERNAME=your_username PASSWORD=your_passwordThat's it. Everything else is auto-detected.--- USAGE ---From your project root:Usage # macOS / Linux compiler/.venv/bin/python compiler/osbot_auto_build.py # Windows compiler\.venv\Scripts\python compiler\osbot_auto_build.pyIf you have multiple scripts, it will show a menu. You can also pass the name directly: compiler/.venv/bin/python compiler/osbot_auto_build.py my_scriptYour compiled DLL will be saved to compiler/downloads/.--- NOTES ---- Your source files are never modified or deleted- Works on Windows, macOS, and Linux- If a DLL already exists, it gets overwritten with the new build- Do not share your .env file — it contains your credentials Edited 19 hours ago19 hr by ProjectPact
Create an account or sign in to comment