In the makefile that I sent you you could see that I was renaming the
.o into .rel.
Works fine like that.
On Wed, Jul 9, 2014 at 3:25 PM, Joshua Lansford
wrote:
> On Wed, Jul 9, 2014 at 9:07 AM, Maarten Brock
> wrote:
>>
>> The only issue is that gputils uses .o instead of .rel object files and
Hi,
If you realy are into numerics, you can emulate doubles using floats.
Here are some pointers
http://stackoverflow.com/questions/6769881/emulate-double-using-2-floats
At the endo of the day everythign is an integer, so you can always re
implement double precision (from your link you will need o
> When using the -mpic16 flag the compiler doesn't seem to produce rel files
> when -c is supplied.
It works for me here without problems. I am using 3.4.0.
https://github.com/kakila/libdwengo-sdcc/blob/master/lib/Makefile.am
On Tue, Jul 8, 2014 at 9:40 PM, Joshua Lansford
wrote:
> Hello folks
t; Hope that helps,
> Raphael
>
>
> On Sat, Jul 5, 2014 at 6:02 PM, JuanPi wrote:
>>
>> Hi all,
>>
>> I managed to get the code compiled by sdcc now I ma trying to create a
>> library.
>>
>> I am using autotools and the problem I have is that
Hi all,
I managed to get the code compiled by sdcc now I ma trying to create a library.
I am using autotools and the problem I have is that when libtool calls
sddc I get
sdcc libio18f4550.lib libc18f.lib libsdcc.lib dwengoADC.lo libdwengo.la
at 1: warning 119: don't know what to do with file 'd
Dear all,
I managed to start testing the compilation of our library [1] with sdcc.
I managed to onvert some of the flags to the sdcc syntax.
I was wondering if aynbody has gone already through this process.
The command I am translating now is the compilation
- MC18:
CFLAGS= -Ou- -Ot- -Ob- -Op-
On Sun, Mar 2, 2014 at 11:58 AM, Kustaa Nyholm
wrote:
> On 02/03/2014 02:46, "JuanPi" wrote:
>
>>Our platform uses a PIC18f4550, which I am not sure how well supported
>>it is by sdcc, but I plan to find out.
>
> For what it is worth, I've used SDCC with P
Hi all,
I am working for a non-profit in Belgium. We execute educational
projects, check links below for more info.
We have been stuck with non-free tools for long enough and we are
looking forward to free our toolchain.
Our platform uses a PIC18f4550, which I am not sure how well supported
it is