C/C++ Programming Help Thread

[Insert_Witty_Name]

You need to set PSPDEV.

Read the readme. It's there for a reason.

[SuperBatXS]

What readme?

[Insert_Witty_Name]

ZeMac:~ david.perry$ cd psptoolchain
ZeMac:~/psptoolchain david.perry$ ls
build                   patches                 readme.txt              toolchain-sudo.sh
depends                 readme-ubuntu.txt       scripts                 toolchain.sh
ZeMac:~/psptoolchain david.perry$

That readme.

[SuperBatXS]

Still confused...

[Llanowyn]

I think you may need to add:

set path=%path%;C:/cygwin/usr/local/pspdev/bin
set PSPSDK=C:/cygwin/usr/local/pspdev

to your cygwin.bat file, above the line that says:

bash --login -i

Of course, that could be wrong. I was going to post the relevant part of the readme, but I couldn't find it on my system either. I probably got rid of it sometime during the install chaos or something.

Also, I still need a tutor. :Cry:

[SuperBatXS]

I already put that.

[Insert_Witty_Name]

PSPDEV is not the same as PSPSDK...

[Moca]

http://forums.ps2dev.org/viewtopic.p...er=asc&start=0

Just a suggestion, SuperBatXS.

[SuperBatXS]

I love you, Moca...that's so awesome.
Another question, how do i use this (bin2c) with OSLib:
http://psp-coding.com/index.php?topic=24.0

[Moca]

I love you, Moca...that's so awesome.
Another question, how do i use this (bin2c) with OSLib:
http://psp-coding.com/index.php?topic=24.0

You mean with an image...? Not "with OSLib". Anyway, bin2c just converts each byte in a file into it's hexadecimal equivalent and sticks it in an array.

Just include the header containing the buffer so that you can use it in your code. The array is loaded into memory, so be wary of how big the array you are loading is.

#include "myFile.h"

From the "tutorial"
"There are ways to include other types of files, but I'll go over that later." - Just to let you know, this IS how you include "other types of files". The difference is how you deal with the file that you bin2c'd

[SuperBatXS]

You mean with an image...? Not "with OSLib". Anyway, bin2c just converts each byte in a file into it's hexadecimal equivalent and sticks it in an array.

Just include the header containing the buffer so that you can use it in your code. The array is loaded into memory, so be wary of how big the array you are loading is.

#include "myFile.h"

From the "tutorial"
"There are ways to include other types of files, but I'll go over that later." - Just to let you know, this IS how you include "other types of files". The difference is how you deal with the file that you bin2c'd

I got bin2c to convert my image into a header file, which i am supposed to include. My question is, how do i load the image from memory using OSLib, similiar to this code with the modified graphics lib on that website:

Image* background = loadImageFromMemory(Name_Of_Structure,sizeof(Name_Of_Structure);

[Moca]

I got bin2c to convert my image into a header file, which i am supposed to include. My question is, how do i load the image from memory using OSLib, similiar to this code with the modified graphics lib on that website:

Image* background = loadImageFromMemory(Name_Of_Structure,sizeof(Name_Of_Structure);

Just like you would load any other picture loaded in memory? I haven't used OSLib, but surely you can pass the address of a buffer containing the image to a function. Look in the oslib header file.

A simple google search lead me to "oslLoadImageFile". I'm sure that function calls another function which takes an address of a buffer holding the image. Well, it should if the code was made to be reusable...

[SG57]

Yes, oslib has a method to load an image internally (rather then externally). Heh, how do you think the intro function is done?

Read your documentation ;)
If you're too lazy here's a sample:

// your 'text' image data
const unsigned long text_data[] = { ... };

// your 'picture' image data
const unsigned long picture_data[] = { ... };

// Your array of virtual files (rather then explain either look at your documentation, even still you should be able to understand this just by looking at it)
const OSL_VIRTUALFILENAME ram_files[] =		{
	{"ram:/text.png", (void*) text_data, sizeof(text_data), &VF_MEMORY},
	{"ram:/picture.png", (void*)picture_data, sizeof(picture_data), &VF_MEMORY}
};

...

// call this once before you attempt to load the images
oslAddVirtualFileList((OSL_VIRTUALFILENAME*)ram_files, oslNumberof(ram_files));

// Then just call the load image function like an external image, just use the ram: device
OSL_IMAGE *text = oslLoadImageFile("ram:/text.png", OSL_IN_RAM | OSL_SWIZZLED, OSL_PF_8888);
oslAssert(text);

OSL_IMAGE *picture = oslLoadImageFile("ram:/picture.png", OSL_IN_RAM | OSL_SWIZZLED, OSL_PF_5551);
oslAssert(picture);

[Moca]

Yes, oslib has a method to load an image internally (rather then externally). Heh, how do you think the intro function is done?

Read your documentation ;)
If you're too lazy here's a sample:

