Ok, thanks Brad.
Hello Qt Mailing list,
First i thought this is a bug in CMake but it has appeared that it seems to be
a bug in qmllint:
Here the original question:
when I run qmllint from the command line to test an error I get:
C:\Tests>C:\Qt\5.6\msvc2015\bin\qmllint.exe test.qml
test.qml:1
Bruce Stephens writes:
> execute_process(COMMAND ${PERL_EXECUTABLE} -MSys::CPU -e ""
> ERROR_QUIET RESULT_VARIABLE status)
Thank you very much for the tip! The command above works very well for me.
As a CMake newbie, I was afraid that I was overlooking some sort of
"prepackaged" version o
Hi Everyone,
I'm trying to solve a rather peculiar (at least to me) artifact of CMake's
install().
I have a binary file (elf) that I call install() on to copy it and later
package with CPack.
Specifying no permissions results in a RPM extracting in 0444 mode, whereas
specifying USE_SOURCE_PERMI
On Mon, May 23, 2016 at 11:30 PM, Eric Eide wrote:
> Hi! I am a CMake newbie, and I have a question about examining the set of
> available Perl modules on a system.
>
> In CMake (version 2.8.12+), how can I test for the presence of a particular
> Perl module, e.g., "Sys::CPU"?
I think use execut
Hi! I am a CMake newbie, and I have a question about examining the set of
available Perl modules on a system.
In CMake (version 2.8.12+), how can I test for the presence of a particular
Perl module, e.g., "Sys::CPU"?
At the time that CMake is run, I would like to check for the presence of
variou
Hi all. First, a brief intro. My name is Jaffar Sidek and I am a blind
computer programmer and user from Singapore. Would also like to thank
the list owner for helping me with my subscription since I couldn't get
around to filling up the capture thingy on my own. I first came to know
about
Maybe not the most elegant, but here's one way. You could initiate a
trivial dummy sub-build. By this I mean execute a separate CMake run for a
dummy project off to the side somewhere and have it generate a file with
the results of the queries you want, then include() that generated file in
your ma
On 05/23/2016 11:34 AM, Roman Wüger wrote:
> I tried it with CMake 3.5.1 and 3.5.2 and now with the master with
> the same result. I've attached an example which won't work.
I was able to reproduce it with that, but I also tried this:
add_custom_target(${PROJECT_NAME}-c2
COMMAND C:/Qt/5.6/msv
Hi all,
I'm wanting to enable a couple of different options to enable/disable
compiler wrappers in my project. I would like to do something roughly
like this (and something similar to make ccache work right)
option(ENABLE_FUZZ "Use AFL fuzz wrapper" OFF)
if(ENABLE_FUZZ)
set(AFL_PATH /*depends
On 05/23/2016 03:25 AM, Roman Wüger wrote:
> The output is:
>
> 1> _resVar: -1
> 1> _outVar:
> 1> _errVar:
>
> It seems that the error pipe isn’t read correctly, because _errVar is empty.
I cannot reproduce that. With an empty test.qml file I get:
_resVar: -1
_outVar:
_errVar: test.qml
Hi Bruce,
CPack basically packages up everything that gets "installed". We've got a
number of superbuilds as we call them that work this way. Basically you
have all of your external projects perform their install into the same
temporary location somewhere in the build tree, like
${project_name_B
Sorry, that should obviously have gone to this mailing list.
-- Forwarded message --
From: Bruce Stephens
Date: Mon, May 23, 2016 at 2:40 PM
Subject: Using CPack to package things not built using CMake
To: cmake-develop...@cmake.org
Suppose I have a build which uses a number of
If you know the full path to the library then I'd suggest using it as
/path/to/foo/libfoo.a (or .so if it's shared) instead of -L/path/to/foo
-lfoo. CMake will adjust the flags to -L and -l if needed but the
preference is always to use the full library path.
- Chuck
On Mon, May 23, 2016 at 2:23
Thanks for your work on this,
I hope this can get into the main codebase soon. Currently we use internal
productbuild and pkgbuild scripts from our pre-cmake days.
Reading through your patch now I have some feedback:
1. Package ID:
The pkgid for pkgbuild can often be something other than
"com.C
Hi @all,
I'm quite new to CMake. If I've made a mistake or something is much easier to
solve, please tell me.
I'd like to use CMake in embedded development (Build System: Linux, Target: ARM
Microcontroller) to get rid of complicated makefiles.
We're building multiple devices where stuff like e
Just to clarify, although ParaView's superbuild assists you to set up and
compile in either "compile TOOLS" or "CROSS compile" mode (or the default
"HOST" mode) the protobuf inclusion I was speaking of in is found within
paraview's source code and is not an external project.
See ${PVSOURCE}/ThirdPa
As an addition:
If I run "C:\Qt\5.6\msvc2015\bin\qmllint.exe test.qml 1> stdout.txt 2>
stderr.txt"
Then the error is written to stderr.txt.
Regards
Roman
> Am 23.05.2016 um 09:25 schrieb Roman Wüger :
>
> Hello,
>
> when I run qmllint from the command line to test an error I get:
>
> C:\Tes
Hello,
when I run qmllint from the command line to test an error I get:
C:\Tests>C:\Qt\5.6\msvc2015\bin\qmllint.exe test.qml
test.qml:1 : Syntax error
C:\Tests>echo %ERRORLEVEL%
-1
C:\Tests>
If I call this from a CMake script
execute_process(COMMAND C:/Qt/5.6/msvc2015/bin/qmllint.exe
18 matches
Mail list logo
