public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Invoking static library automatically
@ 2006-12-01  7:45 Rohit Arul Raj
  2006-12-01 15:22 ` Ian Lance Taylor
  0 siblings, 1 reply; 2+ messages in thread
From: Rohit Arul Raj @ 2006-12-01  7:45 UTC (permalink / raw)
  To: gcc-help

Hi all,

I have built a static runtime library and i want the linker to access
it automatically without having to pass it explicitly.

Are there any environmental variables available to make this happen?

Regards,
Rohit

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Invoking static library automatically
  2006-12-01  7:45 Invoking static library automatically Rohit Arul Raj
@ 2006-12-01 15:22 ` Ian Lance Taylor
  0 siblings, 0 replies; 2+ messages in thread
From: Ian Lance Taylor @ 2006-12-01 15:22 UTC (permalink / raw)
  To: Rohit Arul Raj; +Cc: gcc-help

"Rohit Arul Raj" <rohitarulraj@gmail.com> writes:

> I have built a static runtime library and i want the linker to access
> it automatically without having to pass it explicitly.
> 
> Are there any environmental variables available to make this happen?

I'm not aware of any environment variable which directs the linker to
automatically include a library.  If there were one, it would be
documented in the linker manual:
    http://sourceware.org/binutils/docs-2.17/ld/index.html

You can force the linker to always include a library by changing the
linker script, but of course then you have to tell the linker to use
your new linker script.

Ian

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2006-12-01 15:22 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-12-01  7:45 Invoking static library automatically Rohit Arul Raj
2006-12-01 15:22 ` Ian Lance Taylor

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).