This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: static vs. shared linking
- From: David Stacey <drstacey at tiscali dot co dot uk>
- To: cygwin at cygwin dot com
- Date: Sat, 11 Apr 2015 19:51:03 +0100
- Subject: Re: static vs. shared linking
- Authentication-results: sourceware.org; auth=none
- References: <5510A9AB dot 7020607 at tiscali dot co dot uk> <5511AF73 dot 9070607 at tiscali dot co dot uk> <20150325090453 dot GB3017 at calimero dot vinschen dot de> <551339E4 dot 60705 at tiscali dot co dot uk> <20150330105529 dot GJ29875 at calimero dot vinschen dot de> <5519A0E1 dot 6020707 at tiscali dot co dot uk> <20150331090527 dot GB32403 at calimero dot vinschen dot de> <551ACCE2 dot 3000103 at tiscali dot co dot uk> <5526351D dot 2000307 at tiscali dot co dot uk> <20150409172453 dot GB6901 at calimero dot vinschen dot de>
On 09/04/15 18:24, Corinna Vinschen wrote:
On Apr 9 09:15, David Stacey wrote:
The solution is to compile with '-frepo', which works for both my test code
and also poco-1.6.0 - although it has quite an impact on the compilation
time (it trebles what was already a fairly lengthy compilation). Do you
think this is the correct way to proceed, or should I look to explicitly
export an instantiation of the std::basic_string<>s that Poco creates?
Sorry, I'm not an expert on this template stuff.
Seriously, you're missing all the fun ;-)
But if -frepo works
for you it sounds like the right thing to go forward.
Thanks for your reply. OK, I'll stick with '-frepo'. I suspect that
users of the Poco library will also be forced to use '-frepo' (otherwise
they'll find themselves with the same problem I had). That shouldn't be
too much of a hardship. I'll be sure to include that on the announcement.
Dave.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple