reaper_plugin_functions.h is not kept up-to-date

[cfillion]

The copy on this repository hasn't been updated in 3 years and is missing newer functions such as realloc_cmd_register_buf.

It would be useful if the SDK was always kept in sync (eg. automatically) with new REAPER releases, so that it's easier to pull fresh headers with git (versus having to manually generate it from the GUI REAPER action and maintain a local copy of that file).

[eureka-cpu]

I have a project I'm working on that will create direct mappings of the ReaScript C/C++ API bindings for Rust, similar to reaper-rs, but only for functionality that ReaScript can provide. I'd like to also include this SDK, or possibly even make a crate just for it that will work in tandem with the ReaScript crate. Would anyone mind pointing me in the direction of how to generate the header files from a Reaper instance? Are all files in the SDK generated that way? Thanks in advance.

[cfillion]

Run the "[developer] Write C++ API functions header" action to generate reaper_plugin_functions.h for the current REAPER instance (optionally including extension-provided functions as well). (The other headers are hand-written.)

[eureka-cpu]

Run the "[developer] Write C++ API functions header" action to generate reaper_plugin_functions.h for the current REAPER instance (optionally including extension-provided functions as well). (The other headers are hand-written.)

Thanks so much. That makes things a bit easier. I'll work on a way to get that header file auto generated and open a PR.

[eureka-cpu]

Just a quick update: I have the code to automate getting the header file from reaper via the command line, and I'm currently working on automating pull requests to this repository when a new reaper version becomes available.

[eureka-cpu]

Okay, I now have everything automated. The header file will be generated and a pull request opened when a new reaper version becomes available on the download page.

[eureka-cpu]

@justinfrankel would you mind reviewing the PR linked to this issue? Quite a lot of work went into figuring out how to automate this, it would be greatly appreciated from our small team https://github.com/Cloud-Scythe-Labs

We are almost finished with the MVP of an extension plugin that enables cloud collaboration for reaper, so anything we can do to make building plugins easier for the entire community we're happy to contribute to (:

[eureka-cpu]

@cfillion it seems that this repo isn't checked on very often so we may just go ahead with a community fork we'll maintain on our org (unless there's some other fork we should contribute to instead). We'll have it auto sync so that when this does get updates the fork will also get them, but the reaper_plugin_functions.h will always be up-to-date with the latest release.