[jallib] r3086 committed - Added DOS version of 2.4p and readme.txt

[jal...@googlecode.com]

Revision: 3086
Author: robhamerling
Date: Mon Sep 3 11:58:49 2012
Log: Added DOS version of 2.4p and readme.txt


http://code.google.com/p/jallib/source/detail?r=3086

Added:
/trunk/compiler/README.txt
/trunk/compiler/jalv2d.exe

[Rob Hamerling]

Hi guys,

On 3-09-12 20:59, jal...@googlecode.com wrote:
> Revision: 3086
> Author: robhamerling
> Date: Mon Sep 3 11:58:49 2012
> Log: Added DOS version of 2.4p and readme.txt

Kyle releases also a DOS version of JalV2, but I noticed that it was not
in SVN, and I just added it. Did I forget why we excluded it from our
JALPACK distributions or was it simply forgooten and nobody noticed
until now?

Regards, Rob.

--
R. Hamerling, Netherlands --- http://www.robh.nl

[Sebastien Lelong]

Hi Rob,

I'm sure to understand what you mean by "DOS version", but jalv2, from Kyle's zip, usually have a Linux ("jalv2") and a Windows ("jalv2.exe") version, but no DOS version. What could be the use ? Isn't Windows version enough ?

Cheers

Seb

--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to jal...@googlegroups.com.
To unsubscribe from this group, send email to jallib+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jallib?hl=en.

--
Sébastien Lelong

[Rob Hamerling]

Hi Seb,

On 4-09-12 07:26, Sebastien Lelong wrote:
>
> I'm sure to understand what you mean by "DOS version", but jalv2, from
> Kyle's zip, usually have a Linux ("jalv2") and a Windows ("jalv2.exe")
> version, but no DOS version. What could be the use ? Isn't Windows
> version enough ?

Probably for most people the Windows version will be enough, but not for
everybody. I think the Linux version will be used, and I'm sure about
the eCS version. I wouldn't know if anybody is interested in the DOS
version, but I think it's only fair to Kyle to distribute the whole
original package (except the include files for which we have replacements).

You probably saw my fixes of some serial libraries. There is now only
one sample left with a warning: 18f27j53_sd_card_minix_read.jal.
It a sample of yours, could you have a look, please.

[Sebastien Lelong]

Hi Rob
I'll have a look at the sample.
Is there any chances to have an OSX version of jalv24p ? ;)
Cheers
Seb

[Rob Hamerling]

Hi Seb,

On 4-09-12 10:01, Sebastien Lelong wrote:

> Is there any chances to have an OSX version of jalv24p ? ;)

We should have!
And I suppose it won't be much work. The OS/2, Linux and Windows
versions which I build here with Open Watcom C/C++ from the sources Kyle
distributes give no errors or warnings. Unfortunately I have not the
environment to create, let alone test an OSX version.
But I thought you did build an OSX version last year, at least there is
one in Jallib with your name....

[zmafoox]

Greetings,

There is no DOS jalv24p version. jalv24d.exe is the debug version. I've no idea why I always include it.

[Rob Hamerling]

Hi Kyle,

On 4-09-12 22:46, zmafoox wrote:
>
> There is no DOS jalv24p version. jalv24d.exe is the debug version. I've
> no idea why I always include it.

Sorry, my mis-interpretation of the 'd' suffix. I'll remove it from Jallib.

One reason for my mis-interpretation may be the size of the Linux
binary. It is about 3 times the windows version and looks to me as your
debug version. Why would it otherwise be so extremely large compared to
the other variants? When I compile the sources for Linux the binary gets
about the same size as the Windows executable.

[Sebastien Lelong]

Hi Rob, guys,

Just committed of new version of jalv24p running under OSX :)

I've followed Eur's instruction, removing "-Werror" in Makefile.inc. I also had to create "bin" output directory at zip output directory's root. I'd need more input from OSX users, it works on my machine, but...

Cheers,

Seb 

--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to jal...@googlegroups.com.
To unsubscribe from this group, send email to jallib+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jallib?hl=en.

--
Sébastien Lelong

[Sebastien Lelong]

Hi Rob, Kyle,

About the sample, I had a look, it seems like a bug in the compiler. Guilty line:

const byte myfile[MINIX_MAX_FILENANE_LEN] = "file2K\0                       "

This is a NULL terminated string. MINIX_MAX_FILENAME_LEN is const, its value is 30.

Now replace "\0" by "\n", warning is gone. Sounds like the compiler doesn't like \0 escape sequence...

Kyle, does it make sense to you ?

Thanks.

Cheers,

Seb

--
Sébastien Lelong

[zmafoox]

Greets,

Yeah, that makes sense though I don't see it in the code. I'll see what I can do.

Seb

To unsubscribe from this group, send email to jallib+un...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/jallib?hl=en.

--
Sébastien Lelong

[Sebastien Lelong]

Great, thanks Kyle
Cheers
Seb

To view this discussion on the web visit https://groups.google.com/d/msg/jallib/-/GFiq5Jm0gJIJ.