Changes to make fptools insfrastructure usable for standalone
libraries
Alastair Reid
alastair at reid-consulting-uk.ltd.uk
Wed May 21 10:49:33 EDT 2003
On Wednesday 21 May 2003 2:29 pm, Simon Marlow wrote:
> Rather than reply individually to each point in your message, I've just
> hacked up what I think package.mk should look like (attached, but
> completely untested).
After adding this to my library Makefile
SRC_CC_OPTS += -I$(shell $(GHC) --print-libdir)/include
(required when compiling greencard code), this worked well.
If it still works for ghc builders, I think what you have is enough progress
that it should be committed.
I haven't yet tried setting up libraries/X11/mk/*.mk as you suggest...
This may have some bearing on the following:
> If you just leave $(libdir) alone, you'll get one that looks like
> /usr/lib/<yourlibrary>.
It still wants to install into $(libdir) not $(libdir)/HSX11 (or some other
suitable subdirectory). The install rules in target.mk make it quite clear
that it will install into $libdir.
One could argue that installing directly into libdir is what users of
configure expect $libdir to mean - but it feels wrong to me.
>> TOP = .
>> include $(TOP)/mk/boilerplate.mk
>> FPTOOLS_TOP := ../..
> Hmm, you should need to touch $(FPTOOLS_TOP).
Assuming that was meant to be "shouldn't", the reason I have to change the
setting is this line in boilerplate.mk
FPTOOLS_TOP := $(TOP)
--
Alastair
More information about the Glasgow-haskell-bugs
mailing list