Isn't this because you (we) don't use the magical jallib wrapper (I'm on it)
? I mean, we 'd talked about using the -i option of jalv2 compiler:

  jalv2 -i board_16f877a_dwarf .jal i2c_test_l0.jal

This being integrated within a nice jallib wrapper script (dunno yet what it
would look like).

So I think tests may not be included, even if it sounds logical they could
from your example. Let's assume we agree tests files (not samples) should be
prefixed with "test_", and can be included (only for testing purpose, not as
a start for a new project). Samples, on the contrary, aren't designed to
included (would be a very bad idea), and are stored in "by_device" map.
Finally, when releasing, libs (ie. everything in "include") will be flatten,
all others things, like samples and tests, won't. From there, people do what
they want: if they want to flatten more, they can do it, we @ jallib provide
the "standard" way to use a jallib release: a dir contains all the libs,
then a separate structure containing samples and tests (and doc) help users
to use these libs

Seb

2008/9/30 Joep Suijs <[EMAIL PROTECTED]>

> What I do now when developing/testing is to 'expand' the full jallib tree
> as an include path for the compiler. My main file only contains 2 lines
> like:
>
> include board_16f877a_dwarf
> include i2c_test_l0
>
> This way, I can build any test from the most recent files without the
> burden of (error prone) copying of files back and forth. For this, it is
> nescesarry that the board and test files have unique names and is good if
> there is some naming convention. Maybe we should use a test_ prefix on the
> test files, like we do with the board files.
>
> So, we don't agree (yet) if your statement also applies to test files. I
> don't have an opinion on the naming convention of sample files, as long as
> they don't interfere with libs, board and test files.
>
> Joep
>
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to