Rolf Eike Beer wrote:
Clinton, Stephen,
inspired by what OpenBSD currently does downstream I did a patch that
always searches for the plain executable names (like moc) after all
versioned executable names (e.g. moc4) have been tried.
I recall discussion about this kind of thing before, but
Brad King wrote:
On 05/21/2014 09:18 AM, Stephen Kelly wrote:
I recall discussion about this kind of thing before, but I think
relating to qmake-qt4 and other versioned names.
Currently qmake is preferred over qmake-qt4, but I do not know
why.
I found what I was remembering/referring to
On Wednesday, May 21, 2014 10:50:42 AM Brad King wrote:
On 05/21/2014 09:18 AM, Stephen Kelly wrote:
I recall discussion about this kind of thing before, but I think
relating to qmake-qt4 and other versioned names.
Currently qmake is preferred over qmake-qt4, but I do not know
why.
On 05/21/2014 11:21 AM, Stephen Kelly wrote:
I found what I was remembering/referring to here:
http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/6313/focus=6314
[snip]
On 05/21/2014 11:24 AM, Clinton Stimpson wrote:
Should we change FindQt4.cmake to loop over paths first,
On 2014-05-15 08:36, Ben Boeckel wrote:
On Thu, May 15, 2014 at 12:45:27 +0200, Nicolas Desprès wrote:
Nope. These variables are the cmake equivalent to the __LINE__ and __FILE__
C-pre-processor macro. What I need is the #line directive equivalent which
force the value of these variables so
Am Mittwoch, 21. Mai 2014, 09:24:34 schrieb Clinton Stimpson:
On Wednesday, May 21, 2014 10:50:42 AM Brad King wrote:
On 05/21/2014 09:18 AM, Stephen Kelly wrote:
I recall discussion about this kind of thing before, but I think
relating to qmake-qt4 and other versioned names.
On Wed, May 21, 2014 at 8:06 PM, Matthew Woehlke
mw_tr...@users.sourceforge.net wrote:
On 2014-05-15 08:36, Ben Boeckel wrote:
On Thu, May 15, 2014 at 12:45:27 +0200, Nicolas Desprès wrote:
Nope. These variables are the cmake equivalent to the __LINE__ and
__FILE__
C-pre-processor macro.
On 2014-05-21 15:24, Nicolas Desprès wrote:
On Wed, May 21, 2014 at 8:06 PM, Matthew Woehlke wrote:
On 2014-05-15 08:36, Ben Boeckel wrote:
This will also likely need a policy since there's no guarantee that
#line directives don't exist in already existing code as comments.
Maybe we should
On Wed, May 21, 2014 at 9:31 PM, Matthew Woehlke
mw_tr...@users.sourceforge.net wrote:
On 2014-05-21 15:24, Nicolas Desprès wrote:
On Wed, May 21, 2014 at 8:06 PM, Matthew Woehlke wrote:
On 2014-05-15 08:36, Ben Boeckel wrote:
This will also likely need a policy since there's no guarantee
I've noticed that the FindFreetype module doesn't search standard Unix and
Windows paths. Can I add these to the find module?
As it currently stands, the module won't find Freetype in either Windows or
Linux (despite it being installed in very standard locations). It can be
overridden by creating
10 matches
Mail list logo
