C/C++ Programming Help Thread

Zitat:

---

Zitat von Moca

in main.c
#include "yourfile.c"

---

No! Never ever include source files (.c or .cpp) in other source files. Place this at the top of the main file:

Code:

---

extern static unsigned char background[];

---

This tells the compiler when it is compiling the main source file that this variable is in another object file and will be linked by the linker later.

Zitat:

---

Zitat von Moca

Huh???!??

Im kinda not understanding what you are saying :P ..

Make sure u add

in main.c
#include "yourfile.c"


In the makefile

TARGET = Hi
OBJS = main.c yourfile.c




I dont understand what you were saying so i hope that helped :P

---

yeah you helped me:)

ok i realy need help i have been trying to get a prx to load a image but nothing seems to be working would any of you guys be able to help me.
thx mafia1ft

Zitat:

---

Zitat von yaustar

No! Never ever include source files (.c or .cpp) in other source files. Place this at the top of the main file:

Code:

---

extern static unsigned char background[];

---

This tells the compiler when it is compiling the main source file that this variable is in another object file and will be linked by the linker later.

---

You 'can' include then so 'Never Ever' is not a good word -_-.
I don't know what you were talking about and I'm lazy to check -_- , So I guess your right about this case <_< .

Moca usually includes his file.c into his main.c when he's using bin2c ;) .

Zitat:

---

Zitat von the unique warrior

You 'can' include then so 'Never Ever' is not a good word -_-.
I don't know what you were talking about and I'm lazy to check -_- , So I guess your right about this case <_< .

Moca usually includes his file.c into his main.c when he's using bin2c ;) .

---

"Never ever include source files" implies that it is a bad thing to do.
"You cannot include source files" implies a fact.

The choice of using "never ever" seems to be fine in terms of choice of words.

When using an IDE or a makefile generation, it will automatically compile any .c or .cpp file. By including a .c or .cpp into another file, you are effectively compiling it twice or more, once directly to the compiler and the other, indirectly from #includes since all #include does is text replacement.

eg:

Code:

---

// source1.c
void Hello ( )
{
    // Do stuff
}

---

Code:

---

// source2.c
#include "source1.c"

int main()
{
    // do more stuff
    return 0;
}

---

The compiler compiles source1.c to a seperate .obj file then when it compiles source2.c, it sees this:

Code:

---

void Hello ( )
{
    // Do stuff
}

int main()
{
    // do more stuff
    return 0;
}

---

Compiles it, then when the linker tries to link the two obj files, it throws a function redefinition error.

Technically, you can #include anything (XML, TXT, etc).

I don't know who this Moca is, but I will shoot him if he did that in my codebase/projects.

Okay need help again :P

i have tested the psp-programming fourth tute about image blitting,

so i have this main function:

Code:

---

int main() {
        char buffer[200];
        Image* ourImage;
        pspDebugScreenInit();
        SetupCallbacks();
        initGraphics();
        sprintf(buffer, "ourImage.png");
        ourImage = loadImage(buffer);
        if(!ourImage) {
                //Image load failed
                printf("Image load failed!\n");
        } else {

        int x = 0;
        int y = 0;
        sceDisplayWaitVblankStart();

        while (x < 480) {
                while (y < 272) {
                        blitAlphaImageToScreen(0, 0, 480, 272, buffer, x, y);
                        y += 272;
                }

                x += 480;
                y = 0;
        }

                flipScreen();
        }

                sceKernelSleepThread();
                return 0;
}

---

what i want to know is how i blit that image rotated 180 degrees or blitting it reversed?

Zitat:

---

Zitat von yaustar

"Never ever include source files" implies that it is a bad thing to do.
"You cannot include source files" implies a fact.

The choice of using "never ever" seems to be fine in terms of choice of words.

When using an IDE or a makefile generation, it will automatically compile any .c or .cpp file. By including a .c or .cpp into another file, you are effectively compiling it twice or more, once directly to the compiler and the other, indirectly from #includes since all #include does is text replacement.


I don't know who this Moca is, but I will shoot him if he did that in my codebase/projects.

---

I have to admit that your right that it compiles twice. BUT just try doing what this guy 'Moca' wanted to do . use your SDK too :

Code:

---

bin2c text.txt text.c text

---

and convert a text file to .C .
Then Do something like this

Code:

---

#includes. (note: don't include the text.c yet )
int main( int argc, char **argv)
{
  SceUID fd = sceIoOpen("text.txt", PSP_O_WRONLY | PSP_O_CREAT | PSP_O_TRUNC, 0777);
  sceIoWrite(fd, text_buffer, text_size);
  sceIoClose(fd);
  sceKernelExitGame();
return 0;
}

