[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: API dox
From:       "Nathan Bradshaw" <nathanlbradshaw () gmail ! com>
Date:       2008-06-14 14:07:39
Message-ID: 92af7fc70806140707l6a6bfa8cq1ae6c3fdba2a19a1 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Thanks for the heads up Allen, I actually have no idea how i missed that
section of TB.... I'd searched around and found the policies and guidelines
but somehow missed that section :|

cheers
N

On Sat, Jun 14, 2008 at 10:04 AM, Allen Winter <winter@kde.org> wrote:

> On Saturday 14 June 2008 09:35:48 Nathan Bradshaw wrote:
> > Hi all, sorry if this is a FAQ but my searching around has not really
> > revealed a definitive answer to this...
> >
> > I'm trying to be a good boy and doing a thorough job of documenting all
> my
> > code. All the references to building apidox still refer to the old
> > autotools, so I'm wondering what the CMake way of doing this is? I'd like
> > to build and review them locally before committing and letting EBN catch
> > all my mistakes :)
> >
> I see this question too often.
> I'll write a script and put it in kdesdk/scripts.
>
> In the meantime, there is
>
> http://techbase.kde.org/Getting_Started/Build/KDE4#Generating_local_API_documentation
>
>
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> unsubscribe <<
>

[Attachment #5 (text/html)]

Thanks for the heads up Allen, I actually have no idea how i missed that section of \
TB.... I&#39;d searched around and found the policies and guidelines but somehow \
missed that section :|<br><br>cheers<br>N<br><br><div class="gmail_quote"> On Sat, \
Jun 14, 2008 at 10:04 AM, Allen Winter &lt;<a \
href="mailto:winter@kde.org">winter@kde.org</a>&gt; wrote:<br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> <div><div></div><div class="Wj3C7c">On Saturday 14 \
June 2008 09:35:48 Nathan Bradshaw wrote:<br> &gt; Hi all, sorry if this is a FAQ but \
my searching around has not really<br> &gt; revealed a definitive answer to \
this...<br> &gt;<br>
&gt; I&#39;m trying to be a good boy and doing a thorough job of documenting all \
my<br> &gt; code. All the references to building apidox still refer to the old<br>
&gt; autotools, so I&#39;m wondering what the CMake way of doing this is? I&#39;d \
like<br> &gt; to build and review them locally before committing and letting EBN \
catch<br> &gt; all my mistakes :)<br>
&gt;<br>
</div></div>I see this question too often.<br>
I&#39;ll write a script and put it in kdesdk/scripts.<br>
<br>
In the meantime, there is<br>
<a href="http://techbase.kde.org/Getting_Started/Build/KDE4#Generating_local_API_documentation" \
target="_blank">http://techbase.kde.org/Getting_Started/Build/KDE4#Generating_local_API_documentation</a><br>
 <br>
<br>
<br>
&gt;&gt; Visit <a href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub" \
target="_blank">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> to \
unsubscribe &lt;&lt;<br> </blockquote></div><br>



>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]