| View previous topic :: View next topic |
| Author |
Message |
jj_spike
Joined: 14 Jul 2005 Posts: 5
|
Posted: Fri Aug 05, 2005 9:12 am Post subject: doxygen-docs |
|
|
Hello all,
I made the move from Cygwin to a dedicated Suse Linux install. Let me tell you, the speed is far greater and the little update and other problems simply do not exist.
There is still one problem, I cannot generate the SDK documentation. No matter what I enter for the make, I receive the target does not exist error. I am running the an SDK and toolchain that I downloaded just yesterday. This has been a problem for me from the start. Can anyone assist? I would like to generate the PDF version of the SDK functions.
Best regards,
JJ |
|
| Back to top |
|
 |
Agoln

Joined: 08 Jun 2005 Posts: 326 Location: Fort Wayne, IN
|
Posted: Fri Aug 05, 2005 9:18 am Post subject: |
|
|
in the PSPSDK folder, if you do a 'make doxygen-doc', it says that it has no rule for doxygen-doc?
BTW: Welcome to the more stable, better OS... Linux :).
(Now if we could only get you to a debian-based distro, like ubuntu ;-P ) _________________ Lego of my Ago! |
|
| Back to top |
|
 |
jj_spike
Joined: 14 Jul 2005 Posts: 5
|
Posted: Fri Aug 05, 2005 11:25 am Post subject: |
|
|
Actually, I was a Linux guy many years back. I built my first firewall manually with RedHat and ipfwadm MANY years ago. At over 900 rules, it was quite the script. Things have come a long way since then. I use XP as my desktop platform since all of my multimedia and "Enterprise" apps work only on Wintel platforms. I am now using my spare Asus Pundit-R as a Linux desktop since if does not take up too much room. The latest Suse with KDE is quite slick I must say.
The exact error reads:
linux:/home/user1/pspsdk-1.0+beta # make doxygen-doc
make: *** No rule to make target `doc/doxygen.cfg', needed by `doc/pspsdk.tag'. Stop.
I have not coded C for over 18 years. I thought this would be a good re-introduction.
Thanks!
JJ |
|
| Back to top |
|
 |
ector
Joined: 12 May 2005 Posts: 195
|
|
| Back to top |
|
 |
jj_spike
Joined: 14 Jul 2005 Posts: 5
|
Posted: Mon Aug 08, 2005 11:33 am Post subject: |
|
|
I ran the "toolchain.sh" and all items were built. For the life of me, I cannot locate the documentation that was created. Can anyone tell me where the documentation is stored?
Thanks |
|
| Back to top |
|
 |
jason867
Joined: 24 Jul 2005 Posts: 78
|
Posted: Wed Aug 10, 2005 2:50 pm Post subject: |
|
|
I would also like to know where the documentation is stored in the installation. _________________ Ask not for whom the bell tolls, it tolls for thee, besides, I'm playing my PSP, tee hee!
------------------------------------------------------
Visit my website for my PSP Homebrew! |
|
| Back to top |
|
 |
Agoln

