Google Code Exporter
Google Code Exporter
``` Static link cost much time for big library(such like boost,ACE,sqlite3,etc...). I always using dll for debug, and static link for release. I don't like dll because there still have...
``` Maybe better to use *.manifest to find the right dll. ``` Original comment by `[email protected]` on 2 Feb 2012 at 3:29
``` The main issue isn't that there's no package management, it's that the ctemplate library has an interface based on std::*. Trying to export that from a dll in a...
``` My assumption was that package management would take care of these variants. Not using std::string in the ABI might be an option. The simple 'solution' might be to drop...
``` Has this issue been superseded by issue 75? If so, could you close this one? ``` Original comment by `olafvdspek` on 1 Jun 2012 at 11:38
``` I'm currently building ctemplate with the trial version of xlC but, considering that xlC costs about 4-5k per developer, I might soon have to go back to gcc. So,...
``` ugh, that bit of code was always a bit of a hack and now it's coming back to bite us. :-( What I really want to capture is the...
``` The only good way I can think of is to read /proc/self/maps and scan for the text segment. It works, but is not portable. Since you already have the...
``` Thanks for doing this research! It's good to know the options. I'm not sure how I feel about doing a file I/O operation to implement what may well be...
``` An interesting development. Here's what the local expert had to say: --- The situation described in that bug report can occur when using an old version of glibc which...