bugThe FreeType Project - Bugs: bug #38412, ft2demos is troublesome to build...

 
 

bug #38412: ft2demos is troublesome to build against out-of-source-built freetype2

Submitted by:  Michał Górny <michalgorny>
Submitted on:  Tue 26 Feb 2013 02:18:17 PM UTC  
 
Severity: 3 - NormalItem Group: None
Status: InvalidPrivacy: Public
Assigned to: Werner LEMBERG <wl>Open/Closed: Closed
Planned Release: None

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Thu 28 Feb 2013 11:17:19 PM UTC, comment #2:

Oh, I missed that, sorry. Thanks for the suggestion, I have switched our ebuild to that method.

Michał Górny <michalgorny>
Wed 27 Feb 2013 07:05:34 AM UTC, comment #1:

Why don't you follow the advice given in the README file in the top directory of `ft2demos'? Using this batch file, it works just fine:

tar xzvf freetype-2.4.11.tar.gz
tar xzvf ft2demos-2.4.11.tar.gz

ln -s freetype-2.4.11 freetype2

mkdir freetype2-build
mkdir ft2demos-build

(
cd freetype2-build
../freetype2/configure
make
)

(
cd ft2demos-build
make FT2DEMOS=1 \
TOP_DIR_2=../ft2demos-2.4.11 \
-f ../freetype2-build/Makefile
)

If you want to do it more symmetrical, try this:

tar xzvf freetype-2.4.11.tar.gz
tar xzvf ft2demos-2.4.11.tar.gz

ln -s freetype-2.4.11 freetype2
ln -s ft2demos-2.4.11 ft2demos

mkdir freetype2-build
mkdir ft2demos-build

(
cd freetype2-build
../freetype2/configure
make
)

(
cd ft2demos-build
make FT2DEMOS=1 \
-f ../freetype2-build/Makefile
)

So what exactly isn't documented? If you think that the various XXX_DIR variables should be documented, please provide a patch for the README file in `ft2demos'.

Werner LEMBERG <wl>
Project AdministratorIn charge of this item.
Tue 26 Feb 2013 02:18:17 PM UTC, original submission:

We are building freetype2 using an out-of-source build, and I'm trying hard to get ft2demos built against it.

First, I have tried:

make TOP_DIR=../freetype-2.4.11 OBJ_DIR=../freetype-2.4.11-amd64

but it fails trying to find 'ftconfig.h'.

If I hack the Makefile to include $(OBJ_DIR) in FT_INCLUDES, it compiles fine but fails to find libtool for linking:

make: ../freetype-2.4.11/builds/unix/libtool: Command not found

Looking at the Makefile, it seems that OBJ_BUILD is used to find it (and the includes), so I actually have to set both OBJ_DIR and OBJ_BUILD:

make TOP_DIR=../freetype-2.4.11 OBJ_{BUILD,DIR}=../freetype-2.4.11-amd64

It compiles some of the demos fine but then fail to find libtool again, for grblit.lo:

/bin/sh: 1: ../freetype-2.4.11/builds/unix/libtool: not found

Looking further, it seems that OBJ_BUILD defaults to BUILD_DIR. If I set BUILD_DIR instead of it:

make TOP_DIR=../freetype-2.4.11 {OBJ_DIR,BUILD_DIR}=../freetype-2.4.11-amd64

demos finally build.

After the long story, my question is: does it have to be that hard? Could you please consider making building demos against out-of-source build simpler, or at least documenting the way of doing it?

Michał Górny <michalgorny>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by wl (Posted a comment)
  • -unavailable- added by michalgorny (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Fri 01 Mar 2013 07:45:11 AM UTCwlStatusNeed Info=>Invalid
      Open/ClosedOpen=>Closed
    Wed 27 Feb 2013 07:05:34 AM UTCwlStatusNone=>Need Info
      Assigned toNone=>wl

    Back to the top


    Powered by Savane 3.1-cleanup1