Dear Sir,
I thank Turner for his quick fix of autogen.sh for Mac OS X's
"glibtool" issue, on 2007-01-11.
On Fri, 29 Dec 2006 00:57:12 +0900
[EMAIL PROTECTED] wrote:
>>> In my personal opinion, putting some hooks to check autotools
>>> versions into autogen.sh is not bad idea.
>>
>>I don't object,
Happy New Year everyone!
On 2006-12-22 23:05, Werner LEMBERG said:
>> Could autogen.sh be conditionalised to include Chirstian's hack?
>
>No. You are actually using a developer's version (the CVS), thus you
>have to be prepared to use the latest tools in case . On the other
>hand, a `public' t
Hi,
I think Turner and Werner gave me comment to proceed the work,
thank you.
On Mon, 25 Dec 2006 10:29:30 +0100 (CET)
Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>> At present, configure (not builds/unix/configure) has a hook to
>> ascertain whether make is GNU make /or not. I think, putting
>> de
Hi all,
> I think the support status of Mac OS X is almost same with
> most Unix shipped with partial GNU environment.
> Most of tools in Xcode are Apple modified version that are
> based on GNU tools released 1 or 2 years ago. Thus, on Mac
> OS X, we cannot build simply as we can do on GNU/Linux
> At present, configure (not builds/unix/configure) has a hook to
> ascertain whether make is GNU make /or not. I think, putting
> detailed version check into configure is the simplest improvement.
Yep. This has benefits for other platforms too.
> Or, the documentation improvement is better? Wer
Hi,
I distinguish the document for unreleased CVS source (README.CVS)
from the document for released tarball (docs/INSTALL.XXX).
On Fri, 22 Dec 2006 23:05:59 +0100 (CET)
Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>> But this brings me back to the reason I started this thread. :) "Mac
>> install in
> I don't think I really want to install a different automake, I'm
> worried it might interfere with the one I already have.
Just say `./configure --prefix=/foo' while configuring automake, and
everything will be installed into this tree. Doing this there can't
be any interferences.
> But this
On 2006-12-22 10:12, [EMAIL PROTECTED] said:
>>
>>generating `configure.ac'
>>running `aclocal -I . --force'
>>aclocal: unrecognized option -- `--force'
>>Try `aclocal --help' for more information.
>>error while running `aclocal -I . --force'
>>
>
>The autotools (automake, autoconf) bundle
Hi,
I, too saw problems with freetype2 CVS some weeks ago. Downloading the
2.2.1 release did build with ./configure, make, make install out of the
box.
I tried it today your way and it fails as you describe on my Intel
10.4.8.
Sean McBride wrote:
>>mkdir -p ~/Desktop/freetype2/CVS
>cd ~/Desktop/
Hi,
On Thu, 21 Dec 2006 16:04:07 -0500
"Sean McBride" <[EMAIL PROTECTED]> wrote:
>
>generating `configure.ac'
>running `aclocal -I . --force'
>aclocal: unrecognized option -- `--force'
>Try `aclocal --help' for more information.
>error while running `aclocal -I . --force'
>
The autotools
> Can some please explain how I build freetype2?
>From the CVS, building a shared library:
sh autogen.sh
./configure
make
The developer version:
make devel
make
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http:/
On 2006-12-06 10:21, [EMAIL PROTECTED] said:
>On Wed, 6 Dec 2006 06:43:49 +0900
>[EMAIL PROTECTED] wrote:
>>And, I think, if the document notes about how to check the version
>>of GNU make, the problem (for users who don't know which make he
>>has) will be solved. However, yet I've not checked the
Hello Sean,
do you mean that the standard Unix installation instructions
do not work, or simply that you would like an explicit mention
of Mac OS X ?
Regards,
- David Turner
- The FreeType Project (www.freetype.org)
On Tue, 5 Dec 2006 12:49:37 -0500, "Sean McBride" <[EMAIL PROTECTED]> said:
>
Hi,
On Wed, 6 Dec 2006 06:43:49 +0900
[EMAIL PROTECTED] wrote:
>And, I think, if the document notes about how to check the version
>of GNU make, the problem (for users who don't know which make he
>has) will be solved. However, yet I've not checked the minimum
>version of GNU make to build. I will
Hi,
Possibly this is my task.
Apple bundles 2 make programs, /usr/bin/gnumake (GNU make) and
/usr/bin/bsdmake (BSD pmake). /usr/bin/make had ever been linked
to bsdmake, but now it is linked to gnumake. I think, additional
mention about "gnumake" is enough.
And, I think, if the document notes ab
On 2006-12-05 21:31, David Turner said:
>do you mean that the standard Unix installation instructions
>do not work, or simply that you would like an explicit mention
>of Mac OS X ?
The latter. Mostly because of this in INSTALL.UNIX:
The FreeType build system _exclusively_ works with GNU Ma
Hi,
I searched the entire /docs folder for the word 'mac' and it only
appears in the files CHANGES and formats.txt.
There is no mention of the Mac in any of the INSTALL* files. It would
be nice to have an INSTALL.MAC file, even if it was minimal and deferred
to the INSTALL.UNIX file.
--
___
17 matches
Mail list logo