---

You'll get an unidentified variable error.
Now try the samething with the .c file included and you won't get an error .

This MayBe PSP-SDK's Problem(at least the old one ) and maybe fixed now, or I was doing something wrong the last time I teseted this -_-

Zitat:

---

Zitat von yaustar

No! Never ever include source files (.c or .cpp) in other source files. Place this at the top of the main file:

Code:

---

extern static unsigned char background[];

---

This tells the compiler when it is compiling the main source file that this variable is in another object file and will be linked by the linker later.

---

Quoted for emphasis although ther is an error in the code above :/

You code should have been:

Code:

---

extern unsigned char text_buffer[];
extern int text_size;
int main( int argc, char **argv)
{
  SceUID fd = sceIoOpen("text.txt", PSP_O_WRONLY | PSP_O_CREAT | PSP_O_TRUNC, 0777);
  sceIoWrite(fd, text_buffer, text_size);
  sceIoClose(fd);
  sceKernelExitGame();
return 0;
}

---

And remove the static keyword from the generated .c file since it limits the variable to file scope.

At the VERY worse, I rename the generated .c file to a .h, put in header guards and then #include it. Renaming the file means that auto generated makefiles/scanners and IDEs want compile it to a seperate .obj file.

Hi i have a question if i do:

Code:

---

do {
} while (Condition);

---

is there a dif with this:

Code:

---

while (Condition) {
}

---

The first case will at least run the code in the brackets once, because the condition check is done at the end of the code segment.
Nothing else.

Zitat:

---

Zitat von ZereoX

Hi i have a question if i do:

Code:

---

do {
} while (Condition);

---

is there a dif with this:

Code:

---

while (Condition) {
}

---

---

Do while loop does a loop before checking the condition.

A while loop checks the condition before looping.

OK thanks so EG:

Code:

---

int x=0;
do {x++;}
while ( x < 0)

---

So here x will atleast be 1 since it does a loop before checking the condition.

Thanks I apreciate.

Zitat:

---

Zitat von ZereoX

OK thanks so EG:

Code:

---

int x=0;
do {x++;}
while ( x < 0)

---

So here x will atleast be 1 since it does a loop before checking the condition.

Thanks I apreciate.

---

Yes.

-The message you have entered is too short.-

is there a way to check for files in a folder and if so what libarys/commands do you need?
-= Double Post =-
also how to i save images from the screen

You need to include stdio.h and open said file, the fopen function will return NULL on failure. See here: http://www.cplusplus.com/reference/c...dio/fopen.html

For saving a screenshot, if you're using graphics.c/.h then the saveImage function is all you need.

Zitat:

---

Zitat von SWE_PsYcHo

Okay need help again :P

i have tested the psp-programming fourth tute about image blitting,

so i have this main function:

Code:

---

int main() {
        char buffer[200];
        Image* ourImage;
        pspDebugScreenInit();
        SetupCallbacks();
        initGraphics();
        sprintf(buffer, "ourImage.png");
        ourImage = loadImage(buffer);
        if(!ourImage) {
                //Image load failed
                printf("Image load failed!\n");
        } else {

        int x = 0;
        int y = 0;
        sceDisplayWaitVblankStart();

        while (x < 480) {
                while (y < 272) {
                        blitAlphaImageToScreen(0, 0, 480, 272, buffer, x, y);
                        y += 272;
                }

                x += 480;
                y = 0;
        }

                flipScreen();
        }

                sceKernelSleepThread();
                return 0;
}

---

what i want to know is how i blit that image rotated 180 degrees or blitting it reversed?

---

CAN ANYONE HELP ME?!

The graphics.c/.h that you are using doesn't support rotation.

It seems you need OSLib for rotation...

By the way, is it possible to add a function do graphics.c to allow rotation, or does graphics.c use some GU mode which doesn't allow it? I'm not sure how the GU works.

Image rotation is something I need for Bounce, but it uses graphics.c and I don't really want to port the whole thing to OSLib...

You need to be in an ortho projection to use the sceGumRotate* functions, neither the graphics.c or OSLib uses an ortho projection.

How do you write to flash?

How can I blit an image onscreen for five secs. and then sceKernelExitGame()?

Zitat:

---

Zitat von psphacker12.

How can I blit an image onscreen for five secs. and then sceKernelExitGame()?

---

Why is everyone asking "how tos"?

Blit the image
Flip the buffer
Wait for VSync 5 * 60 times
Exit game

Done.

I have a question when example:

Code:

---

using namespace std;

