to ive guidance on project structure i think one needs to know a bit more about what you intend to do.. do you want to generate code in a runnable jar, gradle plugin, idea plugin ?

either way it would make most sense to have your code generation all in one gradle subproject and reuse it for gradle plugin and runnable jar

gradle plugin? For code gen?

write the code in eg

build/generated-src/main/kotlin

and register it as source root

Instead of shipping the generated library.

i would probably make a gradle plugin in

buildSrc

and use it to generate the library

I'll look into making a gradle plugin subproject then.

it genertes some stuff but is not completely what you need

and here is a better plugin example.. it registers multiple source folders, the selected lines ensure that kotlin and idea plugins are applied: https://github.com/DaemonicLabs/Voodoo/blob/master/plugin/src/main/kotlin/voodoo/VoodooPlugin.kt#L26-L27

it calls poet outside of anu task, that mkes it execute every time the plugin is applied, eg. on every build

i hope you can puzzle together something useful 😛

if not it can go into

buildSrc/someSubProject

is the project public anywhere ? is the codegen part is working i could try to PR the gradle plugin stuff

The project is public but I've only just started the codegen bit,

It's here https://github.com/Dominaezzz/kgl, I'm planning on adding a

kgl-opengl

subproject that'll depend on the plugin in buildSrc.

because i think it might be easier to have just one root module in the main project

unless you plan to add other graphics wrappers

that way it is easier to move if you want to.. and seperate fro mthe plugin code and seperate from other codegen stuff you might add later

although they can surely depend on some shared 3rd module.. once you see similarities that can be factored out

There will be a lot of similarities.

Will splitting them into separate modules give me anything. I was planning on having two packages in the same module.

basically buildSrc on its own can be a normal gradle project, but because itsnamed like this and placed correctly it will be used i nthe build process of another gradle project

nothing much, except seperation of concerns

in buildSrc ? i think so.. add application plugin,

application { mainClass = ".." }

and you should be able to run any tasks on it

did you know idea can even manage multiple gradle projects at once ? in my case i have a samples subdirectory that applies the plugin from mavenLocal() for testing purposes

I forgot one can stick a top level main function anywhere and IntelliJ will offer to run it.

is there anything holding kgl back on gradle 4.10.2 ? gradle 5 would make it a bit easier to configure some things

so i have successfully split this up in 2 tasks.. one to download the xml and the other one generates the source

problem is now triggering that task before the kind of compile you want.. this one seems to only do mingw generation, thats windows right ?

is there different things to be performed for jvm, js and native ? then you can create different tasks and have those call common generator code the different tasks are then gonna make sure the

jvmMainClasses

,

jsMainClasses

and whatever native uses are dependent on them its not a problem to set up, i am just not sure how its gonna be and i am on a linux laptop so the windows mingw stuff is not being set up for me i think

if it is just always the same code then you might as well just make it a function thats not part of a plugin and call that with the generate-src and whatever other arguments