[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: "Bernhard R. Link" <brlink@xxxxxxxxxx>
- Reply-to: libssh@xxxxxxxxxx
- Date: Sat, 29 Sep 2012 14:13:48 +0200
- To: libssh@xxxxxxxxxx
* Werner Koch <wk@xxxxxxxxx> [120927 14:11]: > 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. #ifdefs might be fragile, but non-generic header files are quite fragile, too, and can have ugly side-effects with cross-compiling and other cases. As long as there is a specific case like working around some very unusual environment, just checking for that with an ifdef can be quite a robust solution. Bernhard R. Link
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> |