Page 3 of 4
Re: [HELP] .love --> .exe
Posted: Mon Jun 21, 2010 9:58 am
by thelinx
Could anyone upload a love.app folder so I can make some kind of automated script to generate one-click executables for all supported platforms?
Re: [HELP] .love --> .exe
Posted: Mon Jun 21, 2010 3:21 pm
by Luiji
Linux can go either way, as ".a" files can be embedded and ".so" files can be linked. It's often considered best practice to use ".so"s, since multiple programs can link to it thus saving space.
Re: [HELP] .love --> .exe
Posted: Mon Jun 21, 2010 4:44 pm
by bmelts
Re: [HELP] .love --> .exe
Posted: Mon Jun 21, 2010 10:25 pm
by Jasoco
The problem with that though is that once the file goes to Windows, it will become unusable because of the different file systems. Well, at least that's how it was in the 90's with the Classic Mac OS. It might still work. Apple has tried to move away from incompatibility, but I can't guarantee that the love.app will still work when transferred back over to OS X.
It's better for one of us Mac users to create a script to do it for us since the OS X version should not leave OS X. Just as the Windows version shouldn't leave Windows. If I had time, I might try it out. Again.
Re: [HELP] .love --> .exe
Posted: Mon Jun 21, 2010 10:43 pm
by Luiji
I've successfully made a Windows version in Linux and have had no compatibility problems, so your point is invalid.
There are certain programs that can read HFS+ file systems without converting the file-system, but they're hard to find and quite rare. If Apple truley wanted to move away from incompatability, then they'd either support alternative file-systems for reading such as EXT and NTFS or would release HFS+ drivers for Windows and Linux.
Re: [HELP] .love --> .exe
Posted: Wed Jun 23, 2010 12:11 am
by Jasoco
Luiji wrote:I've successfully made a Windows version in Linux and have had no compatibility problems, so your point is invalid.
No it's not. I was talking about making Mac versions on Windows. Not Windows versions. And I might even be wrong about it not working. I don't know for sure because I have never tried. I wouldn't trust it to work though without actually having the OS for testing it.
Re: [HELP] .love --> .exe
Posted: Thu Jul 08, 2010 1:32 am
by leiradel
I have a working packer for Windows that can pack love.exe + all dlls + the .love file into a single executable. When run, the executable will unpack everything yo a temporary folder, run the game, wait for it to exit and clean the temporary folder.
I've opened a topic to try to get a nice splash screen with a progress bar for the unpacker while it decompresses the files but got nothing. I'm willing to make binaries and source code available once I have the splash screen image. If anyone is willing to help I appreciate.
viewtopic.php?f=3&t=1428
Cheers,
Andre
Re: [HELP] .love --> .exe
Posted: Thu Jul 08, 2010 11:51 pm
by Luiji
Would you like it to be an animated splash screen image with one of those rotating arrows or something or something like that?
Also, the DLLs are separate due to some licensing weirdness, so embedding the DLLs should be optional, please.
WHERE'S THE SECRET SECRET!?
Re: [HELP] .love --> .exe
Posted: Fri Jul 09, 2010 1:17 am
by leiradel
Luiji wrote:Would you like it to be an animated splash screen image with one of those rotating arrows or something or something like that?
I was thinking of a progress bar, but the decompression is usually so fast that maybe rotating arrows or something like that would be a good choice.
Luiji wrote:Also, the DLLs are separate due to some licensing weirdness, so embedding the DLLs should be optional, please.
LGPL says you can't statically link the library to your code without making it LGPL or GPL. There's nothing against
packing them together with an executable. Otherwise, installers wouldn't be allowed to pack LGPL'ed DLLs...
Cheers,
Andre
Re: [HELP] .love --> .exe
Posted: Fri Jul 09, 2010 1:45 am
by Luiji
Good point on LGPL, but I'd consult some other users that have more experience with GPL software. Unless the libs can be modified by the user (i.e. by extracting them), then I think it voids users ability to upgrade the lib, as required by the LGPL (thus one of the reasons it is incompatable with iPhone and Wii).