appleide wrote:made LOVE with your friend mike
Oh, the puns. You've seen the
pun thread, right?
appleide wrote:It's not going to compile for Linux.
Not with those makefiles, no. I was referring to the source code.
Oh, and if you want to make XCode project files, that would be awesome too. (But that's up to you).
appleide wrote:Also I want to ask something.... There's different 'modules' for LOVE right? So are we going to place them in the LOVE folder, or put them in the user's preferences folder so when they upgrade they keep the modules ? Either would be okay. I would just go with windows for now because LOVE would update heaps and might break compatibility with those modules every several versions?
The .dylib modules should be placed in the LOVE folder, if it is common to do it that way in MacOS. Like you said, using arbitrary versions will break compatibility at some point.
appleide wrote:There seems to be currently a different scheme for windows and linux... so I am not sure.
In Windows, it's (fairly) common to put .dlls in the installation folder. On Linux, it's (supposedly) common to put them in /usr/lib/<appname>, if installed properly.
The different "schemes" are just these:
- In Windows, modules are assumed to be in the same folder as love.exe.
- In Linux, modules will be loaded either from the same folder as the love binary, or from /usr/lib/love. (Checked in that order).
In any case, it was never the intention that user should update these modules themselves, so keep them out of preferences/home folders.
8-)