[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libssh and Visual C++ (again)


Of course, if we git rid of ssize_t, things become simpler :-)

2012/9/27 Andreas Schneider <asn@xxxxxxxxxxxxxx>

> On Thursday 27 September 2012 14:41:33 Christophe Baribaud wrote:
> > 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...
>
> I think this is still too complex and I don't like it.
>
> The sftp functions should simply return an int64_t.
>
> We can add a
>
> typedef int64_t ssh_ssize_t to libssh.h, but it doesn't really matter.
>
>
> Cheers,
>
>
>         -- andreas
>
>
>

References:
libssh and Visual C++ (again)Christophe Baribaud <christophe.baribaud@xxxxxxxxx>
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)Andreas Schneider <asn@xxxxxxxxxxxxxx>
Archive administrator: postmaster@lists.cynapses.org