Closed aglitchman closed 10 years ago
Ok, sorry about the delay but I finally got around to taking a look at this.
It makes a certain amount of sense, but I'm a bit confused about how BRL_MAKE_META_IMPLEMENTED could be defined elsewhere?
Are you talking about an entirely new target that defines this in its modules/monkeytarget.monkey file and imports the appropriate native code? Sort of the way targets can define BRL_GAMETARGET_IMPLEMENTED etc?
Or are you talking about a 'plain' module somewhere, in which case, an 'import' would need to be added to transcc - in which case, why not just add the native makemeta code to transcc directly?
Or am I completely missing the point?!?
The other option is to convert makemeta.cpp to monkey, which should now be possible due to filestreams - or are you thinking about target without filestreams? This option sounds good to me...
The meaning of this pull request is that now the implementation of makemeta is only available for C++. If Java_Tool or C#_Tool platforms were created, transcc would be impossible to compile to C# or Java. If you will manage to rewrite makemeta to Monkey, it solves all the problems.
Thank you!
This pull request allows building transcc on targets other than "C++ Tool".