04-01-2015, 02:00 AM
I had a small time for that...
...let's start again.
$ SDL_DIR=/mingw rebar compile
which now a days I'm using:
$ SDL_DIR=/usr/local rebar compile
Take a look on Readme file in the ESDL repository. You will find:
So, if it was put "somewhere in you path" the which command that is able to search into all folders/path/directories included in the $PATH environment variable will find executables as well as .DLL too (who knows why?)
As the "which" command is ran in the MSys console, the $PATH environment variable is not that one own by Windows, but the one provide by MSys plus the folders we append in the bash_profile script.
...let's start again.
(06-20-2014, 01:25 PM)ggaliens Wrote: I think I see something odd in #3. With SDL_DIR assignment ?that #3 is related to building the ESDL pack. This line:
$ SDL_DIR=/mingw rebar compile
which now a days I'm using:
$ SDL_DIR=/usr/local rebar compile
Take a look on Readme file in the ESDL repository. You will find:
Quote:...
You need rebar, see: github.com/rebar/rebar
Build with:
rebar compile
On windows:
===========
SDL_DIR=/opt/local rebar compile (requires Microsoft's SDK)
or
CC=gcc SDL_DIR=/opt/local rebar compile (requires mingw)
also copy SDL.dll to esdl/priv dir or put SDL.dll somewhere in your path.
...
So, if it was put "somewhere in you path" the which command that is able to search into all folders/path/directories included in the $PATH environment variable will find executables as well as .DLL too (who knows why?)
As the "which" command is ran in the MSys console, the $PATH environment variable is not that one own by Windows, but the one provide by MSys plus the folders we append in the bash_profile script.