incubator-stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Farid Zaripov" <Farid_Zari...@epam.com>
Subject RE: binary compatibility question
Date Thu, 18 Oct 2007 21:22:27 GMT
> От: Travis Vitek [mailto:Travis.Vitek@roguewave.com]
> Отправлено: Пт, 19.10.2007 0:07
> Кому: stdcxx-dev@incubator.apache.org
> Тема: RE: binary compatibility question
> 
> Farid Zaripov wrote:
> >
> >  The binary compatibility requirement is related to shared
> >libraries only, or to both shared and static libraries?
> >
> 
> Well technically it is a problem with both static and shared, but for it
> to be an issue with a static build the user would have to have kept
> their object files laying around, otherwise they would just rebuild the
> entire app. Right?
 
  Yes.

> 
> >  If only to shared libraried, then the STDCXX-509 issue can be fixed
> >on MSVC by exporting alias with the required name using /EXPORT
> >linker option.
> >
> 
> Yes, this was mentioned in the status call on Wednesday. The idea was
> discarded because it seems it would require some changes to the build
> infrastructure.
 
  No changes ar required in build infrastructure, because of we can use
#pragma comment (linker, "") dirctive (see the src/export.cpp file).
 
  I.e. #pragma commnt (linker, "/EXPORT:?__rw_flt_infinity@__rw@@3MB=?__rw_flt_infinity@__rw@@3T_FltBits@1@B,DATA")
for __rw_flt_infinity and so on.

Farid.

Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message