tobil4sk

This file exists to avoid issues like this: https://github.com/HaxeFoundation/hxcpp/blob/master/include/hx/Undefine.h You'd have to do some more debugging to figure out what's messing up the include order and making it so that...

Similarly, this example breaks dynamic library builds with the compile cache on windows: ```xml ``` ``` Link: lib.dll LINK : warning LNK4001: no object files specified; libraries used LINK :...

> I don't want to change that because anything returned by haxelib should be inserted at the location of the corresponding -lib argument. If we instead collect all haxelibs and...

> find_subsequent_libs merely collects all immediate groups of -lib A -lib B -lib C to reduce the number of haxelib calls. This should not affect argument expansion order unless haxelib...

How about this: 1) Haxe expands all hxml files 2) Once all `-lib` flags are known, all libraries are passed to haxelib to be resolved in a single call 3)...

> I think that would still not be a general solution because a -lib can lead to more -lib after the haxelib call. `-lib` flags shouldn't really go in `extraParams.hxml`,...

To reiterate, these are the reasons why I would recommend against client side hashing: - Client side hashing leads to overall worse security, because it delays security changes. Any changes...

I think this may be something that will require some work in haxe/neko (or potentially whatever target haxelib is migrated to) to solve: https://github.com/HaxeFoundation/haxe/issues/3122

What was your current version of haxelib when running into this problem?

Looks like hxcpp doesn't support FreeBSD currently: https://github.com/HaxeFoundation/hxcpp/issues/277