int main() {
    pspDebugScreenInit();
    SetupCallbacks();

    int age;
    int year = 2007;

    cout<<"Type you age:\n";
    cin>> age;
    cin.ignore()
   
  if ( age < 0 ) {BLAH}

---

Is there a way of actualy way of entering a number on teh psp, since on that on the pc you just have to press a number.

Does it look like hte PSP has a keyboard?

Youd have to write your number entering routine. I did somtehing very very similar in coolguy and I's Block Dude clone. I had an array, someting like:

Code:

---

char password[4];
int spot=0;

---

Then something like...

Code:

---

if up is pressed and password[spot] != 'a' { password[spot] -= 0x01 }
if cross is pressed {
  spot++
  if spot > 3 { compare password to password string from map file }
}

---

Or something similar and much more defined and working... I made it ~5 months ago, back when I was ~2/3 of what i am now, so it shouldnt be hard

There is a debug screen keyboard in the PSP SDK.

Check out the pspdebugkb.h header and the sample too.

The debug console has a built-in keyboard? Huh - whats it look like?

You have been away from your PSP way too long, seriously.

Zitat:

---

Zitat von yaustar

Why is everyone asking "how tos"?

Blit the image
Flip the buffer
Wait for VSync 5 * 60 times
Exit game

Done.

---

Or more simply:

Blit image
Flip the buffer
Delay thread for five secs

Done. :)

Anyway I think that a PSP hacker should know how to do this

I havent had a PSP since ~2days before the 2.8 eloader came out.... Thanks for rubbing it inthere Raph...

I wasn't trying to insult you, just stating an obvious fact. If you still had your PSP, you wouldn't have asked such a question.

Zitat:

---

The debug console has a built-in keyboard? Huh - whats it look like?

---

Actually, I find it rather sad, but props that you still try to keep up in the scene :P I prolly wouldn't have the guts

Ive had to resort to Lua, but ya im trying... Dont like it as it messes with my C syntax, but its all good i guess.

Zitat:

---

Zitat von SG57

Ive had to resort to Lua, but ya im trying... Dont like it as it messes with my C syntax, but its all good i guess.

---

Whenever I look at Lua code, the lack of semi-colons just jumps at me...

http://img484.imageshack.us/img484/7...wonprobqp8.png
any suggestions?

dl all auto makes again in the cygwin setup
-= Double Post =-

Code:

---

[email protected] ~/psptoolchain
$ ./toolchain.sh
--19:13:07--  ftp://ftp.gnu.org/pub/gnu/binutils/binutils-2.16.1.tar.gz
          => `binutils-2.16.1.tar.gz'
Resolving ftp.gnu.org... 199.232.41.7
Connecting to ftp.gnu.org|199.232.41.7|:21... connected.
Logging in as anonymous ...

---

mine freezes at that

Zitat:

---

Zitat von coolguy5678

Whenever I look at Lua code, the lack of semi-colons just jumps at me...

---

im exactly the same way. i just can't do it.

Zitat:

---

Zitat von MaTiAz

Or more simply:

Blit image
Flip the buffer
Delay thread for five secs

Done. :)

Anyway I think that a PSP hacker should know how to do this

---

this is what im trying to do but it doesn't work you try it.

Code:

---

#include <pspdisplay.h>
#include <pspctrl.h>
#include <pspkernel.h>
#include <pspdebug.h>
#include <pspgu.h>
#include <png.h>
#include <stdio.h>
#include "graphics.h"
PSP_MODULE_INFO("Image Display Program", 0, 1, 1);

int main() {
initGraphics();
Image* Wallpaper = "wall.png";
blitAlphaImageToScreen(0, 0, 480, 272, Wallpaper, 0, 0);
flipScreen();
sceKernelDelayThread(3000000);
if (Wallpaper!=NULL) freeImage(Wallpaper);
sceKernelExitGame();
return 0; }

---

I wrote a tutorial how to get around that error at psp-programming.com.

Search through all the names of the threads ive created over there, and you should find it. I havent made too many over there, so....
-= Double Post =-
guy above me - you need to load the image properly:

Code:

---

Image *Wallpaper = loadImage("image.png");

---

I believe that would work

Zitat:

---

Zitat von SG57

I wrote a tutorial how to get around that error at psp-programming.com.

Search through all the names of the threads ive created over there, and you should find it. I havent made too many over there, so....
-= Double Post =-
guy above me - you need to load the image properly:

Code:

---

Ijmage *Wallpaper = loadImage("image.png");

---

I believe that would work

---

lol Ijmage....

Code:

---

Image *Wallpaper = loadImage("image.png");

---

Wow... troll much?

how do you write to a file white hex edit
for example to offset -> 962c??