Hi Seb,
Sebastien LELONG wrote:
> 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.
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.
For the device files it is different, but that is done...
>> 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 ?
SVN pl jallib says:
Properties on 'jallib':
svn:executable
But I don't think this 'attribute' is of any significance to eCS.
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
> 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)
You are right, it works without the '.py' too.
> 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)
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).
>> The jallib_repos environment seems not to work properly with compile.
>
> How do you set it ? env variable (how ?) ? -R option ?
I should have said it works but processing the contents has quirks!
>> 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.
> 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.
> Could you send me some examples of how you build your cmd line ? With
> different subdirs ?
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.
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
-~----------~----~----~----~------~----~------~--~---
