Is there any way to build STLPort iostream libraries statically? Or is it actually better if I keep it as is, and just add the dll file on the release versions of my projects?
Is there any way to build STLPort iostream libraries statically? Or is it actually better if I keep it as is, and just add the dll file on the release versions of my projects?
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
*bumps and hides from the moderators*
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
I'd guess that there is a way to compile it statically, because a google( "STLPort static") returns lots of hits.
dwk
Seek and ye shall find. quaere et invenies.
"Simplicity does not precede complexity, but follows it." -- Alan Perlis
"Testing can only prove the presence of bugs, not their absence." -- Edsger Dijkstra
"The only real mistake is the one from which we learn nothing." -- John Powell
Other boards: DaniWeb, TPS
Unofficial Wiki FAQ: cpwiki.sf.net
My website: http://dwks.theprogrammingsite.com/
Projects: codeform, xuni, atlantis, nort, etc.
There seems to have been a problem with static libs under windows for version 5.0. Can't really tell from the mailing lists exactly how to solve it. Granted my knowledge of makefiles is very limited.
I'm moving on to version 5.1.0 and will read the documentation more carefully... and GNU Make.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
