Compiling on lubuntu

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • PopTart
    Apprentice
    • May 2017
    • 89

    Compiling on lubuntu

    Hello, I'm pretty new to Linux, but I managed to compile the game on Lubuntu. Had a heck of a time, since a lot of assumed dependencies weren't there. I ran the following lines:

    ./autogen.sh
    ./configure --enable-sdl -enable-x11 ~/Desktop/angband-4.2.1/execute
    make
    make install

    It seems like everything compiled, and I didn't get any errors. So, what's supposed to happen now? It made a new folder called execute, but nothing seems executable in there. I've tried navigating to different folders within the terminal and typing "angband" but nothing works.

    Thanks!
  • PopTart
    Apprentice
    • May 2017
    • 89

    #2
    Found it

    Mysterious... when I navigate to the folder and type "angband", it doesn't work. But when I drag the icon into the terminal, it works.

    Comment

    • PopTart
      Apprentice
      • May 2017
      • 89

      #3
      Slightly new question

      When I configured during build, I used these line:

      ./configure --prefix ~/Desktop/angband-4.2.1/execute --enable-sdl --enable-x11
      make
      make install

      It seems like x11 is working fine, so it works when I put in
      /home/lubuntu/Desktop/angband-4.2.1/execute/games/angband -mx11 -- -n5

      but when I try to run

      /home/lubuntu/Desktop/angband-4.2.1/execute/games/angband -msdl

      ...I get the error: Unable to prepare any 'display module'!

      How do I get SDL to work? Thanks!

      Comment

      • PopTart
        Apprentice
        • May 2017
        • 89

        #4
        More info: I double checked in my configure step if SDL2 is installed, and yes it is, I installed the main one, the graphics, and the fonts, just no sound.

        Another weird thing, in X11, saving the subwindow setup seems to work, but it seems like it's not creating the subwindow file, and when I load it nothing happens, but it doesn't give any error message.
        Last edited by PopTart; December 21, 2020, 08:08.

        Comment

        • invisibletroll
          Apprentice
          • Jul 2020
          • 50

          #5
          If you install the game, it should run by typing "angband". Otherwise you need to type "./angband".

          Type "./configure --help" to get configuration options. Usually you can disable any option you can enable.

          Comment

          • fph
            Veteran
            • Apr 2009
            • 1030

            #6
            If you compiled in SDL2 support, then to activate it you should run Angband with -msdl2. If you use -msdl, it tries to use the older SDL1 backend instead.

            Usually when I am compiling I prefer to configure Angband with --with-no-install and then running it from the main compilation folder with "src/angband -msdl2" (or whatever options/backend you wish to use). I suggest to do the same; it is one less thing to do, and it makes it simpler to upgrade to a new version.
            --
            Dive fast, die young, leave a high-CHA corpse.

            Comment

            • invisibletroll
              Apprentice
              • Jul 2020
              • 50

              #7
              Originally posted by fph
              If you compiled in SDL2 support, then to activate it you should run Angband with -msdl2. If you use -msdl, it tries to use the older SDL1 backend instead.

              Usually when I am compiling I prefer to configure Angband with --with-no-install and then running it from the main compilation folder with "src/angband -msdl2" (or whatever options/backend you wish to use). I suggest to do the same; it is one less thing to do, and it makes it simpler to upgrade to a new version.
              New versions are not released that often.

              Comment

              • PopTart
                Apprentice
                • May 2017
                • 89

                #8
                Originally posted by fph
                If you compiled in SDL2 support, then to activate it you should run Angband with -msdl2. If you use -msdl, it tries to use the older SDL1 backend instead.

                Usually when I am compiling I prefer to configure Angband with --with-no-install and then running it from the main compilation folder with "src/angband -msdl2" (or whatever options/backend you wish to use). I suggest to do the same; it is one less thing to do, and it makes it simpler to upgrade to a new version.
                Same problem when I use -msdl2. But I will try this no-install option, thank you!

                Comment

                • PopTart
                  Apprentice
                  • May 2017
                  • 89

                  #9
                  Originally posted by invisibletroll
                  If you install the game, it should run by typing "angband". Otherwise you need to type "./angband".

                  Type "./configure --help" to get configuration options. Usually you can disable any option you can enable.
                  I reconfigured it to install to the default directory, and now it works to simply type angband. Thanks!

                  Comment

                  • PopTart
                    Apprentice
                    • May 2017
                    • 89

                    #10
                    Still not able to make SDL2 work

                    Comment

                    • fph
                      Veteran
                      • Apr 2009
                      • 1030

                      #11
                      Originally posted by PopTart
                      Same problem when I use -msdl2. But I will try this no-install option, thank you!
                      Does `configure` confirms that those SDL frontends have been compiled in? If you look at the end of that wall of text usually it tells you if all the required headers have been detected correctly. (Note that you can re-run `configure` if you wish to check its output.)
                      --
                      Dive fast, die young, leave a high-CHA corpse.

                      Comment

                      • invisibletroll
                        Apprentice
                        • Jul 2020
                        • 50

                        #12
                        Don't configure with "--enable-sdl". Use "--enable-sdl2".

                        Comment

                        • PopTart
                          Apprentice
                          • May 2017
                          • 89

                          #13
                          Originally posted by fph
                          Does `configure` confirms that those SDL frontends have been compiled in? If you look at the end of that wall of text usually it tells you if all the required headers have been detected correctly. (Note that you can re-run `configure` if you wish to check its output.)
                          It confirms that SDL2 has been compiled in.

                          Comment

                          • PopTart
                            Apprentice
                            • May 2017
                            • 89

                            #14
                            It could have to do with

                            1. I'm running Lubuntu, which maybe can't support SDL2
                            2. Intel Atom processor, not AMD

                            Comment

                            • fph
                              Veteran
                              • Apr 2009
                              • 1030

                              #15
                              That's quite strange; none of these facts should have an impact. If `configure` finds all the required headers and confirms in the final messages that the SDL2 support is going to be included in the build, then it means it should be supported, no matter what distro or architecture you are using. That's precisely the job of a configure script, to confirm that all the required libraries and dependencies are there.

                              Be sure that you have rebuilt everything after the last configuration change: `./configure --with-your-favorite-options` followed by `make clean` and `make` just to be 200% sure you rebuild everything from scratch.
                              --
                              Dive fast, die young, leave a high-CHA corpse.

                              Comment

                              Working...
                              😀
                              😂
                              🥰
                              😘
                              🤢
                              😎
                              😞
                              😡
                              👍
                              👎