From: Florian Weimer <fw@deneb.enyo.de>
To: Ian Lance Taylor <iant@google.com>
Cc: Bill Cox <waywardgeek@gmail.com>, gcc@gcc.gnu.org
Subject: Re: Dumb idea for accelerating FOSS development
Date: Wed, 12 Jan 2011 21:13:00 -0000 [thread overview]
Message-ID: <87ipxtrfjr.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <mcry66qw0wn.fsf@google.com> (Ian Lance Taylor's message of "Wed, 12 Jan 2011 08:18:48 -0800")
* Ian Lance Taylor:
> Bill Cox <waywardgeek@gmail.com> writes:
>
>> $ gcc myprog.c -lgit://github/~waywardgeek/sonic=0.1
>
> In Go we have a program goinstall which looks at import statements and
> pulls in required libraries, where the libraries are named based on
> where the sources live. A similar process could work in the C/C++
> world, based on #include statements.
Oh. Has anybody tried to implement this for passing the appropriate
-L/-l flags to the linker? And why isn't everybody doing this? 8-)
prev parent reply other threads:[~2011-01-12 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 11:07 Bill Cox
2011-01-12 12:44 ` Basile Starynkevitch
2011-01-12 13:43 ` Axel Freyn
2011-01-12 14:07 ` Bill Cox
2011-01-12 15:00 ` Jonathan Wakely
2011-01-12 13:32 ` Robert Millan
2011-01-12 14:21 ` David Brown
2011-01-12 16:19 ` Ian Lance Taylor
2011-01-12 21:13 ` Florian Weimer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ipxtrfjr.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=waywardgeek@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).