Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ios] libraries - pugixml missing? #8194

Closed
Tracked by #8192
dimitre opened this issue Nov 15, 2024 · 8 comments
Closed
Tracked by #8192

[ios] libraries - pugixml missing? #8194

dimitre opened this issue Nov 15, 2024 · 8 comments

Comments

@dimitre
Copy link
Member

dimitre commented Nov 15, 2024

/Volumes/tool/ofw/libs/pugixml/lib/macos/pugixml.xcframework:1:1 While building for iOS, no library for this platform was found in '/Volumes/tool/ofw/libs/pugixml/lib/macos/pugixml.xcframework'.

@ofTheo
Copy link
Member

ofTheo commented Nov 21, 2024

I think iOS is working now right @artificiel ?
Can we close this?

@artificiel
Copy link
Contributor

it's hard to say as there is no clear information on the context of where the reported error occurred.

FWIW xmlSettingsExample compiles and runs fine with of_v20241109_ios_release.

i do notice in the reported error path above the presence of /macos/ maybe the encountered error is related to path libs "exploration"? again lacking context to ensure.

@artificiel
Copy link
Contributor

artificiel commented Nov 21, 2024

following up on iOS testing, i noticed that all projects relying on subfolders (for .h or other ressources) are broken as distributed (ex: assimpExample iosExternalDisplayExample iosNativeARCExample iPhoneGuiExample) as the provided project does not include subfolders.

running the bundled PG (0.83.0) over them restores things.

i don't know how the iOS project files are generated for release but it seems to run incorrectly as far as /src processing goes

[edit to add: maybe this warrants another issue but maybe it's trivial]

@ofTheo
Copy link
Member

ofTheo commented Nov 21, 2024

@artificiel @dimitre
Sounds like we need to be using the same PG in the CI that's been shipped ( 0.83.0 ).
We should check the actions and see what PG version is being used .

Was this in the nightly release @artificiel or the latest release?

@ofTheo
Copy link
Member

ofTheo commented Nov 21, 2024

Hmm the nightly is using 0.86.0 see:

projectGenerator exists...
PG building example projects
  [notice ] { "openFrameworks projectGenerator": "0.86.0" }
  [notice ] ofPath set and valid using ["/home/runner/work/openFrameworks/openFrameworks/out/openFrameworks_pkg_creation"]
  
  [notice ] -----------------------------------------------
  [notice ] updating an existing project
  [notice ] target platform is: ios
  [notice ] recursiveUpdate "/home/runner/work/openFrameworks/openFrameworks/out/openFrameworks_pkg_creation/examples"

Is this a regression with 0.83.0 to 0.86.0 ?

@artificiel
Copy link
Contributor

above testing was done in the context of #8192 with of_v20241109_ios_release which includes 0.83.0.

just re-checked with of_v20241121_ios_release which now includes 0.86.0, and it's the same: the delivered example projects do not include subfolders, but running 0.86.0 over them fixes it. so either a regression in PG (since at least a little while) or something related to command-line invocation or some other env condition of CI.

NB: "get info" on the PG app reports v 0.67.0:
image

@dimitre
Copy link
Member Author

dimitre commented Nov 26, 2024

Yeah once Dan added this info to "reflect" PG command line. but it got outdated soon.
I think they are two very different pieces of software, they should have independent versions.

@dimitre
Copy link
Member Author

dimitre commented Nov 26, 2024

I'm closing this one as I've downloaded the latest libs and worked OK

@dimitre dimitre closed this as completed Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants