Configuration support evolves - 1/n

[Binlogo]

Roadmap: #7 (comment)

• Evolve configuration:
  • 👉 Support standalone xcframework.toml config file together with [package.metadata.xcframework] table
  • Support pre-build hooks. e.g: to generate headers (.h) or module map files.
  • Support custom-build options. e.g: to allow running user-defined build jobs.

• legacy(v1) config format seamless support.

[akesson]

I'm already looking forwards to this PR 😄

One thing: I don't think the "legacy config format seamless support" is really important. The project is in alpha which basically signals that these types of changes are likely. Instead focus on making changes that makes sense

[Binlogo]

I'm already looking forwards to this PR 😄

Thanks for your encouraging words. I will continue working on this PR during my spare time until it's ready. If you have any concerns or suggestions, please feel free to share them.

One thing: I don't think the "legacy config format seamless support" is really important. The project is in alpha which basically signals that these types of changes are likely. Instead focus on making changes that makes sense

Agree, this is a lower priority, but for "legacy config support" or in other words, "the simple configuration in its early stages and straightforward use case", I'm considering extensibility and simplicity balance.

[akesson]

Hey @Binlogo. Do you think you'll keep working on this? I'll do some changes myself now but they'll surely conflict with the ones in this PR.

[Binlogo]

Hey @Binlogo. Do you think you'll keep working on this? I'll do some changes myself now but they'll surely conflict with the ones in this PR.

Oh, I almost forgot. 😶 My focus has shifted, so I might return to this later. For now, I won't be able to continue in the short term. Please go ahead with your changes, and I'll handle any conflicts or redo them if necessary.

[akesson]

Sure. You are welcome back anytime you want 😄