infinint-type dependent headers?
Johnathan Burchill <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.dar.general |
|---|---|
| Organization | Department of Physics and Astronomy, University of Calgary |
| Message-ID | <[email protected]> |
Hi Denis, I thought it was appropriate to move this topic over to dar-discussions. Excuse me if this is not okay. As far as the infinint::... compilation problem when largefile support is enabled in libdar, I copied several lines from your configure.ac and put them in my autoconf file: AC_SYS_LARGEFILE # Checks for typedefs, structures, and compiler characteristics. AC_C_CONST AC_C_INLINE AC_TYPE_OFF_T etc. That fixed the kdar compile problem when largefile support is enabled. On to the header installation issue: Denis Corbin wrote: >I think the best thing to do (in a long term view) is for me >to change the way included files are installed, for they do >not depend on any macro (I mean #define). But, a given user Do you mean you would have the MODE=?? not defined anymore? >may need to have both installed libdar32 and libdar64, this >is possible for the library as the do not have the same >name, but the problem is that the included files share the >same name. So I suppose that making several subdirectories >like "include/dar/32" "include/dar/64" >"include/dar/infinint" is a possible solution, to have >several version of each included files. I do not see why this would be necessary. Doesn't your MODE switch already take care of the various infinint types? I do not see how the headers differ that much that you need separate directories for them. > >this would imply a change in kdar to have and use #include ><dar/64/libdar.hpp> or #include <dar/infinint/libdar.hpp> >and so on. > In which case I would have to #include <dar/MODE_DIR/libdar.hpp> where MODE_DIR is defined at configure time? i.e. MODE_DIR is one of 32, 64, or infinint? >If you have better idea about the subdirectories name, >thanks to let me know. And also If you have another >solution. :-) > Looks like I need to study the problem some more.:) I'm pretty sure I'm missing the point altogether, so I'll get back to you about it later. >Denis. JB -- Johnathan K. Burchill, Ph.D. [email protected]
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQBADhkYrXMSOtiWrO4RAtGBAJ9Cdif4H6Oxpe7OxvqYiXWM4icmnQCeJSeT Whpqz2xnOl2Sc/kAazo2U98= =ewts -----END PGP SIGNATURE-----