Hi,
> Yes, now it compiles, great! Than you so much for the help
> with this little detail and the whole SDCC project, one of the most
> enjoyable and useful open source projects I've used.
Good to hear.
> If I want to compile this in a 'standard' SDCC installation, do
> I just leave the -L path
On 14.2.2013 23.33, "Raphael Neider" wrote:
>> Ok, so I could not give up so easily, I found 'opensnoop' on Mac OS and
>> it shows that SDCC opens:
>>
>> 501 2232 gplink-1 libdev18f4550.lib
>> 501 2232 gplink-1
>> /Users/nyholku/sdcc-3.2.0/share/sdcc/lib/pic16//libdev18f455
Hi,
> 3.2.1 #8415 (Feb 10 2013) (Linux)
>
> which I downloaded, compiled and installed on ubuntu 12.04
>
> I compiled the example code with
>
>> sdcc -mpic16 --use-non-free crt0i.o toggle_led.c
You are at least missing a command line parameter: -p18f47j53
While it is strange that libdev18f452 (th
Hi,
I am a new user of sdcc and I was trying to compile and link a simple
program for the pic 18f47j53.
First of all, the sdcc version I am using is
3.2.1 #8415 (Feb 10 2013) (Linux)
which I downloaded, compiled and installed on ubuntu 12.04
I compiled the example code with
> sdcc -mpic16 --u
> Ok, so I could not give up so easily, I found 'opensnoop' on Mac OS and
> it shows that SDCC opens:
>
> 501 2232 gplink-1 libdev18f4550.lib
> 501 2232 gplink-1
> /Users/nyholku/sdcc-3.2.0/share/sdcc/lib/pic16//libdev18f4550.lib
> 501 2232 gplink-1
> /Users/nyhol
On 14.2.2013 21.14, "Raphael Neider" wrote:
>
>$ strace -o trace.log -f -eopen sdcc
>$ grep libdev18f4550.lib trace.log | grep -v ENOENT
>
>should yield several hits and reveal the path to the libdev18f4550.lib
>that is being used by the linker.
>
>$ gplib -s /path/to/your/libdev18f4550.lib | gre
On 14.2.2013 21.14, "Raphael Neider" wrote:
>Hi again,
>
>(This is a potential double-post since my previous post does not seem
>to have made it to the list. This version is edited/updated.)
>
>I tried with r8008 and cannot reproduce this with properly built
>libraries.
>___eeprom_gptr{get,put}[1
Hi again,
(This is a potential double-post since my previous post does not seem
to have made it to the list. This version is edited/updated.)
I tried with r8008 and cannot reproduce this with properly built libraries.
___eeprom_gptr{get,put}[1234] are provided by libdev18f4550.lib, so I
guess thi
On 14.2.2013 20.19, "Raphael Neider" wrote:
>Hi,
>
>I think you are missing libdev18f4550.lib in the to-be-linked
>libraries. If adding this just before or after libsdcc.lib does not
Tried both, no change:
>help, please provide the output of your failing command with the -V
>("capital-V") flag
Hi,
I think you are missing libdev18f4550.lib in the to-be-linked
libraries. If adding this just before or after libsdcc.lib does not
help, please provide the output of your failing command with the -V
("capital-V") flag added to the command line.
I am currently rebuilding my gputils/sdcc from scr
Hi,
I had already tried the --print-search-dirs
nyholkus-MacBook-Pro:kusti nyholku$ /Users/nyholku/sdcc-3.2.0/bin/sdcc
--print-search-dirs -L /Users/nyholku/sdcc-3.2.0/share/sdcc/lib/pic16/
-Wl,-m,-s18f4550.lkr -mpic16 -p18f4550 --disable-warning 85 --std-sdcc99
--obanksel=3 --use-non-free -o ../
Sdccman chapter "2.3 Search Paths" might also help you.
Borut
On 14. 02. 2013 16:54, Maarten Brock wrote:
> If you want to see which paths are searched and in which order, use
> --print-search-dirs on the command line.
>
>
>> On 14.2.2013 17.18, "Maarten Brock" wrote:
>>
>> Hi Maarten,
>>
>> and
If you want to see which paths are searched and in which order, use
--print-search-dirs on the command line.
> On 14.2.2013 17.18, "Maarten Brock" wrote:
>
> Hi Maarten,
>
> and thanks.
>
>>Hi,
>>
>>--L is wrong, it should be -L
>
> Ok.
>
>>And with --nostdlib not only the default path is ignore
On 14.2.2013 17.18, "Maarten Brock" wrote:
Hi Maarten,
and thanks.
>Hi,
>
>--L is wrong, it should be -L
Ok.
>And with --nostdlib not only the default path is ignored but also the
>default library names. So you must specify them on the command line.
Yes, --nostdlib was just a test, I do want
Hi,
--L is wrong, it should be -L
And with --nostdlib not only the default path is ignored but also the
default library names. So you must specify them on the command line.
Maarten
> Hi
>
> according to the manual there is an '--L' option to specify
> the library paths but when I use it I get:
>
Hi
according to the manual there is an '--L' option to specify
the library paths but when I use it I get:
at 1: warning 117: unknown compiler option '--L' ignored
if I use -L the compiler finds the /usr/local/share/sdcc/lib/pic16/
libraries not the ones I specify with the -L option.
If I, in ad
On 14.2.2013 15.26, "Kustaa Nyholm" wrote:
>
>Also, there must be something wrong because I also get:
>
>message: using default linker script
>"/usr/local/share/gputils/lkr/18f4550.lkr"
>
>
>although I specify the linker script on the command line, I must
>have something wrong on that command line
On 14.2.2013 10.28, "roelof 't Hooft" wrote:
>
Thanks for the tip, I may end up doing something like that,
however, it looks to me that I should be able to just tell
sdcc to use different path for libraries with -L option.
I've tried this:
/Users/nyholku/sdcc-3.2.0/bin/sdcc "-L
/Users/nyhol
On Thu, 2013-02-14 at 07:17 +0200, Kustaa Nyholm wrote:
> If so, how can I keep the old and new sdcc and gputils
> separate so that I can use both for the time being?
Hi,
What I do is to make seperate directories for each
version of sdcc in /opt/ and have a symbolic link
to it :
roelofh@castle:~
19 matches
Mail list logo
