You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@zicklag ... while I have you here maybe you can answer something for me? What is the plan with regards to handling bindings for multiple c++ classes in the same project. The idl file in the sample is called point.idl presumably because the only thing it handles presently is the Point class but if I wanted to add a class (different header and implementation file) would I just append it to the same .idl file? And if so I suspect I will have to handle it somehow in the makefile? Perhaps make is a bit light for a larger workload if that's the case? Perhaps the work presently being done by make should be handled by a webidl executable? I'm not sure what the long term goals are for this project but it looks like something that I would like to make more industrial use of than just a few samples...
but if I wanted to add a class (different header and implementation file) would I just append it to the same .idl file?
Yes. All of the definitions that you want to go into the Haxe module would go into the same WebIDL file.
And if so I suspect I will have to handle it somehow in the makefile? Perhaps make is a bit light for a larger workload if that's the case? Perhaps the work presently being done by make should be handled by a webidl executable?
Yes, you would want more automation for that that this library doesn't currently provide. I'm actually using this library to automate C++ bindings for Kha projects. Kha has its own make system called Khamake, and I have recently submitted PRs for Khamake and Kha that completely automate the whole binding process.
For any other users of this library, though, a setup for automating the make process for other applications would be useful. What I setup was very specific to Kha, but you could still check it out at armory3d/haxebullet#25 (comment).
Originally posted by @WolfieWerewolf in #13 (comment)
The text was updated successfully, but these errors were encountered: