sdcc-user

[Sdcc-user] PIC16 - how to manually create library ?

[<vac...@se...>]

Hello,

> Try with these updates, compiles with SDCC 2.7.0 #4818.
> 
> Note that you must recompile the SDCC library files using the 2455 (or
> 4550, ...) as the default processor. If you use the ones that come
> with the SDCC distribution, the resulting code won't work (problem with
> sfr allocations between the 18f242 and the 18f2455).

I got the message form Xander regarding his USB framework.

How can I manually create (on Win32 platform) pic18f2455.lib file ? I downloaded sdcc-2.7.0.tar.bz2 source package and there is just Linux (./configure;make;make install) methodology described.

If I try it with just "sdcc pic18f2455.c" - it does not work for me.

Vaclav

Re: [Sdcc-user] PIC16 - how to manually create library ?

[Taco W. <wa...@sc...>]

On Wednesday 05 December 2007 16:53, Vaclav Peroutka rattled on the keyboard:
> Hello,
>
> > Try with these updates, compiles with SDCC 2.7.0 #4818.
> >
> > Note that you must recompile the SDCC library files using the 2455 (or
> > 4550, ...) as the default processor. If you use the ones that come
> > with the SDCC distribution, the resulting code won't work (problem with
> > sfr allocations between the 18f242 and the 18f2455).
>
> I got the message form Xander regarding his USB framework.
>
> How can I manually create (on Win32 platform) pic18f2455.lib file ? I
> downloaded sdcc-2.7.0.tar.bz2 source package and there is just Linux
> (./configure;make;make install) methodology described.
>
> If I try it with just "sdcc pic18f2455.c" - it does not work for me.
>
> Vaclav
>
If you work with windows, you should install cygwin (http://www.cygwin.com) 
which gives you a bash shell where you have an unix-like environment. In this 
environment you can easily configure, make etc. 
Taco

Re: [Sdcc-user] PIC16 - how to manually create library ?

[Peter K. <pe...@pk...>]

On Dec 6, 2007 9:18 AM, Taco Walstra <wa...@sc...> wrote:

> On Wednesday 05 December 2007 16:53, Vaclav Peroutka rattled on the
> keyboard:
> > Hello,
> >
> > > Try with these updates, compiles with SDCC 2.7.0 #4818.
> > >
> > > Note that you must recompile the SDCC library files using the 2455 (or
> > > 4550, ...) as the default processor. If you use the ones that come
> > > with the SDCC distribution, the resulting code won't work (problem
> with
> > > sfr allocations between the 18f242 and the 18f2455).
> >
> > I got the message form Xander regarding his USB framework.
> >
> > How can I manually create (on Win32 platform) pic18f2455.lib file ? I
> > downloaded sdcc-2.7.0.tar.bz2 source package and there is just Linux
> > (./configure;make;make install) methodology described.
> >
> > If I try it with just "sdcc pic18f2455.c" - it does not work for me.
> >
> > Vaclav
> >
> If you work with windows, you should install cygwin (http://www.cygwin.com
> )
> which gives you a bash shell where you have an unix-like environment. In
> this
> environment you can easily configure, make etc.

Or just RTFM, it's all explained.

-
Peter

Re: [Sdcc-user] PIC16 - how to manually create library ?

[<vac...@se...>]

> > >
> > > How can I manually create (on Win32 platform) pic18f2455.lib file ? I
> > > downloaded sdcc-2.7.0.tar.bz2 source package and there is just Linux
> > > (./configure;make;make install) methodology described.
> > >
> > > If I try it with just "sdcc pic18f2455.c" - it does not work for me.
> > >
> > > Vaclav
> > >
> > If you work with windows, you should install cygwin (http://www.cygwin.com
> > )
> > which gives you a bash shell where you have an unix-like environment. In
> > this
> > environment you can easily configure, make etc.
> 
> Or just RTFM, it's all explained.
> 

Hello, thank you for your answers. But please before you should have read the question. I did have not asked about compilation of the whole package. That's not what I wanted to do. I asked how to compile single library.

Anyway Raphael just answered me - thank you very much.

Vaclav

Re: [Sdcc-user] PIC16 - how to manually create library ?

[soliton <sol...@gm...>]

I am using mingw to compile it under Windows. You can find it here:
http://www.mingw.org/
However to compile sdcc you also need bison and flex, you can find
them in gnuwin32 package at: http://gnuwin32.sourceforge.net/
Also if your target is PIC microcontroller, then you also need
gputils. Get it from: http://gputils.sourceforge.net/

Good luck :D


-- 
soliton
------------------------------------
Diskusi di http://phimega.com/forums

Re: [Sdcc-user] PIC16 - how to manually create library ?

[Peter K. <pe...@pk...>]

btw: there is a script in support/scripts directory called somethig like
sdcc_cygwin_mingw32 . ( you can modify it to exclude support for non-pic
processors )

It should get you running, when everything is compiled ( before make install
) go to lib directory and compile the libs for your pic.
In any case you'll need cygwin environment to compile sdcc on windows, mingw
is just a way to compile/link it, to work without cygwin.

--
Peter


On Dec 6, 2007 9:42 AM, soliton <sol...@gm...> wrote:

> I am using mingw to compile it under Windows. You can find it here:
> http://www.mingw.org/
> However to compile sdcc you also need bison and flex, you can find
> them in gnuwin32 package at: http://gnuwin32.sourceforge.net/
> Also if your target is PIC microcontroller, then you also need
> gputils. Get it from: http://gputils.sourceforge.net/
>
> Good luck :D
>
>
> --
> soliton
> ------------------------------------
> Diskusi di http://phimega.com/forums
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell.  From the desktop to the data center, Linux is going
> mainstream.  Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> Sdcc-user mailing list
> Sdc...@li...
> https://lists.sourceforge.net/lists/listinfo/sdcc-user
>



-- 
http://www.pkuhar.com/
skype: pkuhar

Re: [Sdcc-user] PIC16 - how to manually create library ?

[<vac...@se...>]

Hello,

I probably do not have MinSYS properly installed. The log is attached.

Is it possible to just run following:
sdcc $SOME_SDCC_PARAMS pic18f2455.c
gpasm $SOME_GPASM_PARAMS pic18f2455.asm
gplib $SOME_GPLIB_PARAMS pic18f2455.o

to have just the desired LIB file ? Or it is just not possible ?

Thank you,
Vaclav

$ support/scripts/sdcc_mingw32 
checking for gawk... gawk
checking version of the package... 2.7.0
checking for i586-mingw32msvc-gcc... /usr/local/cross-tools/i386-mingw3=
2msvc/bin/gcc
checking for C compiler default output file name... configure: error: C=
 compiler cannot create executables