// your 'text' image data
const unsigned long text_data[] = { ... };

// your 'picture' image data
const unsigned long picture_data[] = { ... };

// Your array of virtual files (rather then explain either look at your documentation, even still you should be able to understand this just by looking at it)
const OSL_VIRTUALFILENAME ram_files[] =		{
	{"ram:/text.png", (void*) text_data, sizeof(text_data), &VF_MEMORY},
	{"ram:/picture.png", (void*)picture_data, sizeof(picture_data), &VF_MEMORY}
};

...

// call this once before you attempt to load the images
oslAddVirtualFileList((OSL_VIRTUALFILENAME*)ram_files, oslNumberof(ram_files));

// Then just call the load image function like an external image, just use the ram: device
OSL_IMAGE *text = oslLoadImageFile("ram:/text.png", OSL_IN_RAM | OSL_SWIZZLED, OSL_PF_8888);
oslAssert(text);

OSL_IMAGE *picture = oslLoadImageFile("ram:/picture.png", OSL_IN_RAM | OSL_SWIZZLED, OSL_PF_5551);
oslAssert(picture);

Seems like an overly complicated solution to a simple problem. Surely oslLoadImageFile is just a simple function that opens a file and reads it into a buffer. Then passes the address of that buffer to another function which does the real work.

I'm saying that oslLoadImageFile's purpose should only be to read a file into memory and call another function to do all the image work. All SuperBatXS needs is that function that oslLoadImageFile calls which takes the address of a buffer. No need for overly complicated virtual files in memory.

I don't care much for OSLib since I have no need to use it, just giving advice.

[slicer4ever]

superbat...can i ask why you'r including an image as a header...? especially using oslib, i highly dought your ganna need your image hard-coded into the program, if your that scared of others replacing the image, just load it into the program with oslLoadImageFile, but hey if you rly need to, do wat sg said

[SuperBatXS]

I know what SG57 is saying, but i have no idea what you mean Moca. Could you give a snippet?

