|
From: Josef W. <Jos...@gm...> - 2005-11-12 01:17:35
|
On Saturday 12 November 2005 00:09, Tom Hughes wrote: > In message <200...@gm...> > Josef Weidendorfer <Jos...@gm...> wrote: > > > On Friday 11 November 2005 20:56, Julian Seward wrote: > > > > * Tom's biarch stuff > > > > > > Done. > > > > Still unsolved: biarch for external tools? > > * Can valgrind.pc generation changed to include information for > > biarch installations? > > * Or install 2 valgrind.pc files, and the configure of the > > external tool checks for both a valgrind64.pc and valgrind.pc? > > I don't think pkgconfig has any support for dual architecture > systems Why would pkgconfig fail to support some further variables in valgrind.pc? The major defined ones (Name/Description/Version) have the same value for both subarchitectures in our case. All the variables handled in any special way by pkg-config (Libs/Cflags) would describe the primary architecture (amd64 here), and for the secondary arch we define our own variable names, e.g. installtypes=2 arch=amd64 arch2=x86 platform2=x86-linux valt_load_address2=... Libs2=-L... -l... Cflags2=... Perhaps I am totally misusing pkgconfig here :-) BTW: I use my own 10-liner Perlscript to read the .pc file, so this is no problem... > so the latter is probably the best we can do. Nothing > else seems to bother that I have seen. I have the fear that with 2 pc files, distros will change the names to their convention (e.g. in valgrind-x86/amd64.pc or valgrind32/64.pc), and external tool installations will fail to detect these (if not part of the distro). Josef |