That's because the "Test" program will appear in your platform's ndll/ folder when you use the "build.bat" or "build" script to compile it. The dll/dylib/so file has all of the actual Steam API functionality, and the ndll file allows your Haxe project to communicate with it.Īs for the steam_appid.txt file, it's only there to make the "Test" program work. The steam_api dll/dylib/so file must be next to your platform's steamwrap.ndll file in order for the extension to work. STEAMSDK_DIR/redistributable_bin/steam_api.so -> ndll/Linu圆4/ STEAMSDK_DIR/redistributable_bin/steam_api.so -> ndll/Linux/ Run setup.bat (windows) or setup.sh (mac/linux) and enter the values it asks you for.See steamwrap/example/Test.hx for a basic example. When you release your game on Steam, set this launch script as your executable, NOT the raw linux binary itself.An example (Test.sh) is provided in the example folder You will need a launch script to ensure libraries are loaded from the righ location.Make sure libsteam_api.so is sitting next to steamwrap.ndll.```openfl test windows -Dsteam -Dfinal``` (for instance) **Compiling with the "-Dfinal" flag should suppress creation of the steam_appid.txt** Make sure it's stripped during the publishing stage.** ![]() **This extension will automatically create a steam_appid.txt in your binary folder.**
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |