This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Re: Re: how to build a driver to a single library


Hi, Andrew Lunn

I have do that following your advice.
but it seems the driver is nerver be loaded to run.

i do these in my ethernet driver:

	NETDEVTAB_ENTRY (if_dtest_netdev,
		 "if_dtest",
 		if_dtest_init,
 		&if_dtest_sc);

	extern cyg_netdevtab_entry_t *if_dtest_netdev_ex = &if_dtest_netdev;

and linked as:

	i386-elf-gcc -nostartfiles -L..../ecos_install/lib -Llibdtest.a -Ttarget.ld -g -
nostdlib -Wl,--gc-sections -Wl,-static -o app app.o

should a modify something in the file target.ld?

what's the trouble?


Sincerely yours,
Tian-Jun

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 > On Tue, Jul 19, 2005 at 09:01:28AM +0800, Tianjun - zdk wrote:
> >  Hi,Andrew 
> >  
> >    so i should not to linked the library to extras.o?
> >  and just to generate a libarery mylib.a use my favourite name?
> >  and then use this command to link it in my Application
> >  
> >   compile  -lmylib mylib.a application.c
> >  
> >    can this working?
> 
> There is no need to link your library to extras.o. Just link your
> application with the library as normal, eg something like
> 
>     arm-elf-gcc -o foobar application.o -lmylib -nostartfiles  -Ttarget.ld
> 
>         Andrew


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]