Joined: 08 Jun 2005 Posts: 326 Location: Fort Wayne, IN
|
Posted: Wed Aug 10, 2005 11:22 pm Post subject: |
|
|
if you do a checkout of the svn repository (svn checkout svn://svn.pspdev.org/psp/trunk/pspsdk), then you should be able to do a 'make doxygen-doc') and have it work. _________________ Lego of my Ago! |
|
| Back to top |
|
 |
statikeffeck
Joined: 15 May 2005 Posts: 11
|
Posted: Sun Aug 14, 2005 1:18 am Post subject: |
|
|
I can compile any PSP programs without any problems. However I can't compile the docs using the posted instructions. I basically just want to look at the docs for libgu for graphics drawing and manipulation. (a google search for libgu comes up with practically nothing).
I created a new directory called "test1" in my CYGWIN environment.
in test1, I used the command
$> svn checkout svn://svn.pspdev.org/psp/trunk/pspsdk
When it was finished, I had a new directory called pspsdk.
In that dir, I did
$> make doxygen-doc
Received error:
make: *** No rule to make target `doxygen-doc'. Stop.
The directory pspsdk/doc is empty, as well as the pspsdk/doc/html directory is empty. |
|
| Back to top |
|
 |
Agoln

Joined: 08 Jun 2005 Posts: 326 Location: Fort Wayne, IN
|
Posted: Sun Aug 14, 2005 4:51 am Post subject: |
|
|
Good plan | Quote: |
When it was finished, I had a new directory called pspsdk.
In that dir, I did
$> make doxygen-doc
| do a ./bootstrap first _________________ Lego of my Ago! |
|
| Back to top |
|
 |
statikeffeck
Joined: 15 May 2005 Posts: 11
|
Posted: Sun Aug 14, 2005 5:11 am Post subject: |
|
|
Thanks.
Besides ./bootstrap, I also had to run ./configure (not sure why).
Summary for newbies to get full current docs:
> svn checkout svn://svn.pspdev.org/psp/trunk/pspsdk
> cd pspsdk
> ./bootstrap
> ./configure (might be optional step)
> ./make doxygen-doc
Open pspsdk/docs/html/index.html in a web browser. |
|
| Back to top |
|
 |
mrbrown
Joined: 17 Jan 2004 Posts: 1536
|
Posted: Sun Aug 14, 2005 9:54 am Post subject: |
|
|
| Thanks for repeating information found in the PSPSDK README. |
|
| Back to top |
|
 |
remleduff
Joined: 24 Jul 2005 Posts: 11
|
Posted: Sun Aug 14, 2005 6:28 pm Post subject: |
|
|
Here are a couple of toolchain fixes that might be useful.
Specifically, I think it makes more sense for the doc directory to end up in /usr/local/pspdev/psp/sdk/doc instead of being left in the downloaded directory (which is deleted when the toolchain script finishes).
Also, I changed the toolchain script to automatically build the docs when the sdk is updated (I don't think leaving old documentation around makes sense when using new code).
There's also a small fix to quiet the toolchain script when it tests for missing commands.
Without I get errors that I don't care about since I have "make" and "patch" installed:
./toolchain.sh: line 73: gmake: command not found
./toolchain.sh: line 85: gpatch: command not found
psptoolchain diff:
| Code: | Index: toolchain.sh
===================================================================
--- toolchain.sh (revision 848)
+++ toolchain.sh (working copy)
@@ -61,7 +61,7 @@
# Newlib depends on PSPSDK headers, so if it's being built
# then make sure that PSPSDK is being built.
- if test $BUILD_NEWLIB ; then
+ if test $BUILD_NEWLIB; then
BUILD_PSPSDK=1
fi
@@ -70,10 +70,10 @@
###########################
## Check for make.
- if test "`gmake -v`" ; then
+ if test "`gmake -v 2>/dev/null`" ; then
MAKE="gmake"
else
- if test "`make -v`" ; then
+ if test "`make -v 2>/dev/null`" ; then
MAKE="make"
else
echo "ERROR: Please make sure you have GNU 'make' installed."
@@ -82,10 +82,10 @@
fi
## Check for patch.
- if test "`gpatch -v`" ; then
+ if test "`gpatch -v 2>/dev/null`" ; then
PATCH="gpatch -p1"
else
- if test "`patch -v`" ; then
+ if test "`patch -v 2>/dev/null`" ; then
PATCH="patch -p1"
else
echo "ERROR: Please make sure you have 'patch' installed."
@@ -94,7 +94,7 @@
fi
## Check for wget.
- if test "`wget -V`" ; then
+ if test "`wget -V 2>/dev/null`" ; then
WGET="wget --passive-ftp"
else
echo "ERROR: Please make sure you have 'wget' installed."
@@ -102,7 +102,7 @@
fi
## Check for subversion.
- if test "`svn help`" ; then
+ if test "`svn help 2>/dev/null`" ; then
SVN="svn"
else
echo "ERROR: Please make sure you have 'subversion (svn)' installed."
@@ -331,6 +331,8 @@
## Install the result.
$MAKE install || { echo "ERROR INSTALLING PSPSDK"; exit; }
+ $MAKE doxygen-doc || { echo "ERROR MAKING DOXYGEN DOCS"; exit; }
+
## Clean up the result.
$MAKE clean |
pspsdk diff:
| Code: | Index: configure.ac
===================================================================
--- configure.ac (revision 847)
+++ configure.ac (working copy)
@@ -34,17 +34,6 @@
AC_FUNC_MEMCMP
AC_CHECK_FUNCS([getcwd strchr])
-# Doxygen.
-DX_HTML_FEATURE(ON)
-DX_CHM_FEATURE(OFF)
-DX_CHI_FEATURE(OFF)
-DX_MAN_FEATURE(OFF)
-DX_RTF_FEATURE(OFF)
-DX_XML_FEATURE(OFF)
-DX_PDF_FEATURE(OFF)
-DX_PS_FEATURE(OFF)
-DX_INIT_DOXYGEN(pspsdk, doxygen.cfg, doc)
-
# Override the default prefix to point to where the pspdev tools should be installed.
# The binaries will end up in $prefix/bin, but pspsdk itself will end up in $prefix/$target/sdk.
# TODO: We should see if the user will ever want to override this.
@@ -71,6 +60,17 @@
AC_SUBST(PSPSDK_CFLAGS)
AC_SUBST(PSPSDK_CXXFLAGS)
+# Doxygen.
+DX_HTML_FEATURE(ON)
+DX_CHM_FEATURE(OFF)
+DX_CHI_FEATURE(OFF)
+DX_MAN_FEATURE(OFF)
+DX_RTF_FEATURE(OFF)
+DX_XML_FEATURE(OFF)
+DX_PDF_FEATURE(OFF)
+DX_PS_FEATURE(OFF)
+DX_INIT_DOXYGEN(pspsdk, doxygen.cfg, "$pspsdk/doc")
+
# Turn on all warnings (for host programs).
if test x$ac_compiler_gnu = xyes; then
CFLAGS="$CFLAGS -Wall"
|
|
|
| Back to top |
|
 |
ooPo Site Admin
Joined: 17 Jan 2004 Posts: 2032 Location: Canada
|
Posted: Sun Aug 14, 2005 6:46 pm Post subject: |
|
|
| I've updated the toolchain.sh in svn as suggested with some minor modifications. |
|
| Back to top |
|
 |
remleduff
Joined: 24 Jul 2005 Posts: 11
|
Posted: Sun Aug 14, 2005 7:11 pm Post subject: |
|
|
Looks great, thanks. :)
Without the change to configure.ac in pspsdk, the docs will just be immediately "cleaned up" at the end of the toolchain script because they'll be installed in "/tmp/pspsdev/pspsdk/doc" by default. |
|
| Back to top |
|
 |
jimparis
Joined: 10 Jun 2005 Posts: 1179 Location: Boston
|
Posted: Thu Oct 20, 2005 3:52 pm Post subject: |
|
|
| The toolchain script now copies the built docs to /usr/local/pspdev/psp/sdk/doc, so if you have doxygen installed when you build the toolchain, you should be able to point your browser to file:///usr/local/pspdev/psp/sdk/doc/html/index.html when it's done. |
|
| Back to top |
|
 |
Panajev2001a
Joined: 20 Aug 2005 Posts: 100
|
Posted: Thu Feb 02, 2006 3:57 am Post subject: |
|
|
| I use the toolchain script (the perl based one) and no docs directory is created (just checked). |
|
| Back to top |
|
 |
|