Author: eur.van.andel
Date: Thu Nov 20 00:13:14 2008
New Revision: 581
Modified:
wiki/UnderstandingSvnStructure.wiki
Log:
Edited wiki page through web user interface.
Modified: wiki/UnderstandingSvnStructure.wiki
==============================================================================
--- wiki/UnderstandingSvnStructure.wiki (original)
+++ wiki/UnderstandingSvnStructure.wiki Thu Nov 20 00:13:14 2008
@@ -4,7 +4,7 @@
= Why having such a structure ? =
-_"Yes, why having such a (complicated) structure ?"_ you mask, humble
visitor... Current jalv2 compiler version cannot handle include statements
in sub-directories, so this is a legitimate question.
+_"Yes, why having such a (complicated) structure ?"_ you ask, humble
visitor... Current jalv2 compiler version cannot handle include statements
in sub-directories, so this is a legitimate question.
We, the jallib team, decided to have such a structure because
@@ -13,7 +13,7 @@
_"Yes, but will I have to deal with all these sub-directories ?"_ you then
may ask, curious visitor. Two possibilities:
- * you want to live on the cutting hedge of jallib, you want to have the
very last version of this library. You have to work directly against SVN
files. So, yes, you'll have to deal with all thses sub-directories.
Fortunately, this [UnixCompilingFromSvnHowto page] can help you getting
started with compiling from SVN.
+ * you want to live on the cutting edge of jallib, you want to have the
very last version of this library. You have to work directly against SVN
files. So, yes, you'll have to deal with all thses sub-directories.
Fortunately, this [UnixCompilingFromSvnHowto page] can help you getting
started with compiling from SVN.
* the cutting hedge is too dangerous for you, you want stable things,
validated libs. You want to [http://code.google.com/p/jallib/downloads/list
download] a package. In this package, all libraries are put into a single
directory, just as usual. See HowtoInstallJallib for more.
@@ -103,5 +103,3 @@
So, for instance, in `test/peripheral/usart`, you'll find test dedidated
to USART libraries. These tests are mixed up with a "board" file
(from "board" directory). A _board_ file and a _test_ file gives a
functional, compilable piece of code, which will perform the selected test
on the selected target, using the selected board.
"Woah" I hear you say... "What is it such complicated ?" It's not
complicated. At least, this apparent complexity avoid code duplication, and
permits to seperate the test logic, from the board/target chip setup. Each
type of file focus on a specific task. Don't worry about all of this:
unless you plan to contribute to jallib as a developper, you won't need all
of these. But... we'd be please if you help :)
-
-
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---
