GTXiLib not building

[Mary Baptista Martinez]

Hi team,

I downloaded GTXiLib and the Xcode project doesn't build. The project shows some files missing; there is an empty Pods folder but no Podfile (see screenshot).

My goal is to build the project but not as a dependency. How could I use Xcode to build a binary to integrate that way?

Can it be built with Bazel?

I would prefer to use Bazel but could also pre-build the framework if that is possible. Any advice?

Thanks!

Mary

[Mary Baptista Martinez]

Hi team,

Just wanted to follow up on this. Is it possible to build GTXiLib with Bazel? If so, how?

Thanks,
Mary

[Cooper Knaak]

Hi Mary,

Sorry for the delay. GTXiLib only supports building via CocoaPods. Bazel and other package management systems are not supported, nor is building directly from the Xcode project in GitHub. That Xcode project is a legacy file, which is why it contains references to Pods despite not being a CocoaPods project.

What is the goal of building it directly, not as a dependency? If you want to do local development on GTXiLib or test local changes, the easiest way is to

• clone the project to your local machine.
• create a simple iOS app project in Xcode.
• Write a Podfile in that project to use CocoaPods.
• Install GTXiLib using `:path => "/path/to/local/GTXiLib", which will pull the cloned repository with all its changed, instead of the remote repository.

Sincerely,

Cooper Knaak

[Mary Baptista Martinez]

Hi Cooper,

No worries, thanks for the prompt response today!

The goal of building it directly was to use it with our internal tooling in CI. Basically we place a .framework in the cloud somewhere and grab it when needed, hence needing the ability to build GTXiLib as a standalone framework.

Since that is not an option, my team is going to try a mixed approach using Cocoapods for GTXiLib and Bazel for Abseil. 

We use Bazel internally and the issue I am hitting is with Abseil not finding header files used in GTXiLib. It works fine if using Cocoapods in a standalone project but trying to integrate GTXiLib into our flagship product with Bazel is proving to be challenging.

Mary

[Mary Baptista Martinez]

Hi Cooper,

I have a follow up question: what is the version/commit of Abseil that GTXiLib depends on?

When I try to look at the podspec in cocoapods, there isn't one. https://github.com/CocoaPods/Specs/blob/master/Specs/[%22a%22,%20%225%22,%20%228%22,%20%22GTXiLib%22,%20%3CPod::Version%20version=5.1.2%3E]/GTXiLib.podspec.json

Still trying to get the source built but missing some info 😅

Thanks,

Mary

--
You received this message because you are subscribed to a topic in the Google Groups "ios-accessibility" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ios-accessibility/21zPqflfDtg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ios-accessibil...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ios-accessibility/3360ee15-1ffd-4e74-b93a-fff8f47ac92an%40googlegroups.com.

[Cooper Knaak]

Hi Mary,

No problem. Weird, looks like CocoaPods doesn't parse the link correctly. The actual podspec is https://github.com/CocoaPods/Specs/blob/master/Specs/3/8/6/abseil/1.20230125.3/abseil.podspec.json. Looks like it uses tag 20230125.3 I just tested it locally, and GTX successfully built, ran, and detected issues with the most recent build of Abseil in CocoaPods, which should be 20230125.3.

Abseil has a "build from HEAD" philosophy, so in theory, any commit should work. But CocoaPods is only going to pull whatever version is specified in the podpsec, which is as above.

Let me know if you have further questions!

Sincerely,

Cooper Knaak