> > I can't see why using this wrapper would cause problem using a Makefile. > > You'd > > just have to change the target to include "jallib compile..." or "jallib > > validate...". No ? > > I don't understand what you mean exactly with the last sentence above.
What you do with the jalv2 compiler can be done with jallib wrapper. You can specify multiple entry point the hierarchy, ":" seperated. Ex: jallib compile -R k:/jallib/unvalidated/include/device:k:/jallib/ unvalidated/include/peripheral/usart:k:/jallib/unvalidated/include/jal echo.jal > > My main objections against 'jallib compile' (as it is setup now) are > briefly: > The directory structure of Jallib is only a (potential) issue for the > library developers. But testing a library doesn't need many different > programs, and if more than one the programs will be pretty similar. > Building a makefile for a new program is not much work (copy and modify > a previous makefile) and it needs to specify only those directories > which are needed. It forces me to think(!), but only once with the > initial setup. It won't give a very long '-s string' and calling Make > does not require much commandline typing. Having a Makefile and a jallib wrapper is different. You can include the jallib script within your Makefile, with specific directories inclusion, and just put the whole in a Makefile so typing "make" will do the trick. Everybody then uses what they want to script their compilation steps. > SVN pl jallib says: > Properties on 'jallib': > svn:executable > > But I don't think this 'attribute' is of any significance to eCS. OK, I was hoping the SVN client would do the trick... > > eCS is in this respect to a large extent the same as DOS and Windows. > There is a PATH environment variable, but you can also explicitly > specify the path of the executable on the commandline like: > k:\jallib\tools\jallib The problem is then how to tell which interpreter to use. The shebang "#!/usr/bin/python" at the beginning of the file is only understood under Linux... I think for Windows people have to use a py2exe program, to build a standalone windows executable. > An environment variable is set with the SET command, for example: > > set JALLIB_REPOS=/jallib/unvalidated/include > > similary as export in Linux (but then between double quotes). OK. (you don't need double quotes under Linux BTW). > >> When I set it to 'k:/jallib' it reports that it cannot find directory > >> 'k'. > > You didn't to react on that: the volume specification is important. > Usually programs and data are on the same volume and then you don't need > the drive letter, otherwise it must be possible to specify the volume > letter. I need more investigation on this... > > How do you produce your own cmd line > > on eCom ? Don't you consider all subdirs ? > > I specify only the needed directories. With the restriction of a > maximum commandline of (possibly) 1K I don't see an alternative. OK, and you can do the same with jallib wrapper, by specifying those specific dirs, ":" seperated, for the -R option or env variable. > I'll send you a makefile of the echo-program which I sent you earlier, > together with the created asm output (which contains the command line) > and console log. OK got it, thanks. About the "/\" chars within the cmd line, as I said, I need to escape ";" char under linux. But that's because I let python "submit" the cmd line to the shell. Then the shell interprets it, thus the need of escape "\" chars. This is my mistake, I need not to use the shell, and directly call the program. I'm on it too ! Seb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
