Force unimported hx file to be compiled on the cpp target

[Rui Campos]

Hi,

This is a cpp specific question, I'm not sure what the behaviour is in other targets.

How do I force a hx file to be compiled by haxe when that file is never imported or referenced? By compiling I mean that the file gets generated to cpp, and then appears on the Build.xml. I read about the macros keep, include, etc.. I tried them out but was unsuccessful, maybe I'm doing something wrong, still it would be cool to have some tips! :)

Thanks!

[Luca]

This isn't a c++ specific question :)

Just add the file name to the compiler arguments.

haxe File.hx ... other args

will include File.hx in the compile.

[Hugh]

Hi,

You need to refer to the file - so either on the command line as suggested, or "import" it.  If it is like a bunch of plugins, probably easiest to import all the plugins together from a single "PluginManager" that you know will be linked in somehow.

Then you will need to  @:keep all the plugin classes, so the dead-code-elimination does not remove them.

Hugh

[Juraj Kirchheim]

I would add that the extension is optional. You can just `haxe path.to.Module`.

> --
> To post to this group haxe...@googlegroups.com
> http://groups.google.com/group/haxelang?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Haxe" group.
> For more options, visit https://groups.google.com/d/optout.

[Rui Campos]

Damn! Can't believe it was that simple... Guess that's what you get when you start hacking into an existing complex system, and don't properly study the basics :) 

Thanks!