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