> I'm not so sure that I'll appreciate this 'all-in-one' solution. I can live with multiple scripts or a single one, but having a single script can ease new users to work with jallib. I was planning to create a script dedicated to tests, and Joep suggests to create one main script (which I understand). So I started to create this, but we decide to come back.
What do you all want ? Main/single script ? Several ? > For compiling I use Make most of the times. In the case of the blink > samples to test the device files I call the JSG script and compiler from > a rexx script. I don't think a Python makes it better or easier for me. > For other libraries and test programs I validate the library only just > before committing, but compile the program many times via Make. 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 ? > Some early experiences (with eComStation): > > The file 'Jallib' is not recognised as an executable on my system, and I > don't know how to make that work. When I rename it to jallib.py and > call python to run it, 'validate' works OK. I don't know how executable are declared on eComStation... Ain't SVN checkout it as executable ? What "svn pl jallib" says ? Is there any kind of PATH ? I think you don't have to rename it with a .py extension, "python jallib ..." should work (python's "import" needs files to have .py, not main script) > Maybe I'm overlooking something, but for compilation it seems to require > a lot of typing on the commandline! I could simplify it, but it also needs to be flexible. Using env variable can simplify it (though again, I don't know how env variables are handled in all our different OS) > The jallib_repos environment seems not to work properly with compile. How do you set it ? env variable (how ?) ? -R option ? > When I set it to 'k:/jallib' it reports that it cannot find directory > 'k'. When I specify '/jallib' I get lots of text on my screen among > which all sample directories: making a commandline of about 16 KB long! That ain't suprise me... jallib structure is very deep. I've tested on my machine (Linux), and yes it produces a ~16KB long ! Using a "find" searching for all subdirs, except .svn, it produces the same kind of cmd line. In a word: it's normal. > With '/jallib/unvalidated/include/' it generates a reasonable 'cmd' > with an include string of about 1000 bytes long. But it did not compile. > I got an error message about 'not enough memory'. This maybe caused by > exceeding the maximum commandline length (I'm not sure but I vaguely > remember 1KB, I never hit that limit before). On linux, it's usually 16535 chars IIRC. How do you produce your own cmd line on eCom ? Don't you consider all subdirs ? > So I think for the moment I'll have to stick to the makefile method with > selective includes: only the directories I actually need for a program > (with 'file not found' I quickly see which I forgot!). OK I have my answer... > Wouldn't it be nice if the compiler would search subdirectories! That would be the simpler. > The include string contains some undesired chars. Have a look at the > > beginning of the generated commandline: > > cmd: jalv2 -s > > /jallib/unvalidated/include/\;/jallib/unvalidated/include/device\;/jallib > > The '/\' at the end of each directory spec is undesired. When I leave > out the terminating '/' in jallib_repos I get only the '\', which may > work (apart from the memory problem). I escape the "\" before the ";", else it's detected as the end of the cmd line under Linux. Having ";" as a separator is quite a weird choice... Anyway, this seems to be a "leak" while trying to have a platform-independent script. Could you send me some examples of how you build your cmd line ? With different subdirs ? 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 -~----------~----~----~----~------~----~------~--~---
