The Love Distrubution Pack

[DhruvCollins]

hello guys lets find solution to dll problem!!!! we will call it love distrubtonr pack

plan
zipper . it load zip and is 100 percent complete beta
detector . it will detect false zip and delete otherwise wiruzz corrupt

100 percent complete

[T-Bone]

This sounds good, but I have a few questions:

1. If the zipper and detector are "100% complete", why are you calling them "beta"? Sounds like a contradiction to me.
2. Any advantages over a single line .bat file (other than not having to distribute the .dll files)? For example, will the end user get the same security warnings when building using this method?
3. Is it legal to pack the .dll files into the .exe? I think they're distributed separately because of their licensing, but I can be wrong (distributing a .app for Löve seems okay, so I'm not really sure how this works).

[DhruvCollins]

yes brother the problem is big

[DhruvCollins]

Well the DLL(S) Used in love except
1.msvcr120.dll
2.msvcp120.dll
are very less likely to have a conflict but wii will do this together brother do not worry

[Nixola]

I am not sure you should do this. Libs with that name would probably be used by whatever includes them instead, which is not good.

[DhruvCollins]

@Nixola i sent u the answer in PM
UPDATE: Im going to upload EXER in some time and till i find a solution im going to supply a Redist.exe with all the LOVE DLL(s)
Which Devs can package with thier games and people also will not need to downoad the extra 6 MB of DLL(s) again
and again.
NOTE: Currently EXER only can make the *.love file to *.exe
NOTE: Please Post your suggestions..

[Nixola]

You should also not answer me in a PM, especially because I did say I am not sure about this, as I do not know much about folders priority or what is usual behaviour with libraries on Windows.

Well the DLL(S) Used in love except
1.msvcr120.dll
2.msvcp120.dll
are very less likely to have a conflict...

[Positive07]

On another note, DLLs are not built into LÖVE because of their license, I think OpenAL is LGPL and if you include it you should make your software use that license or similar, this happens with many of the bundled libs

[DhruvCollins]

contact me at my skype we will make a chat brother

[Positive07]

License files are not the problem! but the terms of those licenses.

LGPL states that when you use code licensed under the terms of this license all the modifications and additions made to the code should be under the same (or compatible, that is, Open Source) license, since you are combining a library under the terms of this license with your own game you should then distribute your game under this same license, which means you should open source your game and distribute it's source code.