Re: [ft-devel] No support for side-by-side installation of x86-64and i386
Just I've searched documents in libtool-1.5.22 2.1a, and libtool mail list archive. In the latest CVS snapshot (2.1a), still multilib support is written as future issue. OK. Anyway, I will ask future plan and advise to libtool list, but I think my patch is sufficient for urgent fix until future libtool update. Just go on. Maybe you can drop a note to the libtool maintainers that you've implemented multilib support in FreeType. Again, thanks for your work. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] No support for side-by-side installation of x86-64and i386
Here's revised version of dual-ABI patch which generates unified ftconfig.h for 64/32bit UNIX platforms. This looks very promising! Thanks for your hard work. AC_ARG_ENABLE([multi-abi], [...] Please put all this stuff into one or more separate files (similar to ft-munmap.m4) to make it more comprehensible. Additionally I wonder whether there isn't already some stuff in, say, libtool. Otherwise you could probably contribute your code -- I'm quite sure that the libtool maintainers can give you additional advice. + /* ARCH_DEP_BEGIN */ #undef SIZEOF_INT #undef SIZEOF_LONG + /* ARCH_DEP_END */ Here we need more comments to explain what the comments mean and that they must not be changed. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] No support for side-by-side installation of x86-64and i386
On Mon, 26 Dec 2005 11:28:30 +0100 (CET) Werner LEMBERG [EMAIL PROTECTED] wrote: AC_ARG_ENABLE([multi-abi], [...] Please put all this stuff into one or more separate files (similar to ft-munmap.m4) to make it more comprehensible. Additionally I wonder whether there isn't already some stuff in, say, libtool. Otherwise you could probably contribute your code -- I'm quite sure that the libtool maintainers can give you additional advice. OK, I'll check libtool and reconsider to reduce the script size. Although I believe mine is not the first autoconf macro, I've checked macros bundled with automake, autoconf, and http://ac-archive.sourceforge.net/ but I could not find. + /* ARCH_DEP_BEGIN */ #undef SIZEOF_INT #undef SIZEOF_LONG + /* ARCH_DEP_END */ Here we need more comments to explain what the comments mean and that they must not be changed. OK! Regards, mpsuzuki ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] No support for side-by-side installation of x86-64and i386
[Resend since I did not see the original one. Sorry if it duplicates. ] Hallo Werner, On Thursday, December 8th, 2005 14:37Z, Werner LEMBERG wrote: As far as I've seen, most system headers exist in one copy only, and use preprocessor macros to detect which the architecture is; usually via sys/isa_defs.h, which defines macros for most of the interesting cases: [...] This is the solution I like most. I don't know how difficult it is to achieve that... Well, if you are reading Ilya's original message, it is about what is currently done for Freetype (no surprise to me): Ilya wrote on Tuesday, December 6th, 17:02Z: ] Currently, freetype i386 and x86-64 collide in the following files: ] /usr/bin/freetype-config ] /usr/include/freetype2/freetype/config/ftconfig.h that is, they collide ONLY on the two built configuration files which describe the target architecture; in fact, it boils down that the target architecture bi-arch x86-32 + x86-64 has not been forcasted (in freetype-config.in and ftconfig.h.in). This is only what we need (but that's not easy). This is why I asked Ilya to provide his idea of his environment which would lead to the automatic selection of the correct subtarget/more/arch (to get back to the analogy with Solaris headers, the selecting macros in sys/isa_defs.h, if I got it correctly : sorry I do not use Solaris either). Then, we can probably build the picture of the two files to create for a GNU/Linux x86-64 target, allowing selection of x86-32 as well : if I am not mistaken it is the most sensible option. Then backport it into the .in templates (this is NOT the easy part). Please, do NOT make the mistake to assume that target=*-x86_64 is sufficient: while nowadays every targetting x86-64 also supports x86-32 (i386 if you prefer), there are no architectural reason for this to hold forever, particularly in embeeded; and also, and perhaps more importantly, the trick to have /lib for x86-32 and /lib64 for x86-64 is NOT universal (e.g. on Windows, it is /lib, or more exactly /Program Files or system32, for x86-64, and something along the lines of /lib32 (like /Program Files (x86)) for x86-32). Also as said earlier, we probably should not assume everybody has GLib or pkg-config installed when targetting x86-64 (furthermore it may lead to version dependencies). Antoine ___ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel