Re: [KOS] Cadcdev-kallistios Digest, Vol 32, Issue 5

[Harley L. <los...@gm...>]

On Wed, Dec 22, 2010 at 3:31 PM, Caleb Cittadino
<cal...@gm...> wrote:
> I think my bfd items are here:
>
> /usr/local/dc/i686-pc-cygwin/sh-elf/lib
> /usr/local/dc/i686-pc-cygwin/sh-elf/include

Yeah, you're right. Those are the directories you should be using for
BFDLIB and BFDINCLUDE The Makefile.cfg I included wasn't quite right.
Glad you spotted the correct directories on your own :)

> It looks like the Makefile.cfg is looking for more libs than I have (for the
> cygwin specific block):
>
> "BFDLIB        = -L/usr/local/dc/i686-pc-cygwin/sh-elf/lib -lbfd -liberty
> -lintl"
>
> Should I just add an extra directory to scan with -L so that iberty gets
> picked up in the other location or is that the wrong lib?  Also what about
> the third lib listed up there: "intl".  Is that one still needed for cygwin?

You should also have an iberty in /usr/lib,
/lib,/usr/i686-pc-cygwin/lib or someplace similar. That's actually
what should then get picked up by the compiler for that portion of the
compilation process (which is what you want.) intl may not be needed,
and z(lib) might be needed to be added to that line. I can't say for
sure, but that should get you pretty close.

Just a bit of info about dcload, it consists of two programs, a host
and a target program. The host program is run on your machine to send
executables to the target (the Dreamcast.) The libbfd from sh-elf is
required for the host to know how to work with the target elf format
at a low level.

> On Wed, Dec 22, 2010 at 1:04 PM, Harley Laue <los...@gm...>
> wrote:
>>
>> Caleb Cittadino wrote:
>> > Running "./buildcross -dc -k" did the trick!
>>
>> Ooops, I made a slight typo when I said ./buildcross dc -k, I should
>> have written ./buildcross.sh dreamcast -k
>> -dc -k most likely built kos&kos-ports then rebuilt kos&kos-ports. Not
>> a huge deal besides taking a bit more time. :)
>>
>> > Now I am just trying to find a way to test code.  It seems the best way
>> > is
>> > to just send the elf over the network to the dc using "dcload-ip"
>> > correct?
>> >  I pulled down the latest one (1.0.4 from 2003) and am trying to get it
>> > built now.  Running into some issues with the bfd libs though.  Anyone
>> > use
>> > something different or better that is known to work with the latest
>> > tools?
>>
>> If you have a BBA dcload-ip is absolutely the way to go. It's not
>> exactly the easiest thing to build because it requires that libbdf
>> from sh-elf be installed and then you have to edit the Makefile.cfg
>> for dcload to point to the installed location of that lib/include. The
>> other thing that might be useful for you to change in the Makefile.cfg
>> is the IP of the Dreamcast.
>>
>> There is one other BBA loader that I can think of off the top of my
>> head, but AFAIK it's totally unmaintained (not to mention dcload is
>> much more robust in comparison.) Anyways the loader I'm thinking of is
>> IP upload slave (http://mc.pp.se/dc/ipslave.html) which was one of the
>> first Dreamcast BBA loaders.
>>
>> Attached is a Makefile.cfg that worked for me on a Linux machine that
>> I used buildcross with. You'll probably still need to edit it a bit,
>> but it should be much closer to what you need.