[ECOS] Re: Can I use libtarget.a as library for other environment

[Bart Veer]

>>>>> "oouchi" == Masatomo Ouchi <oouchi@cns.canon.co.jp> writes:

    oouchi> libtarget.a can be used as library for other development
    oouchi> tool?

    oouchi> I use "CodeWarrior for Embedded Systems(Targeting
    oouchi> PowerPC)" by Metrowerks on Windows NT.

    oouchi> I tryed to link libtarget.a made by eCos with other file
    oouchi> in CodeWarrior.

    oouchi> CoreWarrior said there are warning and errors.

    oouchi>  o warnings are following section is unknown and the
    oouchi> section ignored. .stab .stbstr

    oouchi>  o errors are following is undefined

    oouchi>   __udivdi3 hal_interrupt_handlers hal_interrupt_data
    oouchi> hal_interrupt_objects hal_vsr_table __CTOR_END__
    oouchi> __CTOR_LIST__

    oouchi> Q.1 To begin with, my trial is legal and possible ? Q.2 If
    oouchi> yes, what must I do? Are there other objects to be linked?

We do not expect application developers to use any specific
development environment, such decisions should be left to the
individual developer. However we do require that the underlying tools
used to develop applications, in particular the compiler and the
linker, provide certain basic functionality. Suitable tools are freely
available on the sourceware ftp site.

At a guess, the warnings about .stab and .stbstr probably mean that
the wrong linker is being invoked. The errors about undefined symbols
definitely mean that the linker is not being invoked with the correct
arguments, in particular the generated linker script target.ld is not
being used. The eCos documentation makes it clear what options need to
be passed to the linker.

I have never used CodeWarrior and know very little about its
capabilities. I would hope that it provides functionality such as
specifying which linker gets used and how it gets invoked, but I
cannot speak for Metroworks.

Bart Veer // eCos net maintainer