On 14.2.2013 23.33, "Raphael Neider" <rnei...@web.de> 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//libdev18f4550.lib
>>   501   2232 gplink        -1
>> /Users/nyholku/sdcc-3.2.0/bin/../share/sdcc/lib/pic16/libdev18f4550.lib
>>   501   2232 gplink        10
>> /usr/local/share/sdcc/lib/pic16/libdev18f4550.lib
>>   501   2232 gplink        11
>> /usr/local/share/sdcc/lib/pic16/libdev18f4550.lib
>>   501   2232 gplink        11
>> /usr/local/share/sdcc/lib/pic16/libdev18f4550.lib
>
>[snip]
>
>> so it is not there!
>
>Well, the file actually is "there" (it is in the tar.bz2), but not
>where you looked for it ;-)
>>From the tar.bz2 I gather that it will probably end up in
>
>/Users/nyholku/sdcc-3.2.0/share/sdcc/non-free/lib/pic16

Looks like it, sure, great!

>
>which has to be added to the linker search path (-L).
>I assume you have done something like
>
>$ tar xvf sdcc-3.2.0-universal-apple-macosx.tar.bz2
>$ mv sdcc /Users/nyholku/sdcc-3.2.0

Well, being a lazy mac user just double clicked ont bz2
file and dragged it my homedir from the Downloads...

>
>The --use-non-free option to sdcc seems to add this search path too
>late -- i.e., after the linker has picked up the libdev18f4550.lib
>from /usr/local/share/sdcc/lib/pic16/libdev18f4550.lib, which
>obviously comes too early in the search path. I would have to look
>into this more carefully in order to figure out whether to change the
>search path order. Probably I will move all "non-free" paths to before
>system default paths, we'll see. Anyways, that wouldn't help you much
>right now, so just add the path to -L manually and you should be fine.



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.

An additional question:

If I want to compile this in a 'standard' SDCC installation, do
I just leave the -L path away (can't test that for a while), asking
because I want publish this piece of code so that other can
enjoy it and obviously an absolute path to my home dir won't
help any prospective user?

BTW it seems that it is not necessary to specify 'libdev18f4550.lib'
on the command line to SDCC (you know this I guess), as long as
the paths are ok and searched in correct order this is enough.


br Kusti





------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user

Reply via email to