Automatic generation of CMake exports about legacy HOT 4 CLOSED

Hello! This is planned as part of the Coven blueprint. Because IXM is still not even in alpha, different parts are focused on. I've had to take a break the last few weeks due to personal life stuff, while also working on the design of the documentation. I also have a local, (but not yet uploaded to github) list of issues that are required for the alpha release. :)

from legacy.

Thanks. I don't want to take up too much of your time but I was wondering why (atleast the Brujeria blueprint) is opposed to superprojects? It seems to assume the project itself is a single target. Is that a temporary state of the project? If so, I'll refrain from more questions. :)

from legacy.

Brujeria is supposed to be used in conjunction with the brujeria python library. In that instance, you treat each directory as a python module itself, and thus need an init.cmake. All of this integration is a bit of a ways off while I finish up some of the inner workings of IXM (Such as fixing unity builds, PCH generation, etc.)

from legacy.

Closing, as this project has burned me out, and I cannot continue working on it in its current state. CMake has changed massively since this project was started. Most of it is no longer necessary. A new repository will be launched in September.

from legacy.