jaskij

Now, the questions is, how do I test it? Since `cargo-pgx` must be in the same version as `pgx` required by the plugin being built.

@thomcc I primarily marked this as a draft to discuss the interface - mostly around what is passed as an argument, and what is passed as an environmental variable. Meanwhile,...

I have absolutely no clue why that one test is failing, but it seems to be misconfigured, especiall since on my PC (with PG15 installed via `cargo pgx init`) that...

A quick note on how to actually cross-compile with `cargo-pgx`, seems I forgot to post it yesterday. 1. Read [Thom's guide](https://github.com/tcdi/pgx/blob/develop/CROSS_COMPILE.md) 2. Additional requirements: -- host *and* target PostgreSQL (including...

As is, schema generation builds the extension for the host so that it can generate the bindings. This isn't a good solution, but is a workable one. Sadly, schema generation...

@thomcc I see that your work on cross compilation was merged, that's what created the conflict. Do you think there is something I should be looking into or integrating with?...

@thomcc conflict resolved. If you're working on update to `CROSS_COMPILE.md` already, my instructions are condensed in [this comment](https://github.com/tcdi/pgx/pull/981#issuecomment-1383113583). A cleaned up version of `pg_config_wrapper`: ```sh #!/usr/bin/env sh set -x TARGET_SYSROOT="/usr/local/oecore-x86_64/sysroots/cortexa53-crypto-poky-linux"...

Damnit, thought it was already formatted. Will do as soon as I'm at my PC.

@thomcc done.

I don't have the time or energy to get on this now, but might have it at the beginning of September, feel free to ping me then if I don't...