You would need to ensure that the debug and release libraries have identical 
ABIs.  That is definitely not the case for complib.  IBAL seems to be fine, 
though you would need both the debug version of IBAL (identical name to the 
release) and the debug version of complib (different name from release complib).

I'd just make the debug bits available in the SDK only - they are only 
applicable to application developers, not to end users.

-Fab

Hefty, Sean wrote on Wed, 29 Jun 2011 at 09:01:13

> I say go for it.
> 
> I believe that the reason was so that you could install both the debug and
> release versions.  IMO, it ends up being a pain in the butt, since an app must
> be compiled against the correct version, and you can't simply install the
> debug version of a library without recompiling the app.
> 
> It would be better if the libraries used the same names and an app could
> switch between the debug and release version of a library simply by copying
> in the new file.
> 
>> -----Original Message-----
>> From: [email protected] [mailto:ofw-
>> [email protected]] On Behalf Of Uri Habusha
>> Sent: Wednesday, June 29, 2011 1:21 AM
>> To: [email protected]; Smith, Stan
>> Subject: [ofw] removing the dpecial debug file
>> 
>> Currently the OFA build creates different files for debug and release
>> version (i.e complib.dll for release and complibd.dll for debug).
>> 
>> 
>> 
>> I don't know what was the reason to do it in this way, but I  know that
>> there is no other product that do it. If you wants to debug an issue you
>> can install the debug version that contains the debug dll.
>> 
>> 
>> 
>> Using different names complicates our installation package and testing. I
>> want to change the code to use same file name for debug and release.
>> 
>> 
>> 
>> Please let me know if there is any reason not doing it.
>> 
>> 
>> 
>> Thanks Uri
>> 
>> 
>> 
>> Uri Habusha
>> 
>> Windows SW Development Lead
>> 
>> 
>> 
>> Mellanox Technologies
>> P.OBox 586, Yokneam 20692
>> 
>> Israel
>> 
>> 
>> 
>> 
>> 
>> 
> 
> _______________________________________________
> ofw mailing list
> [email protected]
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
_______________________________________________
ofw mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw

Reply via email to