Hi Seb,
Sebastien LELONG wrote: > I've just committed the first draft of "jallib", the magical main wrapper > script, which aims to ease working with jallib. For instance, it can compile > files by expanding dirs and build the -s option, platform-indepently. I'm not so sure that I'll appreciate this 'all-in-one' solution. 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'd need you to test it on several platforms, particularly on windows, macos, > os2, etc... This script is developed in python, I tried to make the code > multi-platforms, though I've quite never had to do this, so > except "surprises". 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. Maybe I'm overlooking something, but for compilation it seems to require a lot of typing on the commandline! The jallib_repos environment seems not to work properly with compile. 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! 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). 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!). Wouldn't it be nice if the compiler would search subdirectories! 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). Regards, Rob. -- Rob Hamerling, Vianen, NL (http://www.robh.nl/) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
