lime 2.0.0.0static linking: windows

[Mark]

hi guys,

New lime and openFL are out (yay :) and doc says for lime "Added support for static linking on Windows, Mac and Linux".

The question is: how? I did not find an option anywhere and I still have 'zlib.dll', 'lime.ndll', etc next to my exe so it's not an automatic static linking it seems.

[bonus question: anyone has a 'best practice' to "hide" asset folder and it's contents from user?]


Thank you in advance,
Mark

[Ian Harrigan]

Oh, nice... that is good news! Will be interesting to see if we can manage a single exe...

As for the assets, ive been using

<assets ... embed="true" />

with success... I only end up with about 5 files after that, none of which are assets.

Cheers,
Ian

[Mark]

It is there and available it says (just remove/add lime, "upgrade" doesn't work very well), but I didn't find switch/option/whatever to set it like that.

As of assets, thanks, I didn't know that! However, building the app like that results in "Custom([file_write,stderr])" error and app  closes. If I copy over the assets folder next to the exe, as if it would have done without embed param, all OK again (a bug, perhaps?)

[Joshua Granick]

The static binaries are not distributed with Lime by default. We need to come up with a good solution for balancing functionality with the file size of downloading updates.

To rebuild, you use "lime rebuild windows -static", static builds are not currently supported for Lime legacy, which OpenFL uses by default on native, unless you use the "-Dnext" flag.

Then you can use static by using "-static" when building, like "lime test windows -static"

--
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.

[Mark]

cool, thank you for the information!