C/C++ Programming Help Thread

[yaustar]

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:

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.

[hallo007]

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:)

[1337PSPer]

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

[the unique warrior]

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

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 ;) .

[yaustar]

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:

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

// 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:

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.

[SWE_PsYcHo]

Okay need help again :P

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

so i have this main function:

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?

[the unique warrior]

"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 :

bin2c text.txt text.c text

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

#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 -_-

[yaustar]

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

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:

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.

[ZereoX]

Hi i have a question if i do:

do {
} while (Condition);

is there a dif with this:

while (Condition) {
}

[Raphael]

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.

[yaustar]

Hi i have a question if i do:

do {
} while (Condition);

is there a dif with this:

while (Condition) {
}

Do while loop does a loop before checking the condition.

A while loop checks the condition before looping.

[ZereoX]

OK thanks so EG:

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.

[yaustar]

OK thanks so EG:

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.-

[slicer4ever]

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

[Insert_Witty_Name]

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.

[SWE_PsYcHo]

Okay need help again :P

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

so i have this main function:

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?!

[Insert_Witty_Name]

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

[coolguy5678]

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...

[Insert_Witty_Name]

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

[the undead]

How do you write to flash?

[psphacker12.]

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

[yaustar]

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.

[ZereoX]

I have a question when example:

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.

[SG57]

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:

char password[4];
int spot=0;

Then something like...

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

[Insert_Witty_Name]

There is a debug screen keyboard in the PSP SDK.

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

[SG57]

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

[Raphael]

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

[MaTiAz]

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 should know how to do this

[SG57]

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

[Raphael]

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.

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