The wrapper is not mandatory, except maybe to validate files, since
jsg_validator.py will soon disappear.
Compiling can be done without it, as you explain, and it just build the
commandline with -s option. I hope it can still be used by newbies, to make
the repos easy to use. But also remember it's highly configurable: you can
select one or more places to recursively find libs, and you can specify the
jalv2 binary. So, I'd say if you want, you could use it in your makefile (not
much value added, probably...). I use it because once configured (correct env
variables), it's quite pleasant to use. But that's for my needs, you probably
don't have the same.
Finally, testing is maybe where we all should use it. Again, you can deal with
the matrix manually, but using the wrapper really makes our live easier (I
hope). Speaking about the matrix, I think we can't just put our test results
somewhere, in a wiki page like we do now, because it's barely not parsable,
typos error prone, lacks informations, ... If we all adhere to the matrix
(!), and the wrapper, things can be easy (again I hope), with a lot of value
added: mainly a matrix html file and dedicated test result page for each PIC
(have you seen my last try), and an history of what we tested through the svn
revisions.
Registering a test result is easy as:
jallib test -a 16f88:test_serial_hardware.jal:true
This line does the following:
* ensure the PIC exists
* ensure the test file exists, and is under SVN
* ensure "true" is an understood state (true/null/false)
* retrieve svn information about the test
* add all these informations to the matrix
* (it could also retrieve the device file revision used to perform the test)
Instead of getting svn revision for this test, open the matrix file, edited it
without typos. Updating the matrix with new available tests is also
completely automated, doing it manually... well, no one here would do it
manually !
You may say why bother registering all those test results. At least, we did it
for blink files, validating the underlying device file. There can be quite
few differences between device files which could make a sample working or
not. So it's important tracking how we test them, by specifying the svn
revision, for instance.
So, the "test" action is IMHO important. Development about it is quite done
now, we should start filling the matrix. If you like it, of course :)
Also see the wiki page for more.
Cheers,
Seb
> Hi Seb,
>
> I don't use it.
> I maintain files in my editor and have a 'project file' for this
> editor in my jallib-test directory, so the editor knows (amongst other
> things) where the base of the project is. In the same directory is a
> makefile which can be fired from my editor and the output is shown in
> the editor.
> In the makefile, i define the build process I want, like what the
> compile command is (including path to the desired compiler, libs etc).
> This way I can use numerous compilers, programmers, downloaders, just
> by adapting the makefile for any of my zillion projects.
>
> So I don't feel a need to use the wrapper.
>
> (But maybe I should, that's why I tell you my setup).
>
> Joep
>
> 2008/11/15, Sebastien LELONG <[EMAIL PROTECTED]>:
> > Hi,
> >
> > I've updated the wiki page jallib wrapper (which is less and less a
> > wrapper btw):
> >
> > http://code.google.com/p/jallib/wiki/UsingJallibWrapper
> >
> > Specifically, I've added usage information, near the end,
> > sectio 'Using "jallib"'. You'll have an overview of what can be done.
> >
> > Some questions... Do you use the wrapper ? If so, for what actions
> > (compile, validate, test) ? Do you use the win exe ? Or did you install
> > dependencies ? Even pysvn ?
> >
> >
> > Seb
> > --
> > Sébastien LELONG
> > http://www.sirloon.net
> > http://sirbot.org
>
>
--
Sébastien LELONG
http://www.sirloon.net
http://sirbot.org
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
