Fix: register VarTools LibraryObject in Cpu.sw to fix broken publish#15
Merged
sclaiborne merged 2 commits intomainfrom Apr 30, 2026
Merged
Fix: register VarTools LibraryObject in Cpu.sw to fix broken publish#15sclaiborne merged 2 commits intomainfrom
sclaiborne merged 2 commits intomainfrom
Conversation
Without these <LibraryObject> entries, AS6 builds the static archive (libVarTools.a) but does NOT generate the loadable runtime module (VarTools.br). The publish workflow then ships a tarball missing .br files, and downstream consumers fail at build time with 'error 427: Needed module vartools ... not installed'. Also expanded the ARM Cpu.sw from <SwConfiguration .../> self-closing to a proper structure with TaskClass#1-8 and a Libraries block, since without the expansion there's nowhere for the LibraryObject to live. Builds Intel + ARM clean (only the benign 447 licensing warning).
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
1 participant
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.
What
Adds a
<LibraryObject Name="VarTools" .../>entry to bothCpu.swfiles (Intel + ARM). Also expands the previously self-closing<SwConfiguration .../>ARM Cpu.sw to a proper structure (TaskClass#1-8 + Libraries block). Adds a missing stringext LibraryObject too (also wasn't registered).Why
@loupeteam/vartools@1.0.0was published missing all.brfiles (onlylibVarTools.afor ARM). Downstream consumers (Chopper, OMJSON, OMSQL, Chopper, atn, etc.) fail at build time witherror 427: Needed module vartools of required range from 1.0.0 ... not installed.Root cause: without the lib being developed registered as a
<LibraryObject>in the configuration'sCpu.sw, AS6 compiles the lib's.abut doesn't include it in the configuration's runtime image, so no.bris generated. The export-as-library action then ships only the.a, producing a broken tarball.This is the same class of bug as LogThat#5, but the trigger is different (incomplete
Cpu.sw, not wrongLIBRARYenv var).Verification
After this change,
Temp/Objects/Intel/.../VarTools.brandTemp/Objects/ARM/.../VarTools.brare both produced. Intel + ARM builds clean (only the benign447licensing warning).Follow-up
Once merged:
@loupeteam/vartools@1.0.0GitHub Package version (manual, requiresdelete:packagesscope)build-export-publish.ymlworkflow with versionv1.0.0to republishRelated
UPGRADE_TO_AS6.mdstep 7c now requires this LibraryObject entry for all migrations going forward