[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libssh and Visual C++ (again)
[Thread Prev] | [Thread Next]
- Subject: Re: libssh and Visual C++ (again)
- From: Christophe Baribaud <christophe.baribaud@xxxxxxxxx>
- Reply-to: libssh@xxxxxxxxxx
- Date: Thu, 27 Sep 2012 14:41:33 +0200
- To: libssh@xxxxxxxxxx
This is my last cumulative patch to address this issue... The new file "libssh_config.h" is built by cmake, and installed. It is the /public/ configuration file, unlike config.h which is the /private/ configuration file. I haven't found a simplier patch to continue using ssize_t under unix/linux platforms, and provide a good equivalent under WIN32 and WIN64 platforms Trying to define the ssize_t type under windows has serious drawbacks. Under WIN32, it is sometimes int and sometimes long (signed 32 bits). Under WIN64 it should be __int64 (signed 64 bits). If two libraries define ssize_t by their own, there are great (bad) chances that they disagree... Regards Christophe 2012/9/27 Werner Koch <wk@xxxxxxxxx> > On Wed, 26 Sep 2012 20:58, christophe.baribaud@xxxxxxxxx said: > > > file, but is it a good practice to have an installed header file whose > > content varies from an architecture to another? > > Yes, that is imho fine and much easier to maintain than fragile > #ifdefs. Some libraries install a generic file and one system specific - > which is a similar approach. > > > Shalom-Salam, > > Werner > > -- > Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. > > >
Attachment:
0003-provide-fallback-definition-of-ssize_t.patch
Description: Binary data
Re: libssh and Visual C++ (again) | Andreas Schneider <asn@xxxxxxxxxxxxxx> |
libssh and Visual C++ (again) | Christophe Baribaud <christophe.baribaud@xxxxxxxxx> |
Re: libssh and Visual C++ (again) | Andreas Schneider <asn@xxxxxxxxxxxxxx> |
Re: libssh and Visual C++ (again) | Christophe Baribaud <christophe.baribaud@xxxxxxxxx> |
Re: libssh and Visual C++ (again) | Andreas Schneider <asn@xxxxxxxxxxxxxx> |
Re: libssh and Visual C++ (again) | Werner Koch <wk@xxxxxxxxx> |
Re: libssh and Visual C++ (again) | Christophe Baribaud <christophe.baribaud@xxxxxxxxx> |
Re: libssh and Visual C++ (again) | Christophe Baribaud <christophe.baribaud@xxxxxxxxx> |
Re: libssh and Visual C++ (again) | Werner Koch <wk@xxxxxxxxx> |