> -----Original Message----- > From: Travis Vitek (JIRA) [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 19, 2007 1:22 AM > To: stdcxx-dev@incubator.apache.org > Subject: [jira] Commented: (STDCXX-675) [MSVC] implement > autolinking feature > > > [ > https://issues.apache.org/jira/browse/STDCXX-675?page=com.atla > ssian.jira.plugin.system.issuetabpanels:comment-tabpanel#actio > n_12552933 ] > > Travis Vitek commented on STDCXX-675: > ------------------------------------- > > If the new user takes advantage of the autolinking feature, > they will have to modify their build system to get it to work > with a previous version of the library. i.e. they will need > to explicitly link the library file when they go back to 4.2.0.
You're right, but what the type of incompatibility of this case? :) Source? - No, because there no source changes. Binary? - No again :) > Will this ever be useful for any compiler other than MSVC and > ICC/Windows? Yes, if the autolinking feature will be implemented there :) > Is there a way that we can ensure the user links > the right library on all platforms? We can define some symbol in the library with the unique name for the each build type, and make the reference to this symbol in <config.h>. Then in case the linking with incorrect library the "undefined symbol reference" linker error will be issued. > This wouldn't avoid the > need to explicitly link the library, but it would eliminate > issues with linking the wrong library. Right. Farid.
