Skip.tools
Upgraded skip to 1.1.8 - but still see logging ref to 1.1.1 #256
-
|
I'm still not able to re-build my project... Should be upgraded to 1.1.8 ❯ 1.1.8/skip.artifactbundle/macos/skip version But when I run > skip export and look at the /tmp/**** log files I see: Error: The skip.tools license was created with a version of the software that expired on 2024-10-01 00:00:00 +0000 and must be re-generated. Which I was getting BEFORE the Xcode : File > Packages > Update...version - which I thought it worked... Xcode builds started working. But > skip export fails. ❯ skip version ❯ skip export Find ref to skip 1.1.1 and errors with license file... skip-export-2024-10-08T01:24:07Z.txt Seems WEIRD that I've got 1.1.8 but the log file does NOT - it's 1.1.1 - how do I debug this? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 14 replies
-
|
Here's something WEIRD... after deleting the .build folder several times - and rebuilding... ❯ pwd Down inside that .build folder so thing copies in the skip command and it is version 1.1.1 Not 1.1.8 !!! So some where in the Gradle build there exist a cached 1.1.1 Skip tools that is being copied into the projects/.build/artifacts.... Riddle me ... this one Batman... |
Beta Was this translation helpful? Give feedback.
-
|
this was command line...
deleted Package.resolved and reran skip export. Same 7 errors |
Beta Was this translation helpful? Give feedback.
-
|
should I have done a Xcode File Package Update? I've no idea what the Package.resolved is a signal flag...??? |
Beta Was this translation helpful? Give feedback.
-
|
Here's a PDF of Package.resolve - I noticed version 1.1.1 in it. |
Beta Was this translation helpful? Give feedback.
-
|
That's the new Package.resolved or the old? Can you run "swift package update" and see if it updates to the latest versions? Or is you Package.swift file pinning to certain versions? |
Beta Was this translation helpful? Give feedback.
-
|
That's the newly created Package.resolved file - I guess the result of a > skip export command. The Package.swift file pinning??? Don't know the meaning of that... but the XML starts with "pins" 
|
Beta Was this translation helpful? Give feedback.
-
Xcode shows skip 1.1.8 Package.resolve deleted and reRan Xcode File > Packages > Update... Then > skip export - command line No luck there ... looking in Package.resove (AFTER deleting it ) see Skip ver 1.1.1 !!! Still. { |
Beta Was this translation helpful? Give feedback.
-
|
Here is Package.swift - noticed a ref to 1.1.1 in it line 17. ❯ vi Package.swift 1 // swift-tools-version: 5.9 |
Beta Was this translation helpful? Give feedback.
-
|
Not knowing what I'm doing but on a lark... updated the version # in Package.swift to: And builds are looking Good, BETTER... Built!! ❯ ls let package = Package( ❯ |
Beta Was this translation helpful? Give feedback.
-
|
That little update of version #s in Package.swift HELPED a lot. !!! Yet the issue is - who/when does Package.swift get updated... and I keep saying (to the wind) this tool chain needs a good CLEAN command! |
Beta Was this translation helpful? Give feedback.
-
|
Xcode and SwiftPM's command-line interface don't use the same pins. Xcode's is internal, whereas the CLI uses the I agree that this is confusing. We will consider ways to call out when the package may be out of date. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the explaination - this helps! I think I'm coming to a fuller understanding of the issues. I've got two platforms, one code base, but two build tool chains. Double the FUN! Double the disFUNtion :( especially when I don't understand the workings. I looked up what PINS could mean... Is there a known way to get the two build chains into sync? |
Beta Was this translation helpful? Give feedback.
-
|
Thinking that advice for problems that are something like - delete Package.resolved are indications of the system of dependencies getting out of sync... a good old fashioned way of resync-ing was to CLEAN and rebuild... but there is no CLEAN. And I'm unsure of where the build process actually starts. Is it build in Xcode? Or is it skip export? Or something else? the more I learn the more I'm amazed that it all works! At least sometimes! |
Beta Was this translation helpful? Give feedback.
-
|
I just reviewed the https://skip.tools/docs/update-guide/ Update Guide... 
|
Beta Was this translation helpful? Give feedback.
-
|
That command appears to create / update the Package.resolved file (timestame coordinates ). But then the Update Guide has us manually editing the Package.swift file to change version #s. Is this a MANUAL step in the resyncorization of the TWO build chains? Or is it recreated/updated by some process? |
Beta Was this translation helpful? Give feedback.
-
|
Let me point out that after getting builds working again... the issues I feel contributed to MY confusion and many mistakes I've made... My ignorance of the two build tool chains. (A BIG problem) The need (requirement) to update the two build tool chains. (I'd not done this since ver 1.1.1 some months back) The strange fact that some process copies executables that are installed in HomeBrew into the hidden project folder (.build/artifacts/skip...) and uses that absolute path to skip executable to build. Which is a redundant skip exe that got out of sync with the properly installed skip exe. This redundancy should be eliminated in the build tool chain. Oh... and the weird reasoning that there is a HIDDEN (.build) folder in the first place. Just BAD form for a build system to hide it's work. The build system does NOT have a proper CLEAN tool/command. The consumer (ME) does not know which pieces of this are generate/derived files and what is source data. The build system and tool chain copies in unix paths and then uses the absolute path to execute commands or as parameters (input) to commands - as apposed to using a relative path - or a well known Env Var (oh how I hate the JAVA_HOME Env Var) but it does solve for this issue. I put this here to help make Skip.tools better in MY future! |
Beta Was this translation helpful? Give feedback.
Xcode and SwiftPM's command-line interface don't use the same pins. Xcode's is internal, whereas the CLI uses the
Package.resolvedfile. This can indeed be confusing, because Xcode might be using one version of the libraries (after you update usingFile/Packages/Update to latest package version), whereas command-lineswiftmight be using another (which won't be updated until you runswift package update, or just delete thePackage.resolvedfile).I agree that this is confusing. We will consider ways to call out when the package may be out of date.