Messages

1

General / Re: Code Exits with -1, but Compiles Fine

« on: February 21, 2014, 03:17:19 am »

Thank you for all the help. I agree that I should probably read up on manual memory management as well as OOP in C++. I would not have ever suspected pointers to be my problem. I'll read up on C++.

Thanks,
Brooks Rady

2

General / Re: Code Exits with -1, but Compiles Fine

« on: February 21, 2014, 02:27:07 am »

Okay, I'll do more work on C++ alone, but, the above code is not mine. Mine is in the form of an attachment, no one has downloaded it yet, and it would be nice to know what is wrong with that first.

Thanks,
Brooks Rady

3

General / Re: Code Exits with -1, but Compiles Fine

« on: February 21, 2014, 02:09:11 am »

I suppose I was looking for a way to split it into functions.  Such as an OnInit() function that would create the window. Things like that, I was trying to do so via multiple files AND classes. So I could use this as an outline for my real game later on. What broke it, or so I think, was when I was trying pass the window object to another file. I used an access function to do so and it compiled, but didn't work. If you could, It would be nice if you could look at my code if the other option doesn't work.

Thanks,
Brooks Rady

4

General / Re: Static Linking in Linux

« on: February 21, 2014, 01:42:51 am »

I looked more into dynamic linking, and yes now I see the upsides.   I am going to use those instead. Thank you for all of the help and advice!

5

General / [SOLVED]Code Exits with -1, but Compiles Fine

« on: February 21, 2014, 01:40:38 am »

I have decided that I would try to adapt a code snippet found on the SFML website to be stretched across multiple files but to no avail. Here is the snippet I was trying to adapt.

#include <SFML/Audio.hpp>
#include <SFML/Graphics.hpp>
int main()
{
    // Create the main window
    sf::RenderWindow window(sf::VideoMode(800, 600), "SFML window");
    // Load a sprite to display
    sf::Texture texture;
    if (!texture.loadFromFile("cute_image.jpg"))
        return EXIT_FAILURE;
    sf::Sprite sprite(texture);
    // Create a graphical text to display
    sf::Font font;
    if (!font.loadFromFile("arial.ttf"))
        return EXIT_FAILURE;
    sf::Text text("Hello SFML", font, 50);
    // Load a music to play
    sf::Music music;
    if (!music.openFromFile("nice_music.ogg"))
        return EXIT_FAILURE;
    // Play the music
    music.play();
    // Start the game loop
    while (window.isOpen())
    {
        // Process events
        sf::Event event;
        while (window.pollEvent(event))
        {
            // Close window : exit
            if (event.type == sf::Event::Closed)
                window.close();
        }
        // Clear screen
        window.clear();
        // Draw the sprite
        window.draw(sprite);
        // Draw the string
        window.draw(text);
        // Update the window
        window.display();
    }
    return EXIT_SUCCESS;
}

I was able to begin splitting up the code, and it complied fine, but when I run it, it returns -1. I started SFML yesterday, and I still haven't found a tutorial that shows how to use multiple files. Here is my code that compiles, but returns -1. I am attaching all my code. Please reply ASAP.
PS. If some one could show me how to adapt the snippet above so I could split it into multiple files and make it so it is object oriented, that would be much preferred. Please explain it though.

Thanks,
Brooks Rady

6

General / [SOLVED]Static Linking in Linux

« on: February 12, 2014, 08:19:01 am »

Hi, I recently compiled SFML on my Linux laptop and now, when ever I compile the code, it gives me this error.

/usr/bin/ld: cannot find -lsfml-graphics
/usr/bin/ld: cannot find -lsfml-window
/usr/bin/ld: cannot find -lsfml-system
collect2: error: ld returned 1 exit status

I DID compile SFML with static libraries, and I'm 99% sure that that is the source of my problem. Is there support for static libraries in SFML 2.1 for Linux? If not, how would I package the app? I don't know much about dynamic linking, but it reduces portability, and I would like to avoid it if at all posible.

Thanks,
Brooks Rady