gnupic: GNU LIB for PIC
Subject:
Re: GNU LIB for PIC
From:
Antonio A Todo Bom ####@####.####
Date:
17 Jul 2002 13:38:04 -0000
Message-Id: <20020717101833.297d3630.antonio@projetos.etc.br>
Hi Jeff, excuse me for the late.
Yesterday my SMTPd was used for Spam attack. So I was out for 1 day.
No dia (On:) Tue, 16 Jul 2002 23:39:52 -0500 (CDT)
Jeff Jackowski ####@####.#### escreveu: (wrote:)
> On Sat, 13 Jul 2002, Antonio A Todo Bom wrote:
>
> >Hi Jeff
> >
> >No dia (On:) Fri, 12 Jul 2002 18:57:52 -0500 (CDT)
> >Jeff Jackowski ####@####.#### escreveu: (wrote:)
> >
> >>
> >> I've made a few libraries for the PIC and released them already.
> >> Unfortunately, the code (in C) only compiles on the CCS PIC C compiler.
Anything in anytime. To the moment I think it's good. We can have many libs for many plataforms but slowly we can port all the libs to any main format or some of 2 or 3 diferent formats.
> >> I'm too far along on a project right now to port the libraries, but I have
> >> put out what I have under the GPL. I'm not idealogically or religiously
> >> opposed to other licenses, so I can be convinced to put the code under
> >> another license. It is most important to me that the code be used (I'm
> >> using it on a project now), and I get some credit for it :-)
> >>
> >> http://home.hiwaay.net/~jeffj1/projects/index.html
> >
> > Ok, it's fine.
> >
> > My work now is to organize all my codes in a set of library
> >blocks. All are in .asm
> >
> > I need study about turn all the codes in .asm to relocable codes.
> >This is hard.
>
> I don't understand what you mean.
Oh! Yes, I mean that my goal is produce codes that can be relocable in ROM memory and the files used on internal RAM maybe would be automaticaly defined by UDATA, UDATA_OVR & UDATA_SHR etc... directives.
See "MPASM Use's guide with MPLINK and MPLIB" section 6.5 from microchip.
But to the moment, all int-RAM positions are define in the header file. So the programmer has the control but he needs to think about every position that is used.
>
> > What so you think about create first a metod to organize all
> >blocks, building rules to use headers files.
> >
> > Then when anybody want to use them, can download, edit only the .h
> >and append the .o to the linker or include the .asm?
>
> Sounds like you're talking about a library that is at least fairly
> configurable at compile time. Generally I'd call that a good idea. I try
> to write in such flexibility to my C libraries, but I do have a bias for
> adding what features I need.
>
> > I am thinking to write a doc to conduct this. What do you think
> >about?
>
> You mean some documenatation, not some MS Word thing, right?
Nevermind. I can use M$, because I don't have M$-Windows in my Office.
I'm thinking in TETEX format to generate PS/PDF, HTML, pure ASCII txt's and others. We can use lyx.
But if TETEX is too hard to somebady, we can use OpenOffice that puts out files in HTML, txt and ps/pdf formats.
>
> > I am totaly open to new ideas. We want to realize this, in any manner.
[snip]
Best regards,
Antonio Augusto Todo Bom Neto
LAX Eletronica e Telecomunicacoes Ltda
gEDA-BR - Users Group - http://gedabr.projetos.etc.br
