I cloned it into /opt/sdl2/, so that I can access /opt/sdl2/SDL/ and found some installation instructions inside INSTALL.txt
Here is the log of ./configure from inside /opt/sdl2/SDL/:
Code:
checking build system type… i686-pc-linux-gnu
checking host system type… i686-pc-linux-gnu
checking how to print strings… printf
checking for gcc… gcc
checking whether the C compiler works… yes
checking for C compiler default output file name… a.out
checking for suffix of executables…
checking whether we are cross compiling… no
checking for suffix of object files… o
checking whether we are using the GNU C compiler… yes
checking whether gcc accepts -g… yes
checking for gcc option to accept ISO C89… none needed
checking for a sed that does not truncate output… /bin/sed
checking for grep that handles long lines and -e… /bin/grep
checking for egrep… /bin/grep -E
checking for fgrep… /bin/grep -F
checking for ld used by gcc… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking for BSD- or MS-compatible name lister (nm)… /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface… BSD nm
checking whether ln -s works… yes
checking the maximum length of command line arguments… 1572864
checking whether the shell understands some XSI constructs… yes
checking whether the shell understands “+=”… yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format… func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format… func_convert_file_noop
checking for /usr/bin/ld option to reload object files… -r
checking for objdump… objdump
checking how to recognize dependent libraries… pass_all
checking for dlltool… no
checking how to associate runtime and link libraries… printf %s\n
checking for ar… ar
checking for archiver @FILE support… @
checking for strip… strip
checking for ranlib… ranlib
checking for gawk… no
checking for mawk… mawk
checking command to parse /usr/bin/nm -B output from gcc object… ok
checking for sysroot… no
checking for mt… mt
checking if mt is a manifest tool… no
checking how to run the C preprocessor… gcc -E
checking for ANSI C header files… yes
checking for sys/types.h… yes
checking for sys/stat.h… yes
checking for stdlib.h… yes
checking for string.h… yes
checking for memory.h… yes
checking for strings.h… yes
checking for inttypes.h… yes
checking for stdint.h… yes
checking for unistd.h… yes
checking for dlfcn.h… yes
checking for objdir… .libs
checking if gcc supports -fno-rtti -fno-exceptions… no
checking for gcc option to produce PIC… -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works… yes
checking if gcc static flag -static works… yes
checking if gcc supports -c -o file.o… yes
checking if gcc supports -c -o file.o… (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries… yes
checking whether -lc should be explicitly linked in… no
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking whether stripping libraries is possible… yes
checking if libtool supports shared libraries… yes
checking whether to build shared libraries… yes
checking whether to build static libraries… yes
checking for gcc… (cached) gcc
checking whether we are using the GNU C compiler… (cached) yes
checking whether gcc accepts -g… (cached) yes
checking for gcc option to accept ISO C89… (cached) none needed
checking for g++… g++
checking whether we are using the GNU C++ compiler… yes
checking whether g++ accepts -g… yes
checking how to run the C++ preprocessor… g++ -E
checking for ld used by g++… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries… yes
checking for g++ option to produce PIC… -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works… yes
checking if g++ static flag -static works… yes
checking if g++ supports -c -o file.o… yes
checking if g++ supports -c -o file.o… (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries… yes
checking dynamic linker characteristics… (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking for a BSD-compatible install… /usr/bin/install -c
checking whether make sets $(MAKE)… yes
checking for windres… no
configure: error:
*** When building from Mercurial you should configure and build in a
separate directory so you don’t clobber SDL_config.h, SDL_revision.h
But I don’t know what exactly to do. Going on with make will cause an error, because where was no Makefile created - what should be done by configure in the first place.
$ cd path/to/repo/of/SDL2
$ mkdir build && cd build
$ …/configure
$ make && sudo make install
In short, SDL2’s repo requires you to build in a different directory, which
could be anywhere. To build from that directory, you just need to cd
into it, then call SDL’s ./configure script (by either relative or full
path), and then it will build the makefiles in that directory.On Tue, Jun 18, 2013 at 10:59 AM, Glocke wrote:
**
Hi,
I’m using GNU/Linux Ubuntu 12.04 x86 and I’m trying to install SDL2! I
just cloned the repository using
I cloned it into /opt/sdl2/, so that I can access /opt/sdl2/SDL/ and
found some installation instructions inside INSTALL.txt
Here is the log of ./configure from inside /opt/sdl2/SDL/:
Code:
checking build system type… i686-pc-linux-gnu
checking host system type… i686-pc-linux-gnu
checking how to print strings… printf
checking for gcc… gcc
checking whether the C compiler works… yes
checking for C compiler default output file name… a.out
checking for suffix of executables…
checking whether we are cross compiling… no
checking for suffix of object files… o
checking whether we are using the GNU C compiler… yes
checking whether gcc accepts -g… yes
checking for gcc option to accept ISO C89… none needed
checking for a sed that does not truncate output… /bin/sed
checking for grep that handles long lines and -e… /bin/grep
checking for egrep… /bin/grep -E
checking for fgrep… /bin/grep -F
checking for ld used by gcc… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking for BSD- or MS-compatible name lister (nm)… /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface… BSD nm
checking whether ln -s works… yes
checking the maximum length of command line arguments… 1572864
checking whether the shell understands some XSI constructs… yes
checking whether the shell understands “+=”… yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu
format… func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain
format… func_convert_file_noop
checking for /usr/bin/ld option to reload object files… -r
checking for objdump… objdump
checking how to recognize dependent libraries… pass_all
checking for dlltool… no
checking how to associate runtime and link libraries… printf %s\n
checking for ar… ar
checking for archiver @FILE support… @
checking for strip… strip
checking for ranlib… ranlib
checking for gawk… no
checking for mawk… mawk
checking command to parse /usr/bin/nm -B output from gcc object… ok
checking for sysroot… no
checking for mt… mt
checking if mt is a manifest tool… no
checking how to run the C preprocessor… gcc -E
checking for ANSI C header files… yes
checking for sys/types.h… yes
checking for sys/stat.h… yes
checking for stdlib.h… yes
checking for string.h… yes
checking for memory.h… yes
checking for strings.h… yes
checking for inttypes.h… yes
checking for stdint.h… yes
checking for unistd.h… yes
checking for dlfcn.h… yes
checking for objdir… .libs
checking if gcc supports -fno-rtti -fno-exceptions… no
checking for gcc option to produce PIC… -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works… yes
checking if gcc static flag -static works… yes
checking if gcc supports -c -o file.o… yes
checking if gcc supports -c -o file.o… (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries…
yes
checking whether -lc should be explicitly linked in… no
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking whether stripping libraries is possible… yes
checking if libtool supports shared libraries… yes
checking whether to build shared libraries… yes
checking whether to build static libraries… yes
checking for gcc… (cached) gcc
checking whether we are using the GNU C compiler… (cached) yes
checking whether gcc accepts -g… (cached) yes
checking for gcc option to accept ISO C89… (cached) none needed
checking for g++… g++
checking whether we are using the GNU C++ compiler… yes
checking whether g++ accepts -g… yes
checking how to run the C++ preprocessor… g++ -E
checking for ld used by g++… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries…
yes
checking for g++ option to produce PIC… -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works… yes
checking if g++ static flag -static works… yes
checking if g++ supports -c -o file.o… yes
checking if g++ supports -c -o file.o… (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries…
yes
checking dynamic linker characteristics… (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking for a BSD-compatible install… /usr/bin/install -c
checking whether make sets $(MAKE)… yes
checking for windres… no
configure: error:
*** When building from Mercurial you should configure and build in a
separate directory so you don’t clobber SDL_config.h, SDL_revision.h
But I don’t know what exactly to do. Going on with make will cause an
error, because where was no Makefile created - what should be done by
configure in the first place.
The error message means you should create a separate directory somewhere,
like build in your SDL clone directory, and run the configure script from
there.
hg clone http://hg.libsdl.org/SDL
cd SDL
mkdir build
cd build
…/configure
make [-j 4]
sudo make install
…etcOn Tue, Jun 18, 2013 at 10:59 AM, Glocke wrote:
**
Hi,
I’m using GNU/Linux Ubuntu 12.04 x86 and I’m trying to install SDL2! I
just cloned the repository using
I cloned it into /opt/sdl2/, so that I can access /opt/sdl2/SDL/ and
found some installation instructions inside INSTALL.txt
Here is the log of ./configure from inside /opt/sdl2/SDL/:
Code:
checking build system type… i686-pc-linux-gnu
checking host system type… i686-pc-linux-gnu
checking how to print strings… printf
checking for gcc… gcc
checking whether the C compiler works… yes
checking for C compiler default output file name… a.out
checking for suffix of executables…
checking whether we are cross compiling… no
checking for suffix of object files… o
checking whether we are using the GNU C compiler… yes
checking whether gcc accepts -g… yes
checking for gcc option to accept ISO C89… none needed
checking for a sed that does not truncate output… /bin/sed
checking for grep that handles long lines and -e… /bin/grep
checking for egrep… /bin/grep -E
checking for fgrep… /bin/grep -F
checking for ld used by gcc… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking for BSD- or MS-compatible name lister (nm)… /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface… BSD nm
checking whether ln -s works… yes
checking the maximum length of command line arguments… 1572864
checking whether the shell understands some XSI constructs… yes
checking whether the shell understands “+=”… yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu
format… func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain
format… func_convert_file_noop
checking for /usr/bin/ld option to reload object files… -r
checking for objdump… objdump
checking how to recognize dependent libraries… pass_all
checking for dlltool… no
checking how to associate runtime and link libraries… printf %s\n
checking for ar… ar
checking for archiver @FILE support… @
checking for strip… strip
checking for ranlib… ranlib
checking for gawk… no
checking for mawk… mawk
checking command to parse /usr/bin/nm -B output from gcc object… ok
checking for sysroot… no
checking for mt… mt
checking if mt is a manifest tool… no
checking how to run the C preprocessor… gcc -E
checking for ANSI C header files… yes
checking for sys/types.h… yes
checking for sys/stat.h… yes
checking for stdlib.h… yes
checking for string.h… yes
checking for memory.h… yes
checking for strings.h… yes
checking for inttypes.h… yes
checking for stdint.h… yes
checking for unistd.h… yes
checking for dlfcn.h… yes
checking for objdir… .libs
checking if gcc supports -fno-rtti -fno-exceptions… no
checking for gcc option to produce PIC… -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works… yes
checking if gcc static flag -static works… yes
checking if gcc supports -c -o file.o… yes
checking if gcc supports -c -o file.o… (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries…
yes
checking whether -lc should be explicitly linked in… no
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking whether stripping libraries is possible… yes
checking if libtool supports shared libraries… yes
checking whether to build shared libraries… yes
checking whether to build static libraries… yes
checking for gcc… (cached) gcc
checking whether we are using the GNU C compiler… (cached) yes
checking whether gcc accepts -g… (cached) yes
checking for gcc option to accept ISO C89… (cached) none needed
checking for g++… g++
checking whether we are using the GNU C++ compiler… yes
checking whether g++ accepts -g… yes
checking how to run the C++ preprocessor… g++ -E
checking for ld used by g++… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries…
yes
checking for g++ option to produce PIC… -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works… yes
checking if g++ static flag -static works… yes
checking if g++ supports -c -o file.o… yes
checking if g++ supports -c -o file.o… (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries…
yes
checking dynamic linker characteristics… (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking for a BSD-compatible install… /usr/bin/install -c
checking whether make sets $(MAKE)… yes
checking for windres… no
configure: error:
*** When building from Mercurial you should configure and build in a
separate directory so you don’t clobber SDL_config.h, SDL_revision.h
But I don’t know what exactly to do. Going on with make will cause an
error, because where was no Makefile created - what should be done by
configure in the first place.
Assuming that you are in ‘/opt/sdl2’, with the main SDL directory at /opt/sdl2/SDL, if I understood correctly,
cd into ‘SDL’ and make a new folder name ‘build’. cd into the new directory and then do configure.
I know that the way I said it above is not real english [ sorry but I’m not a native speaker ], below I give you the code:
$ cd /opt/sdl2
$ hg clone http://hg.libsdl.org/SDL SDL
$ cd SDL
$ mkdir build && cd build
$ …/configure
$ make
$ sudo make install
Practically, you can’t run configure in the top-level directory of the SDL2 source code…
Hope that helps,
Aggelos Kolaitis------------------------
C is the God’s Programming Language
Chris Bush wrote:> The error message means you should create a separate directory somewhere, like build in your SDL clone directory, and run the configure script from there.
I cloned it into /opt/sdl2/, so that I can access /opt/sdl2/SDL/ and found some installation instructions inside INSTALL.txt
Here is the log of ./configure from inside /opt/sdl2/SDL/:
Code:
checking build system type... i686-pc-linux-gnu
checking host system type… i686-pc-linux-gnu
checking how to print strings… printf
checking for gcc… gcc
checking whether the C compiler works… yes
checking for C compiler default output file name… a.out
checking for suffix of executables…
checking whether we are cross compiling… no
checking for suffix of object files… o
checking whether we are using the GNU C compiler… yes
checking whether gcc accepts -g… yes
checking for gcc option to accept ISO C89… none needed
checking for a sed that does not truncate output… /bin/sed
checking for grep that handles long lines and -e… /bin/grep
checking for egrep… /bin/grep -E
checking for fgrep… /bin/grep -F
checking for ld used by gcc… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking for BSD- or MS-compatible name lister (nm)… /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface… BSD nm
checking whether ln -s works… yes
checking the maximum length of command line arguments… 1572864
checking whether the shell understands some XSI constructs… yes
checking whether the shell understands “+=”… yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format… func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format… func_convert_file_noop
checking for /usr/bin/ld option to reload object files… -r
checking for objdump… objdump
checking how to recognize dependent libraries… pass_all
checking for dlltool… no
checking how to associate runtime and link libraries… printf %s\n
checking for ar… ar
checking for archiver @FILE support… @
checking for strip… strip
checking for ranlib… ranlib
checking for gawk… no
checking for mawk… mawk
checking command to parse /usr/bin/nm -B output from gcc object… ok
checking for sysroot… no
checking for mt… mt
checking if mt is a manifest tool… no
checking how to run the C preprocessor… gcc -E
checking for ANSI C header files… yes
checking for sys/types.h… yes
checking for sys/stat.h… yes
checking for stdlib.h… yes
checking for string.h… yes
checking for memory.h… yes
checking for strings.h… yes
checking for inttypes.h… yes
checking for stdint.h… yes
checking for unistd.h… yes
checking for dlfcn.h… yes
checking for objdir… .libs
checking if gcc supports -fno-rtti -fno-exceptions… no
checking for gcc option to produce PIC… -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works… yes
checking if gcc static flag -static works… yes
checking if gcc supports -c -o file.o… yes
checking if gcc supports -c -o file.o… (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries… yes
checking whether -lc should be explicitly linked in… no
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking whether stripping libraries is possible… yes
checking if libtool supports shared libraries… yes
checking whether to build shared libraries… yes
checking whether to build static libraries… yes
checking for gcc… (cached) gcc
checking whether we are using the GNU C compiler… (cached) yes
checking whether gcc accepts -g… (cached) yes
checking for gcc option to accept ISO C89… (cached) none needed
checking for g++… g++
checking whether we are using the GNU C++ compiler… yes
checking whether g++ accepts -g… yes
checking how to run the C++ preprocessor… g++ -E
checking for ld used by g++… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries… yes
checking for g++ option to produce PIC… -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works… yes
checking if g++ static flag -static works… yes
checking if g++ supports -c -o file.o… yes
checking if g++ supports -c -o file.o… (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries… yes
checking dynamic linker characteristics… (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking for a BSD-compatible install… /usr/bin/install -c
checking whether make sets $(MAKE)… yes
checking for windres… no
configure: error:
*** When building from Mercurial you should configure and build in a
? ? separate directory so you don’t clobber SDL_config.h, SDL_revision.h
But I don’t know what exactly to do. Going on with make will cause an error, because where was no Makefile created - what should be done by configure in the first place.
Assuming that you are in ‘/opt/sdl2’, with the main SDL directory at /opt/sdl2/SDL, if I understood correctly,
cd into ‘SDL’ and make a new folder name ‘build’. cd into the new directory and then do configure.
That’s correct
neoaggelos wrote:
I know that the way I said it above is not real english [ sorry but I’m not a native speaker ]
Me neigher
neoaggelos wrote:
Code:
$ cd /opt/sdl2
$ hg clone http://hg.libsdl.org/SDL SDL
$ cd SDL
$ mkdir build && cd build
$ …/configure
$ make
$ sudo make install
That’s great! Thanks a lot! It worked perfectly. I also just tried a minimal demo application from the wiki at it works - so die headers and dynamic libraries were installed correctly
neoaggelos wrote:
Practically, you can’t run configure in the top-level directory of the SDL2 source code.
Someone might add this to the INSTALL.txt ^^
2nd Question: Where to get the the v2.0 versions of SDL_image, SDL_mixer, SDL_ttf, SDL_gfx and SDL_net? I was working with all of them and would like to continue working with them in the context of SDL2
Where to get the the v2.0 versions of SDL_image, SDL_mixer, SDL_ttf, SDL_gfx and SDL_net? I was working with all of them and would like to continue working with them in the context of SDL2.
Okay, I found them myself (but not for SDL_gfx). Unfortunatley the building process crashes for SDL_image, SDL_ttf and SDL_net with the same error while make:
Code:
CDPATH="${ZSH_VERSION+.}:" && cd … && /bin/bash /opt/sdl2/SDL_net/missing aclocal-1.13
/opt/sdl2/SDL_net/missing: Zeile 81: aclocal-1.13: Kommando nicht gefunden.
WARNING: ‘aclocal-1.13’ is missing on your system.
You should only need it if you modified ‘acinclude.m4’ or
’configure.ac’ or m4 files included by ‘configure.ac’.
The ‘aclocal’ program is part of the GNU Automake package: http://www.gnu.org/software/automake
It also requires GNU Autoconf, GNU m4 and Perl in order to run: http://www.gnu.org/software/autoconf http://www.gnu.org/software/m4/ http://www.perl.org/
make: *** […/aclocal.m4] Fehler 127
I already installed automake. But it seems to be v1.11.3. Ubuntu (not just 12.04, also the current release) does not provide v1.13 itself. I don’t know which PPA to use - I don’t want to check multiple PPAs of possible untrusted sources :?
Did you try running autogen.sh to rebuild the configure script yet?
Jonny DOn Tue, Jun 18, 2013 at 2:38 PM, Glocke wrote:
**
scrawl wrote:
sudo apt-get install automake
I already installed automake. But it seems to be v1.11.3. Ubuntu (not just
12.04, also the current release) does not provide v1.13 itself. I don’t
know which PPA to use - I don’t want to check multiple PPAs of possible
untrusted sources [image: Confused]
Anyone know where I can get libjpeg with build scripts that actually
work?
The sourceforge hosted lib is a windows zip and the scripts
contain CR chars which screw up. Even after removing these
the scripts don’t work.
[On OSX. I don’t want a prebuilt package because I want the lib
in /usr/local not a system framework]–
john skaller @john_skaller http://felix-lang.org
You could actually try this:
dos2unix configure
And then you should be able to do your usual configure; make installOn Jun 18, 2013 5:49 PM, “Andre Renaud” wrote:
Hi John,
On 19 June 2013 10:04, john skaller wrote:
Anyone know where I can get libjpeg with build scripts that actually
work?
The sourceforge hosted lib is a windows zip and the scripts
contain CR chars which screw up. Even after removing these
the scripts don’t work.
[On OSX. I don’t want a prebuilt package because I want the lib
in /usr/local not a system framework]
My internal build script for this does the following prior to doing
the standard ./configure ; make ; make install
fromdos *
chmod +x configure
Try the tarballs from independent jpeg group’s website: http://www.ijg.org/files/
You probably want jpegsrc.v9.tar.gzOn Tue, Jun 18, 2013 at 6:04 PM, john skaller wrote:
Anyone know where I can get libjpeg with build scripts that actually
work?
The sourceforge hosted lib is a windows zip and the scripts
contain CR chars which screw up. Even after removing these
the scripts don’t work.
[On OSX. I don’t want a prebuilt package because I want the lib
in /usr/local not a system framework]
Thx