Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - vlag

Pages: 1 [2]
16
Development / Re: Getting Started on a Mac
« on: April 13, 2015, 05:57:44 pm »
Hi,

Ok here is an exemple of what you have to do to unlock the situation :)

Actually, you just have to change a dependency path into the Solarus binary.
To do so, just open a Terminal (clic the glass on top right corner and type "Terminal"), and then copy/paste the following (I assume that the Solarus bundle is placed on the desktop and is named "Solarus.app", but you can change the following path if needed) :

install_name_tool -id @rpath/libluajit-5.1.2.0.2.dylib ~/Desktop/Solarus.app/Contents/Frameworks/libluajit-5.1.2.0.2.dylib
install_name_tool -change /usr/local/lib/libluajit-5.1.2.dylib @rpath/libluajit-5.1.2.0.2.dylib ~/Desktop/Solarus.app/Contents/Resources/Solarus

(I can't test right now, I'll edit this message if I did any typing mistake).


It should do the trick.

17
General discussion / Re: Distribution
« on: April 01, 2015, 12:40:16 pm »
I'm not very aware of licence's specification, but I thought that if you use a GPL software in a project and distribute it, whatever the relation is, you always have to make the source code of your project available.
I also thought that it was the reason why the LGPL was created.

So basically you can't distribute a quest as LGPL since its rules are less restrictive than GPL, which is the Solarus licence, except if you distribute it without any Solarus binaries and file (which is not very convenient for commercial use).


Am I wrong ?

18
Did you install SDL2_image and SDL2_ttf as well as SDL2 ?

If yes, you can place them into /Library/Frameworks , Solarus should be able to find them here.
In case, there is a french tutorial here which could help you, you can skip all bundle-specific part if you only wish to build the binary.

19
Bugs & Feature requests / Re: Crash with sol.main.load_file
« on: August 05, 2014, 08:10:17 pm »
I don't really think that it will work since the same code on ZSDX works fine, but if removing the timer from play.lua doesn't make the game crash, could you try to return a boolean from the timer function ?

Something like
Code: [Select]
sol.timer.start(100, function() return false end)

20
It's my fault, I forgot to change this path when we recently switched from lua to luajit.

In case, if you want to properly fix this before the offical correction, you can change the "id" of the dylib with
$ install_name_tool -id @rpath/libluajit-5.1.2.0.2.dylib libluajit-5.1.2.0.2.dylib

At this point, if you did this on the system library (the one in /usr/local/lib), the dependency path of luajit will be automatically copied from this id when compiling Solarus, but since it is not your case, you also have to change the path directly on the Solarus binary with

$ install_name_tool -change /usr/local/lib/libluajit-5.1.2.dylib @rpath/libluajit-5.1.2.0.2.dylib Solarus

@rpath represent a "special path" that will search first in @executable_path/../Frameworks, then into /Library/Framework if the library is not found, and then some others if I remember correctly.

Hope this helps :)

Pages: 1 [2]