What's going on with the Interop packages?
- Thread starter Ian JCV
- Start date
- Messages
- 9
- Reaction score
- 10
Hi Ian, I answered your question yesterday but for anyone else who stumbles into this thread:
Today we are taking the steps necessary to open source the BRUTAL framework. This includes all the packages we have that we think can help you build your own games in BRUTAL.
That doesn’t include all the source that we use internally to build the framework. We had a bug in our project files that caused the wrong README’s to be attached to the packages we released publicly today, but we’re working on rectifying that in a later documentation pass.
You can assume any package prefixed with “RocketWerkz” is private and not planned for release at this stage.
Today we are taking the steps necessary to open source the BRUTAL framework. This includes all the packages we have that we think can help you build your own games in BRUTAL.
That doesn’t include all the source that we use internally to build the framework. We had a bug in our project files that caused the wrong README’s to be attached to the packages we released publicly today, but we’re working on rectifying that in a later documentation pass.
You can assume any package prefixed with “RocketWerkz” is private and not planned for release at this stage.
Ian JCV
New Member
- Messages
- 2
- Reaction score
- 0
Thanks for taking the time, Rian! I was also hoping to leave a more public trace of the question/answer just in case, but since the README is getting fixed it's not going to matter too much.
I was super excited to see the libclang tooling, but looking at the package description I can at least vaguely guess how it works, and it's a super doable pipeline, just going to take a bit of time to replicate. I hope you guys aren't against maybe-maybe-not-FOSS recreations of those packages, are you? It seems like a great way to write a C++ low level core that gets called from a C# loop, kind of emulating Unity, but backwards.
I was super excited to see the libclang tooling, but looking at the package description I can at least vaguely guess how it works, and it's a super doable pipeline, just going to take a bit of time to replicate. I hope you guys aren't against maybe-maybe-not-FOSS recreations of those packages, are you? It seems like a great way to write a C++ low level core that gets called from a C# loop, kind of emulating Unity, but backwards.
