Hi all, I'm working on a klibc gcc wrapper, which of course needs to know where everything is installed to know where to pull stuff from. This means making a working "make install". My current thinking is to drop /usr/include/klibc, and instead put the whole tree under /usr/lib/klibc. In particular, I'd like to have: $(CROSS) is the cross-compilation prefix if any. /lib/klibc-*.so -- shared binary /usr/bin/$(CROSS)klcc -- gcc wrapper /usr/lib/klibc/$(CROSS)include -- include files /usr/lib/klibc/$(CROSS)lib -- library files /usr/lib/klibc/$(CROSS)bin -- utility binaries The shared binary would be installed in /lib as well as in /usr/lib/klibc/$(CROSS)lib. How does this look to people? -hpa
On Tue, Mar 01, H. Peter Anvin wrote:> How does this look to people?Looks ok.
On Tue, Mar 01, H. Peter Anvin wrote:> Hi all, > > I'm working on a klibc gcc wrapper, which of course needs to know where > everything is installed to know where to pull stuff from. This means > making a working "make install". > > My current thinking is to drop /usr/include/klibc, and instead put the > whole tree under /usr/lib/klibc. In particular, I'd like to have: > > $(CROSS) is the cross-compilation prefix if any. > > /lib/klibc-*.so -- shared binaryThis is runtime thing, the libs to link against should all go into the $DEVELPREFIX or whatever variable you pick.
Olaf Hering wrote:>> >>$(CROSS) is the cross-compilation prefix if any. >> >>/lib/klibc-*.so -- shared binary > > This is runtime thing, the libs to link against should all go into the > $DEVELPREFIX or whatever variable you pick.Yes, those are all in /usr/lib/klibc/lib. -hpa