4 ms·
Try something like this? fcsh-wrap -static-link-runtime-shared-libraries -benchmark=false -debug=false -o tmp.swf -source-path=src -library-path+=lib/as3-sig
by auriplane 5y ago
Try something like this?
fcsh-wrap -static-link-runtime-shared-libraries -benchmark=false -debug=false -o tmp.swf -source-path=src -library-path+=lib/as3-signals-v0.8.swc -- src/core/Main.as
It almost builds for me, but I think since my Flash projects were older than yours my copy of the Flex SDK might be too old.
- mst 5y agoI dearly hope something along these lines works, especially given the author has a repository and thinks the last set of optimisations may have been what introduced a bunch of the current bugs - if that's so, backing out those patches and relying on modern machine's performance to make the optimisations not matter might work out really nicely. Yeah, I'm being hopeful from a complete lack of expertise here. But it'd still be -really- cool if it worked out.
- auriplane 5y agoIt turns out it does build with a newer Flex SDK, but all I get when I run the resulting .swf is a grey screen.
- auriplane 5y agoThe grey screen thing, it turns out, is just because I didn't run the .swf from the bin/ directory. It runs just fine once I put the output file there! For what it's worth, I built it with 4.6.0 of the Flex SDK, which Adobe is still hosting: https://fpdownload.adobe.com/pub/flex/sdk/builds/flex4.6/flex_sdk_4.6.0.23201B.zip https://fpdownload.adobe.com/pub/flex/sdk/builds/flex4.6/fle... So yeah, problem solved, I guess?
- devtailz 5y agoThanks for this. Just to confirm https://github.com/Draknek/fcsh-wrap https://github.com/Draknek/fcsh-wrap is what you are referring to? When I tried the Flex SDK I had troubles getting it configured and pointing to the correct files. I'll see if I can give this a try this evening
- mst 5y agoYou owe me nothing, of course, but I really want to know how this turns out now.