Thanks dude,
Sexy...er, SuperBatXS (wait, what's the difference)

[Moca]

I know what SG57 is saying, but i have no idea what you mean Moca. Could you give a snippet?

Thanks dude,
Sexy...er, SuperBatXS (wait, what's the difference)

OSL_IMAGE* oslLoadImageFile(char *filename, int  location, int  pixelFormat)

There should be a function similar to this:
OSL_IMAGE* oslLoadImageBuffer(char *imageBuffer, int location, int pixelFormat)

Or something like that. It would be stupid to rewrite the image loading part of oslib over and over for each different function that blits an image.

[bnc9]

Quick question:When reading from a text file how do you move on to the next line if a certain character is in the current line,something like ignoring comments in a .c file.
Example:
I have a .txt that has

Spoiler for myfile.txt:

255
//This is a line to be ignored
255

and all I need is the two 255's

[_df_]

p = strchr(line, '/');
if(p != NULL && p[1] == '/')
 *p = 0;

assuming your processing linefeeds/crs into nulls or using fgets or doing any kind of post processing etc...

could answer this a million ways. there is a lot of context missing to know how to answer (ie: how are you reading it into memory).

[SG57]

Seems like an overly complicated solution to a simple problem. Surely oslLoadImageFile is just a simple function that opens a file and reads it into a buffer. Then passes the address of that buffer to another function which does the real work.

I'm saying that oslLoadImageFile's purpose should only be to read a file into memory and call another function to do all the image work. All SuperBatXS needs is that function that oslLoadImageFile calls which takes the address of a buffer. No need for overly complicated virtual files in memory.

I don't care much for OSLib since I have no need to use it, just giving advice.

Well the virtual file system is meant for things like that, it offers great flexibility and fancy stuff. True it may seem overly complicated for such a simple thing but it accomplishes the same thing he's looking for and to my oslib knowledge (unmodified Oslib anyway) it's the only way (the data member of an OSL_IMAGE is private IIRC)

[daaa57150]

Quick question:When reading from a text file how do you move on to the next line if a certain character is in the current line,something like ignoring comments in a .c file.
Example:
I have a .txt that has

Spoiler for myfile.txt:

255
//This is a line to be ignored
255

and all I need is the two 255's

C++ style:

ifstream thefile("path/to/myfile.ext");
if(thefile.fail())
{
    //error here
}
string line;
while(getline(thefile, line))
{
    if(line.find("//")!=0) //true if the line does not start with "//"
    {
        //do what you want with line        
    }
}
    
thefile.close(); 

[SG57]

The irony being you wrapped in PHP code tags lol

[bnc9]

thnx daaa57150!! it works perfectly. I wasn't able to use my comp for the past few days (sent for repair) so I didn't see your post.

[eldiablov]

God ... it's such a basic program and yet it doesn't work xD, someone tell me what the problem is please.

    int main(){
    system("Untitled1.exe"); //Program tested with and without this line
    FILE* text;
    text = fopen("crash.log", "w");

    int i;
    char password[256];

    fscanf(text,"%s", password);
    fclose(text);
    printf("%s", password);

    return 0;
}

Its output is:

-LIBGCCW32-EH-3-SJLJ-GTHR-MINGW32

And it seems to be erasing the file crash.log aswell :/
-= Double Post =-
Nvm I know what the problem is, had it in write mode >_<

[MiKeY188]

int main(){
system("Untitled1.exe"); //Program tested with and without this line
FILE* text;
text = fopen("crash.log", "w");

int i;
char password[256];

fscanf(text,"%s", password);
fclose(text);
printf("%s", password);

return 0;
}

I think this might help :)

int main()
{

system("Untitled1.exe"); //Program tested with and without this line
FILE* text;
text = fopen("crash.log", "w");

int i;
char password[256];

fscanf(text,"%s", password);
fclose(text);
printf("%s", password);

return 0;
}

Then again im new to C++

[Moose]

I think this might help :)

int main()
{

#define printf pspDebugScreenPrintf

system("Untitled1.exe"); //Program tested with and without this line
FILE* text;
text = fopen("crash.log", "w");

int i;
char password[256];

fscanf(text,"%s", password);
fclose(text);
printf("%s", password);

return 0;
}

Then again im new to C++

He isn't writing that for the PSP...

[_df_]

your missing an unlink()/remove() to delete the log file once you are done with it.

[MiKeY188]

Lol i still got loads to learn!

[eldiablov]

I think this might help :)

int main()
{

system("Untitled1.exe"); //Program tested with and without this line
FILE* text;
text = fopen("crash.log", "w");

int i;
char password[256];

fscanf(text,"%s", password);
fclose(text);
printf("%s", password);

return 0;
}

Then again im new to C++

Well for one, you cant run EXE's on the PSP ... and that's C not C++

And ulink() ? Never used it before and i'm not gonna start now. Never heard of it ...

[Torch]

Solved.