Btw, anybody done QT6 build of ftinspect lately?When I was writing the
makefile, I had to install some qt5*-devel packages. I did some qt3/qt4 stuff a
long time ago, so I kept those, but uninstalled most of qt5-dev stuff when I
see qt6 being installed as part of half-yearly upgrade. I am on
Yes, the moc location on fedora 38 can be queried with:
pkg-config Qt5Core --variable=host_bins
If this works correctly on other systems, we should set
MOC=`pkg-config Qt5Core --variable=host_bins`/moc
Or put PATH=${PATH}:`pkg-config Qt5Core --variable=host_bins` and MOC=moc ?
I am more inclined
On Fri, 14 Jul 2023 at 00:49, suzuki toshiya wrote:
> > The pkg-config interface should take care of everything easily. Debian
> and Ubuntu have the relevant qt5 pkg-config files. Other distributions
> should too.
>
> Does pkg-config give the information for the pathname of moc?
> (the original
On Friday, 14 July 2023 at 03:53:10 GMT+8, Werner LEMBERG
wrote:
> Well, this is not how Meson support is currently set up in
`freetype-demos`: in `subprojects/freetype.wrap`, HEAD of FreeType's
> git repository is used. This is absolutely necessary while developing
> since we regularly
>> If we are going to overhaul the build system, I’ve long wanted to
>> have FreeType demos build as a separate package that links against
>> a system-installed FreeType library (not the source directory).
>
> I second that! I think only ttdebug definitely wants to link against
> freetype at the
On Thursday, 13 July 2023 at 22:46:38 GMT+8, Hugh McMaster
wrote:
> If we are going to overhaul the build system, I’ve long wanted to have
> FreeType demos build as a separate package that links against a
> system-installed FreeType library (not the source directory).
I second that! I
The pkg-config interface should take care of everything easily. Debian and
Ubuntu have the relevant qt5 pkg-config files. Other distributions should too.
Does pkg-config give the information for the pathname of moc?
(the original question by Hin-Tak was asking about the
appropriate path to use
On Thu, 13 Jul 2023 at 14:20, suzuki toshiya wrote:
> I would try to let AX_HAVE_QT() macro to find appropriate set:
>
> https://www.gnu.org/software/autoconf-archive/ax_have_qt.html
>
> In the case of Debian (and Ubuntu), qtchooser might be the unified
> interface to switch 4, 5, and maybe 6 in
On Tue, 11 Jul 2023 at 19:26, suzuki toshiya wrote:
> Hi,
>
> In the conventional workflow, the source tree of the FreeType2 library
> has "./configure", but freetype-demos does not have. Just starting
> "make" with existing Makefile under "freetype-demos" carries the
> configured values from
Hi Werner,
On Tue, 11 Jul 2023 at 02:10, Werner LEMBERG wrote:
>
> >> If ftinspect and, potentially, other software is not going to be
> >> built via autotools, is there a case to move to another build
> >> system?
>
> Well, yes. Meson will eventually become the main tool for building
>
I would try to let AX_HAVE_QT() macro to find appropriate set:
https://www.gnu.org/software/autoconf-archive/ax_have_qt.html
In the case of Debian (and Ubuntu), qtchooser might be the unified
interface to switch 4, 5, and maybe 6 in future. It seems that
AX_HAVE_QT() does not check it, because
Besides the obvious (LDFLAGS and CXXFLAGS), I wonder what's correct way to
detect the qt moc tool? It is
/usr/bin/moc-qt5
/usr/lib64/qt5/bin/moc
/usr/lib64/qt5/bin/moc-qt5
on my system (fedora 38). They are all the same. "/usr/lib64/qt5/bin/moc" is
probably canonical, instead of
Good, I was just trying to update configure.raw to add C++ version check &
pkg-check for Qt5 :-)
Regards,
mpsuzuki
On 2023/07/13 11:30, Hin-Tak Leung wrote:
Not really a big fan of cmake/qmake/meson, I thought I'll give it a try, both
to revise my makefile-fu, and perhaps as an educational
Not really a big fan of cmake/qmake/meson, I thought I'll give it a try, both
to revise my makefile-fu, and perhaps as an educational tool for one of the
gsoc people struggling with makefiles.
Here is a bare-minimum sketetal makefile for building ftinspect. It is written
to be minimal, it
On Tuesday, 11 July 2023 at 17:27:02 GMT+8, suzuki toshiya
wrote:
> If somebody wants to try to make autotools to support the building
> of Qt5-based ftinspect, new configure should be added to freetype-demos,
> to check the availability of the extra libraries for ftinspect?
> Or, such check
Hi,
In the conventional workflow, the source tree of the FreeType2 library
has "./configure", but freetype-demos does not have. Just starting
"make" with existing Makefile under "freetype-demos" carries the
configured values from freetype directory. The meson for the ftinspect
wants to confirm
>> If ftinspect and, potentially, other software is not going to be
>> built via autotools, is there a case to move to another build
>> system?
Well, yes. Meson will eventually become the main tool for building
FreeType, I think (or rather, it definitely won't become CMake as the
default).
On Monday, 10 July 2023 at 20:05:58 GMT+8, Hugh McMaster
wrote:
> I've been preparing an update to the Debian package of FreeType and
> realised ftinspect is limited to the meson build system only. Debian,
> by default, has always used autotools.
> There are three build systems currently
I've been preparing an update to the Debian package of FreeType and
realised ftinspect is limited to the meson build system only. Debian,
by default, has always used autotools.
There are three build systems currently available for use in FreeType:
autotools, cmake and meson. As I understand past
19 matches
Mail list logo