See `config.log' for more details.
make: *** No targets specified and no makefile found.  Stop.

> ------------ P=F9vodn=ED zpr=E1va ------------
> btw: there is a script in support/scripts directory called somethig l=
ike
> sdcc_cygwin_mingw32 . ( you can modify it to exclude support for non-=
pic
> processors )
> 
> It should get you running, when everything is compiled ( before make =
install
> ) go to lib directory and compile the libs for your pic.
> In any case you'll need cygwin environment to compile sdcc on windows=
, mingw
> is just a way to compile/link it, to work without cygwin.
> 
> --
> Peter
> 
> 
> On Dec 6, 2007 9:42 AM, soliton <sol...@gm...> wrote:
> 
> > I am using mingw to compile it under Windows. You can find it here:=

> > http://www.mingw.org/
> > However to compile sdcc you also need bison and flex, you can find
> > them in gnuwin32 package at: http://gnuwin32.sourceforge.net/
> > Also if your target is PIC microcontroller, then you also need
> > gputils. Get it from: http://gputils.sourceforge.net/
> >
> > Good luck :D
> >

Re: [Sdcc-user] PIC16 - how to manually create library ?

[Peter K. <pe...@pk...>]

T24gRGVjIDYsIDIwMDcgMTA6NDQgQU0sIFZhY2xhdiBQZXJvdXRrYSA8dmFjbGF2cGVAc2V6bmFt
LmN6PiB3cm90ZToKCj4gSGVsbG8sCj4KPiBJIHByb2JhYmx5IGRvIG5vdCBoYXZlIE1pblNZUyBw
cm9wZXJseSBpbnN0YWxsZWQuIFRoZSBsb2cgaXMgYXR0YWNoZWQuCj4KPiBJcyBpdCBwb3NzaWJs
ZSB0byBqdXN0IHJ1biBmb2xsb3dpbmc6Cj4gc2RjYyAkU09NRV9TRENDX1BBUkFNUyBwaWMxOGYy
NDU1LmMKPiBncGFzbSAkU09NRV9HUEFTTV9QQVJBTVMgcGljMThmMjQ1NS5hc20KPiBncGxpYiAk
U09NRV9HUExJQl9QQVJBTVMgcGljMThmMjQ1NS5vCj4KPiB0byBoYXZlIGp1c3QgdGhlIGRlc2ly
ZWQgTElCIGZpbGUgPyBPciBpdCBpcyBqdXN0IG5vdCBwb3NzaWJsZSA/Cj4KPiBUaGFuayB5b3Us
Cj4gVmFjbGF2CgoKPiAkIHN1cHBvcnQvc2NyaXB0cy9zZGNjX21pbmd3MzIKCnNkY2NfbWluZ3cz
MiBpcyBmb3IgY29tcGlsaW5nIHdpbmRvd3MgdmVyc2lvbiBvbiBsaW51eC4KdXNlIHNkY2NfY3ln
d2luX21pbmd3MzIgaWYgeW91IGFyZSBjb21waWxpbmcgb24gd2luZG93cy4KCgoKCj4KPiBjaGVj
a2luZyBmb3IgZ2F3ay4uLiBnYXdrCj4gY2hlY2tpbmcgdmVyc2lvbiBvZiB0aGUgcGFja2FnZS4u
LiAyLjcuMAo+IGNoZWNraW5nIGZvciBpNTg2LW1pbmd3MzJtc3ZjLWdjYy4uLgo+IC91c3IvbG9j
YWwvY3Jvc3MtdG9vbHMvaTM4Ni1taW5ndzMybXN2Yy9iaW4vZ2NjCj4gY2hlY2tpbmcgZm9yIEMg
Y29tcGlsZXIgZGVmYXVsdCBvdXRwdXQgZmlsZSBuYW1lLi4uIGNvbmZpZ3VyZTogZXJyb3I6IEMK
PiBjb21waWxlciBjYW5ub3QgY3JlYXRlIGV4ZWN1dGFibGVzCj4gU2VlIGBjb25maWcubG9nJyBm
b3IgbW9yZSBkZXRhaWxzLgo+IG1ha2U6ICoqKiBObyB0YXJnZXRzIHNwZWNpZmllZCBhbmQgbm8g
bWFrZWZpbGUgZm91bmQuICBTdG9wLgo+Cj4gPiAtLS0tLS0tLS0tLS0gUMWvdm9kbsOtIHpwcsOh
dmEgLS0tLS0tLS0tLS0tCj4gPiBidHc6IHRoZXJlIGlzIGEgc2NyaXB0IGluIHN1cHBvcnQvc2Ny
aXB0cyBkaXJlY3RvcnkgY2FsbGVkIHNvbWV0aGlnIGxpa2UKPiA+IHNkY2NfY3lnd2luX21pbmd3
MzIgLiAoIHlvdSBjYW4gbW9kaWZ5IGl0IHRvIGV4Y2x1ZGUgc3VwcG9ydCBmb3Igbm9uLXBpYwo+
ID4gcHJvY2Vzc29ycyApCj4gPgo+ID4gSXQgc2hvdWxkIGdldCB5b3UgcnVubmluZywgd2hlbiBl
dmVyeXRoaW5nIGlzIGNvbXBpbGVkICggYmVmb3JlIG1ha2UKPiBpbnN0YWxsCj4gPiApIGdvIHRv
IGxpYiBkaXJlY3RvcnkgYW5kIGNvbXBpbGUgdGhlIGxpYnMgZm9yIHlvdXIgcGljLgo+ID4gSW4g
YW55IGNhc2UgeW91J2xsIG5lZWQgY3lnd2luIGVudmlyb25tZW50IHRvIGNvbXBpbGUgc2RjYyBv
biB3aW5kb3dzLAo+IG1pbmd3Cj4gPiBpcyBqdXN0IGEgd2F5IHRvIGNvbXBpbGUvbGluayBpdCwg
dG8gd29yayB3aXRob3V0IGN5Z3dpbi4KPiA+Cj4gPiAtLQo+ID4gUGV0ZXIKPiA+Cj4gPgo+ID4g
T24gRGVjIDYsIDIwMDcgOTo0MiBBTSwgc29saXRvbiA8c29saXRvbi5saXN0QGdtYWlsLmNvbT4g
d3JvdGU6Cj4gPgo+ID4gPiBJIGFtIHVzaW5nIG1pbmd3IHRvIGNvbXBpbGUgaXQgdW5kZXIgV2lu
ZG93cy4gWW91IGNhbiBmaW5kIGl0IGhlcmU6Cj4gPiA+IGh0dHA6Ly93d3cubWluZ3cub3JnLwo+
ID4gPiBIb3dldmVyIHRvIGNvbXBpbGUgc2RjYyB5b3UgYWxzbyBuZWVkIGJpc29uIGFuZCBmbGV4
LCB5b3UgY2FuIGZpbmQKPiA+ID4gdGhlbSBpbiBnbnV3aW4zMiBwYWNrYWdlIGF0OiBodHRwOi8v
Z251d2luMzIuc291cmNlZm9yZ2UubmV0Lwo+ID4gPiBBbHNvIGlmIHlvdXIgdGFyZ2V0IGlzIFBJ
QyBtaWNyb2NvbnRyb2xsZXIsIHRoZW4geW91IGFsc28gbmVlZAo+ID4gPiBncHV0aWxzLiBHZXQg
aXQgZnJvbTogaHR0cDovL2dwdXRpbHMuc291cmNlZm9yZ2UubmV0Lwo+ID4gPgo+ID4gPiBHb29k
IGx1Y2sgOkQKPiA+ID4KPgo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiBTRi5OZXQgZW1haWwgaXMgc3Bv
bnNvcmVkIGJ5OiBUaGUgRnV0dXJlIG9mIExpbnV4IEJ1c2luZXNzIFdoaXRlIFBhcGVyCj4gZnJv
bSBOb3ZlbGwuICBGcm9tIHRoZSBkZXNrdG9wIHRvIHRoZSBkYXRhIGNlbnRlciwgTGludXggaXMg
Z29pbmcKPiBtYWluc3RyZWFtLiAgTGV0IGl0IHNpbXBsaWZ5IHlvdXIgSVQgZnV0dXJlLgo+IGh0
dHA6Ly9hbHRmYXJtLm1lZGlhcGxleC5jb20vYWQvY2svODg1Ny01MDMwNy0xODkxOC00Cj4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBTZGNjLXVzZXIg
bWFpbGluZyBsaXN0Cj4gU2RjYy11c2VyQGxpc3RzLnNvdXJjZWZvcmdlLm5ldAo+IGh0dHBzOi8v
bGlzdHMuc291cmNlZm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZvL3NkY2MtdXNlcgo+CgoKCi0tIApo
dHRwOi8vd3d3LnBrdWhhci5jb20vCnNreXBlOiBwa3VoYXIK

Re: [Sdcc-user] PIC16 - how to manually create library ?

[Raphael N. <rn...@we...>]

Hi,


>     Is it possible to just run following:
>     sdcc $SOME_SDCC_PARAMS pic18f2455.c
>     gpasm $SOME_GPASM_PARAMS pic18f2455.asm
>     gplib $SOME_GPLIB_PARAMS pic18f2455.o

Probably yes, the Makefile causes
	
../../../../bin/sdcc --asm=gpasm -mpic16 -p18f452 \
	--std-c99 -I. -I../../../include/pic16 \
	-Wa,-q --fommit-frame-pointer --obanksel=9 \
	--denable-peeps --optimize-goto --optimize-cmp \
	--optimize-df --i-code-in-asm \
	-o "../build/libdev/pic18f2455.o" \
	-c "pic18f2455.c";
rm -f "../build/libdev/pic18f2455.lib";
gplib  -c "../build/libdev/pic18f2455.lib" ../build/libdev/pic18f2455.o

to create pic18f2455.lib from pic18f2455.c. Maybe this is what you want,
after having adjusted some path names?!? In your case, I would also
replace -p18f452 with the actual device used, i.e. -p18f2455. I will
look into the Makefile to see why this is not done in the default libs
and change it (if it's not too difficult ;-))...

Regards,
Raphael