I know in CVS there is anon-access... maybe the have something like that for subV?KaL wrote:I would like to download PSPSDK from the subversion repository.. but I need login/password. Where can I get it ? Thanks.
PSPSDK 1.0+beta released!
Doesn't tell me how to do it :/PSPSDK 1.0+beta is availble for download here. If you would like to keep upto date with the latest version, you can also access our subversion repository at "svn://svn.ps2dev.org/psp". We have also setup a new list to monitor subversion commits and submit bug reports which you can join at lists.ps2dev.org.
Here's some instructions, assuming you have svn installed:
Code: Select all
svn checkout svn://svn.pspdev.org/psp/trunk/pspsdk
cd pspsdk
./bootstrap
./configure
make
make install
Thanks. I knew this already. mind you, but thanks.ooPo wrote:Here's some instructions, assuming you have svn installed:
Code: Select all
svn checkout svn://svn.pspdev.org/psp/trunk/pspsdk cd pspsdk ./bootstrap ./configure make make install
-
- Posts: 12
- Joined: Thu Nov 04, 2004 8:08 am
ok, I feel really dumb here...Im still having problems getting the sdk to work. I installed the psptoolchain (the most recent version) and I downloaded the pspsdk (I use cygwin btw) and uncompressed it. When I run ./configure, it tells me pspdev is not found and it stops :(. Now I think it could be because I'm having a hard time 'setting my envornment variables', which I thought I set (I use XP, so I set them thru my computer, etc.).
Also, I read the sticky here about the toolchain, and particularly the '-p' option. Can I just use this to install the pspsdk? Or do I have to have it already installed, and that just updates it?
Also also, can I just use the svn instructions you provided ooPo?
btw, I installed all the packs with cygwin; and I'n not awesome with *nix yet
Also, I read the sticky here about the toolchain, and particularly the '-p' option. Can I just use this to install the pspsdk? Or do I have to have it already installed, and that just updates it?
Also also, can I just use the svn instructions you provided ooPo?
btw, I installed all the packs with cygwin; and I'n not awesome with *nix yet
The svn instructions I provided are right out of the toolchain.sh script. Take a look at it inside a text editor sometime if you're curious.
The latest toolchain script, when run from inside a fully installed cygwin environment, should build the toolchain AND the latest version of pspsdk from svn automatically. You don't need to specify any options on the command line - it defaults to building everything. Using 'toolchain.sh -p' is only needed if you've already installed the toolchain and just want to update pspsdk.
When it finishes building, make sure you follow the instructions in the readme - specifically the part about setting your path and $PSPDEV variables.
The latest toolchain script, when run from inside a fully installed cygwin environment, should build the toolchain AND the latest version of pspsdk from svn automatically. You don't need to specify any options on the command line - it defaults to building everything. Using 'toolchain.sh -p' is only needed if you've already installed the toolchain and just want to update pspsdk.
When it finishes building, make sure you follow the instructions in the readme - specifically the part about setting your path and $PSPDEV variables.
-
- Posts: 12
- Joined: Thu Nov 04, 2004 8:08 am
-
- Posts: 41
- Joined: Sat Jul 02, 2005 10:12 am
I followed everything you said. Minus the having to install doxygen part which you left out. But anyway. I am getting an error that perhaps you can help me with:ooPo wrote:Here's some instructions, assuming you have svn installed:
Code: Select all
svn checkout svn://svn.pspdev.org/psp/trunk/pspsdk cd pspsdk ./bootstrap ./configure make make install
Code: Select all
make[3]: Entering directory `/home/Nick Fury/pspsdk/trunk/pspsdk/sdk/audio'
/bin/sh: PSP_CC@: command not found
make[3]: *** [audio.o] Error 127
Which he left out? You have quite the attitude for someone incapable of following the directions given in the PSPSDK README.Nick Fury wrote:I followed everything you said. Minus the having to install doxygen part which you left out. But anyway. I am getting an error that perhaps you can help me with:
I openly admit to being a jackass and a smartass. It's what I do best. Perhaps from working tech support all day I've turned into a very bitter person.mrbrown wrote:Which he left out? You have quite the attitude for someone incapable of following the directions given in the PSPSDK README.
I'm joking man. I know how to follow directions. I've setup the SDK on two other machines and that error message popped up while I was setting it up under Cygwin on my home machine (for the second time as I had some drive troubles recently). I would like to know about the error. I couldn't seem to find anything about it in either the README or on these forums.
As for being incapable. I assure you I'm not. My question about the status of the next release was not me meaning to push you guys. I'm well aware that you are working hard on it.
However in other threads there were members of your team stating such things as "It should be out by this weekend" or "it should be out in a few days". If it's not going to be released for two weeks then please don't say two days.
ok im quite sure this is a n00b question, but the are or are not the lib funcs released in the other threads c++ functions? if so, why are there not prototypes for all of them, and if this reason is because they have not been hashed yet, how can i help the hashing prosses? (/me has acsess to a mini cluter on a t1 network)
We place no restrictions on what you do with what you produce using our SDK.
That said, it's not to say that Sony won't take a keen interest in you making money off of selling something for the PSP since they're not getting a cut.
Sony and homebrew have always peacefully coexisted but then again noone has tried charging for homebrew before. I have a sneaking suspicion you'd be hearing from Sony's lawyers if you start charging for your software. I just hope they don't come knocking on our door too.
That said, it's not to say that Sony won't take a keen interest in you making money off of selling something for the PSP since they're not getting a cut.
Sony and homebrew have always peacefully coexisted but then again noone has tried charging for homebrew before. I have a sneaking suspicion you'd be hearing from Sony's lawyers if you start charging for your software. I just hope they don't come knocking on our door too.
-
- Posts: 41
- Joined: Sat Jul 02, 2005 10:12 am
I wholeheartedly believe to give credit where credit is due. With that said, I just wanted to say thanks to all the people who helped developed the PSPSDK. I knew absolutely nothing about psp programming 2 months ago, and now I'm happily writing programs and recently landed in a little psp programming gig. Without you guys, I wouldn't have gotten this far. I hope to see 2.0 cracked so I can continue to dev for this fun little computer.
W32 PSPtoolchain
Hi May I know where to get W32 PSPtoolchain?
Thanks
Thanks
PSPSDK keeps on trucking with updates
all the time in svn ....checking svn logs
shows that the sdk is getting a lot of updates
frequently ....as for progress on another beta
then time will tell ...but if you want the
freshest most up to date PSPSDK then
you cant go wrong with svn co svn://ps2dev.org/psp/trunk/pspsdk ;)
cheers
all the time in svn ....checking svn logs
shows that the sdk is getting a lot of updates
frequently ....as for progress on another beta
then time will tell ...but if you want the
freshest most up to date PSPSDK then
you cant go wrong with svn co svn://ps2dev.org/psp/trunk/pspsdk ;)
cheers
10011011 00101010 11010111 10001001 10111010
./configure
checking for pspsdk version... 1.0+beta
checking for pspdev... /usr/local/pspdev
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for psp-gcc... no
checking for psp-as... no
checking for psp-ld... no
checking for psp-ar... no
checking for psp-nm... no
checking for psp-ranlib... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for ranlib... ranlib
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for working memcmp... yes
checking for getcwd... yes
checking for strchr... yes
checking for doxygen... no
configure: WARNING: doxygen not found - will not generate any doxygen documentation
checking for perl... /usr/bin/perl
configure: creating ./config.status
config.status: creating Makefile
config.status: creating sdk/Makefile
config.status: creating sdk/audio/Makefile
config.status: creating sdk/base/Makefile
config.status: creating sdk/debug/Makefile
config.status: creating sdk/kernel/Makefile
config.status: creating sdk/libc/Makefile
config.status: creating sdk/startup/Makefile
config.status: creating sdk/samples/Makefile
config.status: creating tools/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
sorry for asking these questions, i finaly got the psptoolchain installed now this wont work :(make
make all-recursive
make[1]: Entering directory `/home/h/harleyg/pspsdk/pspsdk-1.0+beta'
Making all in sdk
make[2]: Entering directory `/home/h/harleyg/pspsdk/pspsdk-1.0+beta/sdk'
Making all in audio
make[3]: Entering directory `/home/h/harleyg/pspsdk/pspsdk-1.0+beta/sdk/audio'
no -g -O2 -G0 -Wall -I../../sdk/base -I../../sdk/kernel -c `test -f 'audio.S' || echo './'`audio.S
/bin/sh: no: command not found
make[3]: *** [audio.o] Error 127
make[3]: Leaving directory `/home/h/harleyg/pspsdk/pspsdk-1.0+beta/sdk/audio'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/h/harleyg/pspsdk/pspsdk-1.0+beta/sdk'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/h/harleyg/pspsdk/pspsdk-1.0+beta'
make: *** [all] Error 2
here's a permanent mirror:TommyBear wrote:Thanks so much guys! Win32 installer that i made available here: http://www.tomkatgames.com/psp/setup.exe (25MB). Basically the same deal as the ps2dev kit installer
Enjoy everyone!
http://0.dr.ag/REMOTEUPLOAD?url=http:// ... /setup.exe
for future bigfiles use this technique:
just put
Code: Select all
http://0.dr.ag/REMOTEUPLOAD?url=
-
- Posts: 1
- Joined: Wed Mar 29, 2006 2:35 pm