<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
If build_sdk.sh would have done everything, I would not have posted.<br>
<br>
It failed in some not immediately obvious manner, and I don't have <br>
time to trouble shoot right now. <br>
<br>
By having some README I hope the next poor soul trying to compile
has better luck.<br>
<br>
If nobody steps up, I can try to do a first cut at the readme
myself, but it won't be<br>
done any time soon.<br>
<br>
Harri<br>
<br>
On 02/03/2012 02:37 PM, mingw android wrote:
<blockquote
cite="mid:CAOYw7duxog39wKjp_kTFELq9MUtPfuGb6-HF38+Nua6AKRyJ0A@mail.gmail.com"
type="cite">
<p>./build_sdk.sh does everything for you. But you're right of
course, we need docs!</p>
<div class="gmail_quote">On Feb 3, 2012 10:58 AM, "Harri Pasanen"
<<a moz-do-not-send="true" href="mailto:harri@mpaja.com">harri@mpaja.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
Unfortunately I have very limited time right now for<br>
delving into the guts of necessitas right now.<br>
<br>
That said, I did try to build it so that I could eventually<br>
fix something and contribute.<br>
<br>
Unfortunately it first looped on something as it did not find
ant.<br>
After installing ant it still seemed to loop building
something in java.<br>
<br>
Are there any developer getting started howtos, readmes<br>
or other recommended reading?<br>
<br>
Just one README outlining the following would go a long way:<br>
<br>
* technical overview:<br>
<br>
- java/c++ integration.<br>
- run time, where do the Qt libs live that ministro
downloads?<br>
this could be just a link to some existing material on web.<br>
<br>
* prerequisites (jdk, ant, ndk, path setup, etc.)<br>
<br>
* checkout and build (approximate time on a given machine
spec)<br>
<br>
* testing the build.<br>
<br>
* making local modifications<br>
<br>
* submitting patches<br>
<br>
This README should be in the git repo, or possible at some
wiki,<br>
but the README should then have a link pointing to it.<br>
<br>
If the first build and test is fluid, it is easy for
developers to get sucked into<br>
looking at things, fixing things.<br>
<br>
<br>
Just my 2 cents,<br>
<br>
Harri<br>
_______________________________________________<br>
Necessitas-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Necessitas-devel@kde.org" target="_blank">Necessitas-devel@kde.org</a><br>
<a moz-do-not-send="true"
href="https://mail.kde.org/mailman/listinfo/necessitas-devel"
target="_blank">https://mail.kde.org/mailman/listinfo/necessitas-devel</a><br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>